Skip to main content
Tools Harbor

Data Converters

Convert between JSON, CSV, YAML, Base64, URL and HTML-entity formats.

Pick the converter that matches your destination

Conversion is usually forced by whatever has to read the data next. Spreadsheets and most bulk-import screens want rows, so the JSON to CSV Converter flattens an array of objects and detects headers for you. Config files and CI pipelines tend to want YAML, which the JSON to YAML Converter produces in both directions. When data has to survive a transport that only tolerates plain text — an env var, a JSON string field, an email header — the Base64 Encoder / Decoder is the usual answer. Anything going into a URL needs the URL Encoder / Decoder so that spaces, ampersands and slashes do not terminate a parameter early. Text being dropped into markup needs the HTML Entity Encoder / Decoder. And when you want to avoid a network request altogether, the Data URI Generator inlines a small asset directly into your CSS or HTML.

Where conversions usually go wrong

CSV has no type system, so everything arrives as text and a leading zero in a ZIP code or product ID will be eaten by the next spreadsheet that opens it. Nested JSON has no natural CSV representation at all, so decide deliberately whether to flatten with dotted keys or split into several files. YAML is whitespace-significant and reads tabs as an error. Base64 is an encoding, not encryption — it is trivially reversible and should never be used to hide a secret. Data URIs grow roughly a third larger than the file they encode, which makes them a good trade for a small icon and a bad one for a photograph.

Converting without handing over the data

The usual online converter uploads your file to a server, converts it there and asks you to trust the deletion policy. These run entirely client-side, which is the difference between pasting a customer export into a form and never letting it leave the machine. No upload, no account, no retention.