Base64 to text: reading the encoded strings you find in audits
Where Base64 turns up in SEO work, how decoding to text works, and how to tell text from images and credentials.
By ClaudeGPT Si Newsroom, Editorial team··3 min read
To convert Base64 to text, paste the string into a decoder such as the free AyeTab Base64 Encode/Decode page and read the result in the Text pane. If the result is readable, the original was text; if it is a jumble of symbols, it was binary data such as an image or font.
Where SEO people meet Base64
You rarely choose Base64. It shows up while you audit pages, debug tracking or wire up APIs:
- Inline images and fonts. Page source and CSS sometimes embed files as
data:URIs, for exampledata:image/png;base64,iVBOR.... Crawlers and audit tools then report a very long "URL" that is really a file. - API credentials. Many SEO and analytics APIs use HTTP Basic authentication. The header
Authorization: Basic ...is justusername:passwordin Base64, which anyone can read. - Redirect and tracking parameters. Some links pass a destination or a payload as a Base64 query value. Decoding it shows where the link really sends people.
- Structured data and config. Tag managers, feeds and CMS exports occasionally store a field as Base64 to avoid quoting problems.
How Base64 to text works
Base64, defined in RFC 4648, writes any bytes using 64 safe characters: A to Z, a to z, 0 to 9, + and /. Three bytes become four characters, and = pads the end. Decoding reverses that.
The "to text" part is a second step. After decoding you have bytes, and something has to read them as characters. Most text today is UTF-8, which is what the AyeTab tool assumes, so accented letters and other scripts come back intact.
| What the decoded output looks like | What you probably have |
|---|---|
| Readable words or JSON | Text, you are done |
PNG, GIF8 or <svg near the start |
An image |
Starts with %PDF |
A PDF |
user:something |
Basic auth credentials |
| Random symbols throughout | Compressed or encrypted data |
If the page shows "Decode failed", the string is not valid Base64. Check for a missing =, stray spaces, or the URL-safe variant, which uses - and _ instead of + and /.
Decoding credentials and client data safely
An SEO audit often involves values you should not hand to a stranger: a client's API key, a staging password in a Basic auth header, a payload from their analytics. Pasting those into a random decoder site can send them to that site's server.
AyeTab decodes in your browser tab. The input is not uploaded to AyeTab's servers, there is no account, it is free, and the page keeps working offline once loaded. That makes it a sensible default when the string belongs to a client.
For images and data URIs
If the decoded output is an image, switch to the AyeTab Base64 Image tool, which encodes and previews Base64 images. For a page audit, the more useful question is often whether a large inline image should be a normal file the browser can cache. Decoding it first tells you what it is and roughly how big.
Keep the decoder close
The AyeTab extension for Chrome replaces the new tab page with its developer tools and can also open them in a side panel next to the page you are auditing. Paste a Base64 string and smart paste suggests the decoder.
When another tool fits better
If you need to pick a specific character set, decode MIME or PEM variants, or download the result as a file, base64.guru has more options. For bulk work across a crawl export, a short script is faster than any web page. For reading one string during an audit, AyeTab is quick and keeps client data on your machine.