204 format conversions, none of them uploaded
Every conversion the network can do, laid out by what you are starting from. Pick your source format, then the thing you want out of it. Each link opens the tool on the site that owns the format — and like everything here, the file is read and rewritten inside your browser, so a spreadsheet full of customer records never travels anywhere.
From JSON
From PNG
From CSV
From TSV
From TOML
From JSONL
From XML
From PDF
From GeoJSON
From JPG
From YAML
From HTML
From JSON Schema
From NDJSON
From Text
From .env
From .properties
From AVIF
From Base64
From Excel
From Excel (XLSX)
From Fixed width
From INI
From Markdown
From SVG
From TIFF
From WebP
From BMP
From GIF
From GPX
From HTML table
From ICO
From Images
From JSON array
From JSON object
From JSON5
From JSONC
From KML
From OpenAPI
From Parquet
From Query string
From SQL
Why in-browser conversion is the safer default
A conversion site that works server-side needs your file. That means a copy of it exists on someone else's disk, at least until a cron job removes it, and it means the operator could read it. For a public dataset that is fine. For an export of your users' email addresses, a signed contract, or a photo with GPS coordinates in the EXIF block, it is a data transfer you did not intend to make.
Every converter listed above runs as JavaScript in your tab: the file is read with the File API, transformed in memory and offered back as a download. Turn off your network connection after the page loads and they still work — that is the practical test of the claim, and the reason there are no size limits or queue times here. The privacy note spells out what that means in detail.