CSV EXPORT / A PRACTICAL GUIDE

Keep IDs intact.
Review formulas.

CSV stores text values without spreadsheet cell types. That makes it portable, but it also means the next application may interpret an identifier as a number, a date-like value as a date, or a formula-like value as a calculation.

Why an ID like 00124 loses its zeros

CSV Ready reads and writes 00124 as text. It does not convert the value to 124. However, opening a CSV directly in spreadsheet software can trigger automatic type detection. Quoting the field in CSV does not reliably force a spreadsheet to keep it as text.

Use the destination’s text/CSV import workflow and choose Text for identifier columns before completing the import. Check the preview for leading zeros, long IDs, postal codes, and date-like values. The exact menu names depend on your spreadsheet version.

CSV Ready preserves the text it receives. If another application already removed zeros or rounded a long identifier, this tool cannot reconstruct the original values.

Cleanup can change identifiers too

Outer spaces may be meaningful. Trimming is off by default and affects every cell, including header names. Deduplication compares complete data records as text after trimming, when trimming is selected. It never merges records by a guessed identifier or treats 00124 and 124 as the same value.

Review the change counts and output preview before downloading. The preview shows at most 50 data records and shortens long displayed cells; the downloaded file contains all retained records and complete values within the tool’s limits.

Formula-like text deserves a second look

Spreadsheet applications can interpret cells beginning with characters such as =, +, -, or @ as formulas. CSV Ready displays data as plain text and never executes formulas. It flags conservative formula-like patterns, including values such as negative numbers that may be perfectly legitimate.

The optional apostrophe prefix changes each flagged value by adding ' at the start. Some spreadsheet import paths treat that as a text marker; others retain it literally or behave differently. Keep the option off when exact values are required by a data importer, and use the destination’s controls to prevent formula evaluation.

A prefix is not a universal sanitizer. Review untrusted data and the destination’s import behavior. Saving and reopening a spreadsheet can change how escaping is interpreted. Do not treat a CSV Ready check as a malware or security clearance.

Encoding is separate from cell types

Downloads use UTF-8. The optional UTF-8 byte order mark (BOM) can help readers recognize the encoding; it does not preserve leading zeros or prevent formulas. Leave it off if your destination requires a BOM-free file.

File input defaults to strict UTF-8, or UTF-16 when a UTF-16 BOM is present. If decoding fails, choose the file’s actual encoding and reopen it. UTF-16 without a BOM requires a manual choice. Windows-1252 is available for known legacy exports; a wrong choice can still create incorrect text, so inspect accented characters in the preview.

Choose the right handoff

Comma-separated CSV is common for app imports; TSV separates fields with tabs. Both exports use double-quoted fields when separators, quotes, or line breaks occur inside a value, and CRLF record endings. Check whether your receiving app accepts that dialect.

CSV Ready checks structure and offers bounded cleanup. It does not read Excel workbooks, infer schema types, validate business rules, or modify your original file.

Need help with uneven rows? Read the CSV structure guide.

Further reading: OWASP’s CSV injection guidance and Microsoft’s text/CSV import documentation.