How to Import CSV into Google Sheets Without Losing Formatting

Quick fix

• File → Import → Upload your CSV.
• Uncheck “Convert text to numbers, dates, and formulas” to keep leading zeros, long IDs, and codes intact.
• Set the separator manually (comma, semicolon, or tab) if everything lands in one column.
• Match File → Settings → Locale to the file’s date and decimal format, and save the CSV as UTF-8.

To import a CSV into Google Sheets without losing formatting, open File → Import, upload the file, and turn off “Convert text to numbers, dates, and formulas” when identifiers, dates, or codes must remain exactly as written. Then verify the delimiter and spreadsheet locale before using the data. This prevents the most common problems: missing leading zeros, altered dates, scientific notation, and formulas created from plain text.

A CSV stores characters and separators, not spreadsheet formatting. It cannot preserve fonts, colors, formulas, or column types. Google Sheets therefore guesses whether each value is text, a number, a date, or a formula during import. Those guesses are convenient for simple files but dangerous for SKUs, ZIP codes, phone numbers, transaction IDs, international dates, and financial exports. Use the symptom guide below to diagnose the problem, then follow the detailed fix.

CSV formatting problem: quick diagnosis

• 00123 becomes 123: automatic number conversion removed the leading zeros. Import with conversion disabled or keep the destination values as Plain text.
• 1234567890123456 becomes 1.23457E+15: Sheets treated a long identifier as a number and may have lost digits. Re-import it as text from the original CSV.
• 02/04/2026 becomes the wrong date: the spreadsheet locale does not match the date order in the source file.
• José becomes José or �: the CSV character encoding is not being read as UTF-8.
• Every row appears in one column: Sheets detected the wrong delimiter, often comma instead of semicolon or tab.
• 12,50 becomes 1250 or text: the decimal separator in the CSV conflicts with the spreadsheet locale.
• A value beginning with = changes or behaves like a formula: automatic formula conversion was enabled during import.

Use the safest Google Sheets CSV import settings

1. Keep an untouched copy of the original CSV so you can repeat the import if Sheets changes a value.
2. Open the destination spreadsheet and choose File → Import → Upload.
3. Select the CSV and choose the import location you need. For testing, inserting a new sheet keeps the existing workbook safe.
4. Set Separator type to Detect automatically only when the preview separates every field correctly. Otherwise choose comma, semicolon, tab, or Custom.
5. Turn off “Convert text to numbers, dates, and formulas” when the file contains IDs, postal codes, phone numbers, version numbers, ambiguous dates, or text beginning with =.
6. Complete the import, compare several rows with the original CSV, and check totals before replacing or merging production data.

Disabling conversion prioritizes fidelity: values arrive as text instead of becoming usable dates or numbers immediately. That is usually the safest first step. After checking the import, convert only the columns that genuinely need calculations. This is more reliable than asking Sheets to infer every column correctly at once.

Keep leading zeros in ZIP codes, SKUs, and phone numbers

Leading zeros disappear because Sheets interprets 00123 as the number 123. But a ZIP code, SKU, employee ID, or phone number is an identifier, not a quantity. You do not add or average it, so it should remain text.

1. Repeat the import from the original CSV.
2. In the import dialog, disable “Convert text to numbers, dates, and formulas.”
3. Confirm that values such as 00123 still contain five characters after import.
4. If you are pasting into an existing sheet instead, select the destination column first and choose Format → Number → Plain text before pasting.

Quoting a value in the CSV, such as "00123", identifies a field boundary but does not guarantee that Sheets will preserve its type. The import conversion setting or a Plain text destination is the stronger protection. A custom number format such as 00000 can make 123 display as 00123, but it does not restore unknown original zeros and is unsuitable when identifiers have different lengths.

Prevent scientific notation and lost digits in long numbers

Tracking numbers, order IDs, card-like references, and other long digit strings may display as scientific notation. More importantly, spreadsheets preserve only limited numeric precision, so a long identifier can be permanently rounded when it is imported as a number. Treat any digit string longer than 15 digits as text.

1. Do not repair the rounded value in the imported sheet; return to the original CSV.
2. Import again with automatic number, date, and formula conversion disabled.
3. Check the first and last digits against the source file, not just the scientific-notation display.
4. Keep the column as Plain text when sorting, filtering, exporting, or joining it with other data.

Fix wrong dates without day-month swaps

