CSV CSV

CSV Converter

Convert CSV to and from various formats

Convert CSV to other formats

Convert to CSV

View all document converters →

About CSV

CSV files store data in comma-separated values, perfect for importing into spreadsheets and databases.

Common Uses

  • Data import/export between applications
  • Database exports and backups
  • Simple data storage and exchange

CSV Conversion FAQ

What is a CSV file?
+
CSV (Comma-Separated Values) is a text file format for storing tabular data.
Only into another real spreadsheet format. Convert CSV to a spreadsheet and formulas, references and named ranges round-trip intact. Convert to a flat data or page format and every cell is frozen at its last computed value — the number stays, the calculation behind it does not. That is usually what you want for sharing and never what you want for continued work. A CSV is plain text where each line is a row and a delimiter separates fields, with quoting rules that vary between producers.
Because the program guessed the wrong separator. Nothing in the file announces which one it uses, so a spreadsheet applies a regional default — a comma in some locales, a semicolon in others — and when the file disagrees, every line arrives as a single cell. The same absence of a declaration is why accented characters sometimes turn into symbols: the encoding is not recorded either. Both are import settings, not damage. CSV stores exactly one flat sheet with no formulas, no formatting, no types and no multiple tabs, and delimiter or encoding mismatches corrupt it silently.
Because it is what the software on the machine saves by default, and defaults decide almost everything about which formats spread. The awkward cases are the predictable ones: a recipient on different software, an older version, or a system that only accepts one specific format for upload. All three are one conversion away from working. CSV is comma-separated values, the oldest and least specified tabular interchange format still in daily use.
It depends whether the target knows what a sheet is. Another workbook format keeps them all, in order, with their names. A flat data format keeps exactly one, normally the first, and drops the rest without comment — the single most common way to lose data in a spreadsheet conversion. A page format renders each sheet in turn, so nothing is lost, but nothing stays calculable either.
Because a grid cannot reflow. Text rewraps to a narrow screen; a row of eighteen columns cannot, so the choice is scrolling sideways or shrinking everything until the numbers are unreadable. Converting to a fixed page keeps the grid and makes zooming predictable; converting to a document turns each sheet into a table that reads properly in one column, at the cost of being able to recalculate anything.
Age itself is not the problem — several formats from that era are still perfectly good, precisely because everything has had decades to implement them. What matters is what the era assumed: small files, modest processors, no network, and features nobody needed yet. Where those assumptions still fit, the format is fine. Where they do not, that is the reason to convert.
That depends entirely on the target. Converting to another editable document format keeps the structure — styles, headings, tables — so work continues normally. Converting to a page or image format produces something for reading rather than writing, and getting back from there means a second conversion that reconstructs structure rather than restoring it. Keep the CSV as the working copy either way.
Nobody, and that is the point of it. The specification is public, anyone may implement it without asking or paying, and no company can change the terms later — which is why archives, standards bodies and public institutions specify formats like this one for anything that still has to open in twenty years. The trade is not compatibility, which is excellent; it is that there is no vendor to call when some tool implements the spec badly.
With an account, yes — drop them in together and they are queued as one job rather than handled one at a time, with the same settings applied across the batch and the results returned together. Free conversions run a single file at a time (merge tools take two); a paid plan is what unlocks batch processing and the larger per-file limit, which is what makes converting a whole archive practical.
It is deleted. The upload and the converted result both sit on the server only as long as the job needs them and are then removed automatically; the transfer runs over HTTPS in both directions. Nobody reads the contents, nothing is indexed, and nothing is passed to anyone else. If you would rather not wait for the automatic sweep, closing the job removes the files immediately.
Usually seconds. Small files are effectively instant, and the cases that take real time are the ones doing real work: a long recording that has to be re-encoded frame by frame, a scanned document going through character recognition, or a very large batch. Where a conversion only rewraps or repackages the existing data it stays fast no matter how big the file is, because nothing is being decoded.

Other Converters


Rate this tool
4.4/5 - 17 votes
ns6.com — Free WHOIS privacy, DNS and SSL on every domain.