Formula Parse Error in Google Sheets: What It Means and How to Fix It
No time for long YouTube tutorials? Try Guidy and get it all done in minutes. It sits right on your screen and points you to exactly what to do in real time. And it works on any software or browser, in any language.
Try for free
A formula parse error means Google Sheets could not read what you typed. It is not saying your logic is wrong or your data is bad. It is saying the formula is not valid as a piece of writing, in the same way a sentence missing a closing bracket is not valid. Sheets shows this as #ERROR! in the cell, and hovering over the small red triangle in the corner reveals the words "Formula parse error." That message is famously unhelpful because it never says which part it could not read. Here are the seven things that cause it, in the order you should check them.
1. Mismatched parentheses
The single most common cause. Every opening bracket needs a closing one, and long nested formulas make it easy to lose count.
Click into the cell and look at the formula bar. Google Sheets color-codes matching pairs of brackets, so put your cursor next to an opening bracket and its partner will highlight in the same color. A bracket with no colored partner is your problem.
If the formula is long, break it apart. Copy the innermost function into a spare cell on its own and confirm it works, then rebuild outward one layer at a time.
2. The wrong separator for your locale
This one catches people constantly and almost nobody suspects it.
Most people write =SUM(A1,B1) with a comma. But Google Sheets uses the separator that matches your spreadsheet's locale, and many European locales use a semicolon instead. In those settings, =SUM(A1,B1) throws a parse error and =SUM(A1;B1) works.
You will hit this when you copy a formula from a website written for a different region, or when you open a file created by someone in another country.
To check your locale, go to File, then Settings, then look at the Locale dropdown. Either change it to match the formulas you are pasting, or swap the separators by hand.
There is a quicker trick for a one-off formula. Temporarily set the locale to United States or United Kingdom, paste the formula in, then set the locale back to your own. Sheets converts the separators for you and the formula keeps working.
3. Missing quotation marks around text
Any text inside a formula must be wrapped in double quotes. Numbers and cell references must not be.
=IF(A1>10,High,Low) fails. =IF(A1>10,"High","Low") works.
Watch for smart quotes as well. If you copied a formula out of an email, a document, or a web page, the straight quotes may have been converted into curly typographic quotes, which Sheets does not recognize. They look nearly identical in the formula bar. Deleting them and retyping the quotes directly in Sheets fixes it.
4. An extra or missing comma
Usually created while editing. Deleting an argument from the middle of a function often leaves a stray comma behind, and =SUM(A1,,B1) will not parse.
Read the formula from left to right and count the arguments. If a function expects three and you have supplied four separators' worth of gaps, that is the fault.
5. Concatenation written incorrectly
Joining text is a reliable source of this error. The ampersand joins values, and any literal text still needs quotes.
=A1&" "&B1 works and puts a space between two cells. =A1& &B1 does not, because the space in the middle is not quoted. =A1+" "+B1 does not either, because plus is arithmetic rather than joining.
6. Symbols that do not belong inside a formula
Currency symbols, percent signs, and thousands separators typed into a formula rather than applied as formatting will break it.
=A1*$5 fails. Write =A1*5 and format the cell as currency instead. The same applies to =A1*20% in some cases, and writing =A1*0.2 avoids the argument entirely.
7. A named range or sheet name with spaces
Referencing another tab whose name contains a space requires single quotes around the name.
=Sales Data!A1 fails. ='Sales Data'!A1 works.
If you have renamed a tab recently and formulas that used to work have started failing, this is usually why.
How to find the fault faster
Three habits that shorten the hunt considerably.
Build up, do not write out. Start with the innermost function, confirm it returns something, then wrap the next layer around it. You will catch the error at the moment you introduce it rather than at the end.
Use the formula bar's expansion arrow. Click the small arrow at the end of the formula bar to expand it into a multi-line view. Long formulas become readable and mismatched brackets become obvious.
Delete and retype the suspicious section. Faster than staring at it, and it eliminates invisible characters such as smart quotes and non-breaking spaces that no amount of reading will reveal.
When it is not a parse error at all
Google Sheets has several errors that people lump together, and each means something different. #N/A means a lookup found nothing. #REF! means a reference points at a deleted cell. #VALUE! means the wrong type of data went into a function. #NAME? means a function name is misspelled or unrecognized. Only #ERROR! is a parse error, and only that one means Sheets could not read the formula in the first place.
A precise message that does not tell you where the problem is describes most spreadsheet errors, and reading a formula back to yourself rarely reveals what your eyes have already skipped over. Guidy reads your actual sheet, points at the part of the formula that will not parse, and walks you through correcting it in place. It works the same way in Excel and across the other tools where a small error costs a large amount of time, which is covered on our AI assistant for work page.
Key takeaways
● A formula parse error means Google Sheets could not read what you typed. It is a grammar problem rather than a logic or data problem, and it shows as #ERROR! in the cell.
● Mismatched parentheses are the most common cause. Sheets color-codes matching pairs in the formula bar, so a bracket with no colored partner is your fault line.
● Argument separators depend on your locale. Many European locales use a semicolon, so =SUM(A1,B1) fails where =SUM(A1;B1) works. Check File, then Settings, then Locale.
● Smart quotes copied from an email or a web page look nearly identical to straight quotes and will not parse. Delete them and retype the quotes directly in Sheets.
● Only #ERROR! is a parse error. #N/A means a lookup found nothing, #REF! means a deleted reference, #VALUE! means the wrong data type, and #NAME? means an unrecognized function.
FAQs
What does formula parse error mean in Google Sheets?
It means Sheets could not read your formula as valid syntax. The problem is how the formula is written rather than what it calculates, most often a mismatched bracket, a missing quotation mark, a stray comma, or the wrong argument separator for your locale.
Why does my formula work for someone else but not for me?
Almost always the locale separator. Some regions use commas between arguments and others use semicolons, and a formula written for one will not parse in the other. Check File, then Settings, then Locale, and either match it or swap the separators manually.
How do I find the mismatched bracket in a long formula?
Click into the cell and place your cursor beside an opening bracket. Google Sheets highlights its matching partner in the same color. Any bracket without a colored match is the culprit. Expanding the formula bar with the arrow at its right end makes this much easier on long formulas.
Why does my formula break after I paste it from a website?
Two likely reasons. The quotation marks may have been converted to curly typographic quotes, which Sheets does not recognize, and the formula may use a different argument separator than your locale expects. Retyping the quotes directly in Sheets fixes the first.
What is the difference between #ERROR! and #VALUE! in Google Sheets?
#ERROR! is a parse error, meaning the formula could not be read at all. #VALUE! means the formula was read correctly but received the wrong type of data, such as text where a number was expected. They need completely different fixes.
