You've built a file in Excel or Google Sheets, you choose to import it in Google Ads Editor, and instead of a nice preview you get "Missing CSV header", or a preview where every column has been squeezed into one. The file looks fine when you open it. Editor just can't read it.
Before an Editor import in my accounts, the file usually goes through a check, and the first thing that check looks at is the format. That's not because format is the most interesting part. It's because that's where an import most often goes wrong before it has even started, and it's often one of three things.
What Editor expects from the first row
Google's own guide to preparing a CSV file is quite clear on this. Editor treats the first row in an imported file as the column header row, and you have two options: use Editor's own column names, which Google recommends, or use your own and pick the right column in a dropdown when you import.1
That second option sounds flexible, and it is. The catch is that Editor can only offer you the dropdown if it has managed to split the first row into columns at all. If the separator is wrong, there's only one column to choose from, and the whole header row sits in it as one long string of text.
Cause 1: the wrong separator
CSV stands for comma-separated values, so it's reasonable to think a comma-separated file is what Editor wants. In practice, the file Editor exports itself is separated by tabs, and a file that's split differently from what Editor expects is one common reason it can't find the header.
It gets worse in Europe. If your computer uses a comma as the decimal separator, as it does in Danish, German, Dutch and a lot of other settings, Excel will usually save a "CSV" file with semicolons instead, because the commas are taken by the numbers. The file is called .csv and opens fine in Excel, but neither Editor nor anyone else can tell what it's actually split by without looking.
The fix is to save the file as tab-separated text, which brings us to the second cause.
Try it
What Editor sees in your first row
The row is split by commas, but Editor expects tabs, so it sees one column with the whole row in it.
Check the whole file, encoding and all, in the Editor CSV checker →Cause 2: the wrong encoding
Encoding is how the letters in the file are stored. It doesn't matter much as long as everything is plain English. It matters a lot as soon as you have æ, ø, å, ä, é or ü in a headline, a campaign name or a keyword.
Google's advice is to save the file with Unicode Text encoding if you create or edit it in Excel. On Windows, that's Save As and then Unicode Text. On a Mac, it's Save As and then UTF-16 Unicode Text.1 The file extension may change from .csv to .txt, and according to Google, Editor can still import it. That format is UTF-16 with tabs between the columns, which happens to be exactly what Editor exports.
Google also says plainly that Editor doesn't import XLS files1, so the file has to be saved as text first.
Cause 3: column names that don't match
If the file is split and encoded correctly, but Editor still doesn't recognise your columns, look at the names in the first row. A space too many, "Headline1" instead of "Headline 1", or a column name in another language will all leave Editor guessing.
A column name that appears twice is easy to miss when you copy columns between sheets, so check for it too.
The template that imports every time
Formula
A file that imports cleanly = UTF-16 + tabs + Editor's own column names
The safest way I know to build an import file is to start from a file Editor has made itself. Select a few rows of the type you want to import, such as a handful of keywords or ads, and export them from Editor as CSV. That file has the right encoding, the right separator and the right column names, because Editor wrote all three. Build your rows in that file, keep the format when you save, and the header problem is gone.
If you work in Google Sheets, it's worth checking the exported file before you import it, not just the sheet. What you see in the sheet is not what Editor gets.
One more thing worth checking: decimals
While you're in the file, look at your numbers. A file that mixes comma and point as the decimal separator can leave a bid or a budget off by a factor of 10 or 100, and unlike the header problem, that one doesn't give you an error. It just imports. I've seen it happen, and of the two problems, this is the dangerous one.
How the checker helps
The Editor CSV checker looks at the file before Editor does. It checks the extension, that the file is UTF-16 with a byte order mark, that the columns are separated by tabs, the line endings, duplicate column names and mixed decimal separators. After that it moves on to the content: character limits, the three-ad cap per ad group and the rows that decide whether Editor updates your ads or adds new ones.
It runs in your browser, so the file is never uploaded anywhere. You can also try it on a sample file with mistakes in it first, if you'd like to see what it finds.
Frequently asked questions
Can Google Ads Editor import an Excel file?
Not as an Excel file. Google says Editor doesn't import XLS files1, so save it as text first, ideally as UTF-16 Unicode Text with tabs.
Why does the import preview show everything in one column?
Because Editor couldn't split the rows into columns. It's usually the separator: the file is split by commas or semicolons, and Editor expected tabs.
Do I have to use Editor's exact column names?
No, but Google recommends it. If you use your own names, you can pick the right column for each one in the import dialog2, as long as Editor could split the header row into columns in the first place.
My file imported, but some rows are missing. Is that the same problem?
No. That's usually rows Editor skipped, such as a fourth enabled ad in an ad group or an identical ad. Compare Editor's Added, Updated and Skipped numbers after the import.
Sources
- Google Ads Editor Help: Prepare a CSV file (the header row, Editor's own column names, Unicode Text and UTF-16, no XLS files)
- Google Ads Editor Help: Import a CSV file (choosing from a file or pasting text, and correcting headers in the import dialog)
The sources were last checked on 9 November 2026.

