When this workflow helps
A cleaner CSV can reduce duplicate records, trim accidental spaces and make a spreadsheet or database import more predictable. But the same operation can be helpful for one column and damaging for another: case may not matter in a tag, but it can matter in a product code or password-like identifier.
A step-by-step workflow
Learn to normalise whitespace and case, remove empty rows, detect column types and deduplicate CSV data while checking that meaningful values are preserved. Use the following sequence as a checklist; exact controls and supported formats are shown in the live tool.
Understand the columns and source
Check the header row, separator and a few representative records. Note which columns are identifiers, names, categories, dates, free text or numbers before applying global normalisation.
Trim and normalise selectively
Trimming surrounding whitespace is often safe, but changing case should be deliberate. Preserve case-sensitive IDs and values where it carries meaning. Removing empty rows can be useful, while removing empty cells may change the structure.
Inspect detected types
Automatic type detection can help spot dates, numbers and inconsistent values, but ambiguous data needs review. ZIP codes, account codes and IDs can look numeric while needing leading zeroes preserved.
Deduplicate and verify row counts
Decide which columns define a duplicate record. Two rows with the same email may not be duplicates if other fields describe distinct events. Compare input and output counts and inspect a few records before import.
Settings, quality and privacy checks
CSV is a text format with quoting and delimiter rules; commas inside quoted fields and line breaks inside cells should not be treated as simple separators. Use the intended delimiter and preserve headers. For sensitive or important datasets, keep the original and compare a sample or record count after cleanup.
Before using any browser tool with confidential material, check what the specific studio says about local processing, model downloads, external services and supported formats. Do not assume that every app has the same storage or network behaviour simply because it is linked from RuntimeHub.
Common mistakes to avoid
- Lowercasing an identifier or value where case matters.
- Treating numeric-looking IDs as numbers and losing leading zeroes.
- Removing duplicate rows based on too few columns.
- Assuming every comma or newline represents a new field or record.
A useful final habit is to keep the original input until you have opened the output and confirmed that it fits the intended destination. When the result will be submitted, published or used as evidence, inspect it in the actual application that will receive it.
Frequently asked questions
Why did a leading zero disappear from my CSV?
A spreadsheet or automatic type detector may interpret a value as a number. Identifiers such as postal codes and codes often need to remain text.
How should I define duplicates?
Choose the columns that uniquely identify a record for your task. Duplicate names alone may not mean two rows represent the same person or event.
Put the workflow into practice
Use LeanCSV to work through the ideas in this guide. Keep the source available, make the changes you need, and check the result before saving or sharing it.
- Start with the file or information you want to work on.
- Use the available controls to shape the result.
- Preview the output before saving or sharing it.