About

Base64 encoding inflates binary data by approximately 33%, representing every 3 bytes as 4 ASCII characters from a 64-character alphabet. Embedded Base64 GIFs in HTML or CSS bypass additional HTTP requests but increase document payload. Incorrect decoding, truncated strings, or data URI prefix remnants produce corrupt files that fail silently in most viewers. This tool validates the GIF89a/GIF87a signature at the binary level before generating a downloadable file.

The converter strips optional data:image/gif;base64, prefixes automatically, checks character legality against the Base64 alphabet (A - Z, a - z, 0 - 9, +, /, =), and parses the Logical Screen Descriptor to extract frame dimensions and color table metadata. If the decoded bytes do not begin with a valid GIF signature, conversion is rejected before any file is created. Note: this tool handles standard Base64 encoding. Base64url variants (using - and _) require character substitution before input.

Formulas

The Base64 encoding maps every group of 3 input bytes to 4 output characters. The encoded length relates to the original binary size as follows:

L_encoded = 4 ⋅ ceil(L_bytes3)

Inversely, the decoded byte count from a Base64 string of length L_b64 with p padding characters:

L_bytes = 3 ⋅ L_b644 − p

Where L_b64 = length of the Base64 string (excluding whitespace), p = number of trailing = padding characters (0, 1, or 2), and L_bytes = decoded binary length in bytes.

GIF dimensions are extracted from the Logical Screen Descriptor at byte offsets 6 - 9 as little-endian 16-bit unsigned integers:

width = byte[6] + byte[7] × 256

height = byte[8] + byte[9] × 256

The Global Color Table size is determined from bit 7 (presence flag) and bits 0 - 2 (size exponent) of the packed byte at offset 10:

GCT_size = 3 × 2^{(n + 1)} bytes

Where n = value of bits 0 - 2 of the packed field (range 0 - 7).

Reference Data

Property	GIF87a	GIF89a	Notes
Year Introduced	1987	1989	CompuServe specification
Magic Bytes	`47 49 46 38 37 61`	`47 49 46 38 39 61`	First 6 bytes of file
Max Colors	256	256	Per frame, indexed palette
Transparency	No	Yes	Via Graphic Control Extension
Animation	No	Yes	Multiple image blocks with delay
Max Dimensions	65535 × 65535 px	65535 × 65535 px	16-bit unsigned integers
Compression	LZW (Lempel-Ziv-Welch)		Variable code size 2 - 12 bits
Interlacing	Yes	Yes	4-pass progressive rendering
Comment Extension	No	Yes	Block type `0x21FE`
Application Extension	No	Yes	NETSCAPE2.0 for loop control
Trailer Byte	`0x3B`	`0x3B`	Marks end of GIF stream
MIME Type	`image/gif`		RFC 2045 / RFC 2046
Base64 Size Ratio	1.33× original		4 chars per 3 bytes
Data URI Prefix	`data:image/gif;base64,`		Optional; stripped by this tool
Padding Characters	= or ==		Aligns to 4-char boundary
Valid Base64 Chars	64 symbols + pad		A - Z, a - z, 0 - 9, +, /
Browser Support	Universal		All modern browsers decode natively
Color Table Size	2ⁿ⁺¹ entries		n from packed byte bits 0 - 2
Typical Use Cases	Animations, icons, simple graphics		Not suitable for photographs

Frequently Asked Questions

Common causes include embedded line breaks (MIME-wrapped Base64 uses 76-character lines with CRLF), invisible Unicode characters (zero-width spaces from copy-paste), or a data URI prefix that was not stripped. This tool automatically removes whitespace, newlines, and the data:image/gif;base64, prefix. If the string still fails, verify its length is divisible by 4 after cleanup. An incorrect length indicates truncation during transfer.

This tool checks the first 6 bytes of the decoded binary against the GIF87a and GIF89a magic signatures. A JPEG would begin with bytes FF D8 FF, and a PNG with 89 50 4E 47. If someone Base64-encoded a JPEG and labeled it as GIF, this tool will reject it at the signature verification step and report the actual file type detected.

The practical limit is approximately 10 MB of decoded data, which corresponds to roughly 13.3 MB of Base64 text. This constraint comes from browser memory allocation for the atob() function and Blob construction. For very large animated GIFs exceeding this limit, consider server-side decoding. Most embedded Base64 GIFs in CSS or HTML are under 100 KB, well within this range.

Standard Base64 (RFC 4648 §4) uses + and / as characters 62 and 63, with = for padding. Base64url (RFC 4648 §5) replaces + with - and / with _ to be URL-safe, and often omits padding. If your string contains - or _ characters, it is likely Base64url-encoded. You must replace - with + and _ with / before this tool can decode it correctly.

This tool parses the GIF binary to count the number of frames and reports it in the metadata. However, full frame-by-frame extraction requires decoding LZW-compressed image data for each sub-image block, handling disposal methods, and compositing against the canvas state. The preview displays the animated GIF natively via the browser's built-in GIF renderer, showing all frames in sequence.

The decoded file size equals (3 × L_b64 / 4) − p bytes, where p is the number of = padding characters. If whitespace or line breaks were present in the input, they inflate the apparent string length without contributing to the decoded output. This tool strips all non-Base64 characters before calculating the true decoded size.