Keep leading zeros and long IDs as XLSX text cells
Leading zeros and long identifiers may define a record instead of representing a number for calculation. Preserve them as text while the original characters are still available.

How to use this tool
- Add the spreadsheet and name the identifier columns.
- Use 0 for unchanged length or enter a documented padding width.
- Choose XLSX output, run the task and compare source characters.
- Download the result with text cells.
Choose the right settings
Specify the identifier columns and enter 0 to retain their existing length without padding. Set a width only for a documented code rule, and choose XLSX output for text cells.
- Supported input
- CSV,TSV,XLSX
- Available settings
- Columns (comma separated)
- Digit padding (0: unchanged)
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
code 00123 → text cell "00123" in XLSXExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare identifiers with leading zeros and long numbers against the source through their final digits. When padding is enabled, confirm that the added zeros match the actual identifier convention.
If the result is different from what you expected
Zeros already lost or digits already truncated cannot be reconstructed from damaged values by this tool. If opening CSV converts them again, use XLSX text cells or configure the receiving program's import types.
Limits to keep in mind
- XLSX output uses text cells. Already lost zeros or truncated IDs cannot be recovered.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.