Dates such as 02/04/2026 are ambiguous: they can mean February 4 or April 2. Sheets interprets them using the spreadsheet locale. An import can therefore look valid while every day and month is reversed. The safest source format is ISO 8601, written as YYYY-MM-DD, because 2026-04-02 has only one interpretation.

1. Before import, identify whether the source uses MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD.
2. In Google Sheets, open File → Settings and set Locale to the region that matches the source data.
3. Import the CSV and inspect dates where both the day and month are 12 or lower; those are the values most likely to be silently reversed.
4. Apply Format → Number → Date only after Sheets has interpreted the underlying values correctly.

If preserving the exact date text matters more than date calculations, disable conversion during import. You can normalize the verified text in a separate column later. Changing the display format after a date was misinterpreted only changes how the wrong date looks; it does not correct the underlying day and month.

Fix garbled characters by converting the CSV to UTF-8

Text such as José, Zürich, £, €, an em dash, or non-Latin characters can become José, question marks, or replacement symbols when the CSV was saved with Windows-1252, ISO-8859-1, or another encoding. Formatting cells in Sheets will not repair an encoding mismatch.

1. Open the original CSV in an editor that shows file encoding, such as VS Code or Notepad++.
2. Choose Save with Encoding or Convert to UTF-8. Prefer UTF-8 rather than a legacy regional encoding.
3. Save a new copy so the original remains available for comparison.
4. Import the UTF-8 copy and verify names, currency symbols, punctuation, and non-English text.

Fix a CSV that imports into one column

A file can have a .csv extension while using semicolons, tabs, or another character between fields. Semicolon-separated files are common when commas are used as decimal marks. If Sheets chooses the wrong separator, each entire row lands in one column.

1. Open the CSV in a plain-text editor and inspect the first two rows.
2. Identify the repeated separator between fields: comma, semicolon, tab, pipe, or another character.
3. Import again and set Separator type to that character. Use Custom for a pipe or another nonstandard delimiter.
4. Check quoted descriptions that contain commas. A valid CSV keeps those commas inside one field rather than splitting them into extra columns.

If the data is already in column A, select it and use Data → Split text to columns, then choose the correct separator. Re-importing is safer when fields contain quoted separators, because a simple split may not reproduce the CSV parser's handling of quotes and escaped characters.

Correct decimal separators and negative amounts

A US export may use 1,234.56 while a European export uses 1.234,56. If the sheet locale expects the other convention, amounts may arrive as text or change value. Accounting exports may also express a negative amount as (100.00), which Sheets may leave as text.

• Set the spreadsheet locale to match the file before converting amount columns to numbers.
• Confirm a known value and compare a column total with the source report before using the data.
• For parenthetical negatives imported as text, replace the opening parenthesis with a minus sign and remove the closing parenthesis in a separate cleanup column, then convert the result to a number.
• Do not run a global comma-to-period replacement until you know which character separates fields and which character marks decimals.

Protect text that begins with a formula symbol

CSV exports can contain text beginning with =, +, -, or @. When formula conversion is enabled, spreadsheet software may interpret that content instead of preserving it literally. Disable “Convert text to numbers, dates, and formulas” for untrusted files or fields that must remain exact text. Review unexpected formulas before sharing the imported spreadsheet.

How to verify the import before using it

• Compare row count and column count with the source export.
• Check the longest IDs and every identifier that begins with zero.
• Inspect ambiguous dates such as 03/04/2026 and compare them with the source system.
• Search for �, Ã, or question marks that may reveal an encoding error.
• Check known minimum, maximum, and total values in numeric columns.
• Sort a copy of the data to expose mixed text and numeric values, but keep the untouched import for reference.

When the one-click extension is the better workflow

If the CSV is already clean and you simply need it as a new spreadsheet, CSV to Google Sheets removes the repeated upload and import steps. Open the file as a new Sheet, verify the important columns, and then copy or reference approved data from a master workbook. For files with ambiguous dates, long IDs, or unusual delimiters, use the manual import controls above first so you can choose how Sheets interprets the data.

Clean CSV import checklist

• Keep the original CSV unchanged.
• Confirm the delimiter in the preview.
• Disable automatic conversion when exact text matters.
• Import long IDs, ZIP codes, SKUs, and phone numbers as text.
• Use UTF-8 for names, symbols, and international text.
• Match the spreadsheet locale to the source dates and decimals.
• Verify sample records, row counts, and totals before using the data.