DataSwap Fast file & data format converters, no signup

Convert the file without handing over the file

Twenty converters for CSV, JSON, XML, YAML, Markdown and PDF. Everything runs in your browser, so a contract, an export of customer records or an unsigned agreement is converted without ever being uploaded.

Search for a PDF or CSV converter and almost every result is the same deal: upload your file, wait in a queue, download the output, and trust a promise that the original is deleted in an hour. For a recipe that is fine. For an invoice, a payroll export or anything under an NDA, it is a data transfer to a third party that most people would not approve if asked directly.

These tools do the conversion locally using the browser's own file APIs. Nothing is uploaded, so there is no queue, no daily limit, and no retention policy to read — there is nothing on our side to retain.

Tabular Which one do I need? →

Markup Which one do I need? →

Config Which one do I need? →

PDF Which one do I need? →

From the blog

Launch notes and guides →

Data, markup, or PDF?

For tabular data, CSV to JSON and back covers most of the work between a spreadsheet and an API. The converter handles quoted fields, embedded commas and inconsistent line endings, which is where naive splitting on commas quietly corrupts a file and nobody notices until later.

For markup and config, JSON, XML, YAML and Markdown convert in both directions. The .env to JSON converter is the small one people search for at exactly the wrong moment, usually while wiring a config into a deployment.

For PDFs, the set covers the tasks people actually need: merge, split, compress, rotate, reorder pages, add page numbers or a watermark, and convert to and from JPG. Text extraction pulls the words out of a PDF that has them, which is most PDFs that were not produced by a scanner.

What running locally does and does not mean

It means the file never travels: it is read from your disk, transformed in memory, and written back out. Speed depends on your device rather than on a server's queue, so a large merge is fast on a laptop and slower on an old phone.

It also means a scanned PDF stays a scanned PDF. Extracting text needs text to exist in the file; a photograph of a page contains pixels, not characters, and recovering those needs OCR, which is a genuinely different job.

Common questions

Are my files uploaded to a server?

No. Every converter reads the file directly from your device and works on it in the browser. Nothing is transmitted and nothing is stored, which is the point: the files people convert are often exactly the files they should not be uploading to strangers.

Is there a file size limit?

No fixed limit, and no daily cap. The practical ceiling is your device's available memory, since the file is held in RAM while it is converted. Multi-hundred-megabyte PDFs are comfortable on a desktop and may struggle on an older phone.

Does the CSV converter handle commas inside fields?

Yes. It follows the RFC 4180 quoting rules, so quoted fields containing commas, line breaks or escaped quotes survive the round trip. This is the single most common way a hand-rolled CSV parser corrupts data.

Can I extract text from a scanned PDF?

Only if the scan has been through OCR already and carries a text layer. A pure image scan contains no characters to extract, and adding them requires optical character recognition, which these tools do not perform.

Does compressing a PDF lose quality?

It can, and the tool tells you what it did. Most of the saving usually comes from re-encoding embedded images, so a text-heavy document compresses well with no visible change while an image-heavy one trades some visual quality for size.