Base64 to CSV Converter

Decode a Base64 payload into CSV and check the shape of the table before you open it.

Base64
CSV
Runs locally in your browser

About the Base64 to CSV Converter

Report APIs and export jobs love to hand back a spreadsheet as a Base64 string inside a JSON response, because that avoids a second request and a temporary file. The catch is that you cannot tell whether the export worked until you decode it. This tool decodes the payload and immediately reports the table shape.

The status line names the separator that was detected, counts the rows and columns, and flags how many rows have a different column count from the header. That last number is the one worth reading: a ragged row usually means an unquoted separator inside a value, which is the single most common way a CSV export goes wrong. Quoted fields are parsed properly, so a comma inside "Bakker, Logistics" does not inflate the count.

European exports frequently use semicolons because the comma is the decimal separator there. Choose a target separator from the dropdown and the fields are re-quoted correctly for it, which saves a round trip through a spreadsheet import dialog. The trim option removes the padding spaces that some report writers add around every value.

Once you have the CSV, CSV Viewer shows it as a grid and CSV to JSON turns it into records. Encoding a table for an API call is the job of CSV to Base64.

How to use

  1. Paste the Base64 payload from your API response or export field.
  2. Read the row, column and separator report in the status line.
  3. Pick a different Separator in the result if your spreadsheet expects one.
  4. Download the file or copy the rows.

Common questions

What does a ragged row warning mean?
At least one row has a different number of fields from the first. It usually points at an unquoted separator inside a value.
Does changing the separator break quoted fields?
No. Fields are re-quoted for the new separator, so a value containing the new character is wrapped in double quotes.
It says the bytes are binary. Why?
The payload is probably a real spreadsheet file rather than CSV text. Save it with Base64 to File and open it in Excel.
Will Excel open the download directly?
Yes, though for non-ASCII names you may want a byte order mark, which the CSV to Base64 tool can add on the encoding side.