User Rating 0.0
Total Usage 0 times
Supports standard and URL-safe Base64. Max 10 MB.
Is this tool helpful?

Your feedback helps us improve.

About

Base64 encoding inflates payload size by approximately 33% and obscures the underlying data structure. When the encoded payload is tabular data (CSV, TSV), a decoding error or charset mismatch silently corrupts field values. Truncated padding characters (=) cause NULL byte injection. Misidentified delimiters collapse multiple columns into one. This tool decodes Base64 input using the native atob function with full UTF-8 reconstruction via TextDecoder, then parses the result as structured CSV with automatic delimiter detection by frequency analysis. It handles RFC 4648 standard and URL-safe alphabets. Note: this tool assumes the encoded content is plaintext CSV. Binary formats (XLSX, ODS) embedded in Base64 require a different decoder.

base64 to csv base64 decoder csv converter base64 decode online data converter base64 csv download

Formulas

Base64 encoding maps every 3 input bytes (24 bits) to 4 printable ASCII characters (6 bits each). The decoded byte length is computed as:

Ldecoded = 34 × Lencoded P

where Lencoded = length of the Base64 string (excluding whitespace), and P = number of padding = characters (0, 1, or 2).

Delimiter auto-detection uses a frequency consistency score. For each candidate delimiter d, the tool counts occurrences per line and computes variance:

S(d) = 1n ni=1 (ci c)2

where ci = count of delimiter d on line i, and c = mean count across all lines. The delimiter with the lowest non-zero variance and highest mean count is selected. A variance of 0 with c 1 indicates a perfectly consistent structure.

URL-safe Base64 substitution rule: + - and / _. The tool normalizes URL-safe input before decoding.

Reference Data

Base64 CharacterIndexBinaryNotes
A - Z0 - 25000000 - 011001Uppercase Latin
a - z26 - 51011010 - 110011Lowercase Latin
0 - 952 - 61110100 - 111101Digits
+62111110Standard alphabet
/63111111Standard alphabet
-62111110URL-safe variant
_63111111URL-safe variant
= - - Padding (mod 4 alignment)
DelimiterNameCommon UseDetection Priority
,CommaRFC 4180 CSV standard1 (highest)
;SemicolonEuropean locale CSV exports2
\tTabTSV files, database exports3
|PipeLegacy systems, mainframes4
Input SizeEncoded (Base64)Decoded (Bytes)Overhead
Small1 KB768 B33.3%
Medium100 KB75 KB33.3%
Large1 MB768 KB33.3%
Max recommended10 MB7.5 MB33.3%
PaddingInput Length mod 3Pad CharactersExample
No padding00QUJD
Single pad21QUI=
Double pad12QQ==

Frequently Asked Questions

RFC 4648 requires padding with = to make the encoded length a multiple of 4. However, many systems strip padding. This tool auto-restores missing padding by calculating L mod 4 and appending the required 0, 1, or 2 pad characters before decoding. No manual correction needed.
The tool decodes using TextDecoder with the fatal flag set to FALSE. Malformed byte sequences are replaced with the Unicode replacement character U+FFFD (). If the output contains more than 5% replacement characters, the tool warns that the source data is likely binary (e.g., XLSX, images) rather than plaintext CSV.
The detector samples the first 20 non-empty lines and computes variance for each candidate delimiter (, ; \t |). A delimiter with zero variance and a mean occurrence 1 is ideal. If all candidates show high variance, the tool defaults to comma per RFC 4180 and flags a warning about inconsistent structure.
Yes. URL-safe Base64 replaces + with - and / with _ to avoid issues in URLs and filenames. The tool detects the presence of - or _ characters and automatically converts them back to + and / before decoding.
The tool accepts up to 10 MB of Base64 input, which decodes to approximately 7.5 MB of CSV. The table preview is limited to the first 100 rows for rendering performance. The full decoded CSV is available for download regardless of size. Processing time scales linearly: 1 MB typically decodes in under 200 ms.
The CSV parser implements RFC 4180 compliant tokenization. Fields enclosed in double quotes (") preserve embedded delimiters, newlines, and literal quote characters (escaped as ""). For example, the field "Smith, John" is parsed as a single column value Smith, John rather than being split.