Free · No signup · Runs in your browser

Base64 a CSVColumn

Encode or decode a single column to Base64 without uploading your file anywhere.

01 · How it works

Three steps, then done.

Pick a column, choose encode or decode, and download the result. Everything runs locally in your browser — no server, no upload, no trace.

1

Load your CSV

Drop in or paste your CSV. The tool reads it entirely in your browser and lists every column for you to choose from.

2

Pick a column and mode

Select the column, then choose Encode to turn values into Base64 or Decode to turn Base64 back into text. Tick Keep original to write to a new column instead of overwriting.

3

Export the result

Download a clean RFC-4180 CSV with the Base64-encoded or decoded column. Round-trips are lossless and UTF-8 safe.

02 · Why ours

Why Base64 a CSV columnin the browser

Base64 is the standard way to move text and binary-ish payloads through systems that only accept plain ASCII. Doing it client-side keeps sensitive values on your machine.

  • 01

    UTF-8 safe

    Accents, CJK characters, and emoji survive a full encode/decode round-trip. The encoder converts to UTF-8 bytes before encoding, so nothing gets corrupted.

  • 02

    Lossless round-trip

    Encode then decode returns the exact original string. Empty cells stay empty, and invalid Base64 is passed through untouched instead of throwing.

  • 03

    Keep or replace

    Replace the column in place for a quick transform, or add a new _base64 / _decoded column so you keep the source values alongside the result.

  • 04

    Fully private

    No backend, no upload, no logging. The CSV is parsed and transformed entirely in your browser tab, so confidential columns never leave your device.

"Base64 belongs at the edge — encode the column on your own machine and only the encoded bytes ever travel."
csvtodashboard.com
03 · FAQ

base64 column questions.

Does this handle non-ASCII text like accents or emoji?
Yes. Values are converted to UTF-8 bytes before Base64 encoding (the encodeURIComponent + btoa pattern), so characters like é, ñ, 日本語, and emoji encode and decode without corruption.
Empty cells stay empty. They are not encoded into a Base64 representation of an empty string, so your blanks remain blank in both directions.
The decoder tolerates it: if a value can't be decoded as Base64, the original text is passed through unchanged instead of erroring, so one bad cell won't break the whole export.
Yes. Enable Keep original column and the tool adds a new column (named column_base64 when encoding or column_decoded when decoding) while leaving the source column intact.
No. The entire process is 100% client-side. Your CSV is read, transformed, and exported within your browser — nothing is sent to a server.