Value Errors in Excel

“value errors in excel” comes up constantly, so this page leads with the exact answer, and only then explains the detail. Everything works in Excel on Windows and Mac and maps almost one-to-one to Google Sheets. Copy the answer above and get back to work, or read on to turn a one-off fix into something you never have to look up again.

Exact answer

In Excel: #VALUE! means an argument is the wrong TYPE — nearly always text, or a character that looks like a space, where a number was expected.

Annotated stepsExcel
1

Select the failing cell and use Formulas ▸ Error Checking ▸ Trace Error to see which argument is at fault.

2

Test the suspects: =ISTEXT(B2) exposes a stored string, =LEN(B2) exposes trailing characters, =CODE(RIGHT(B2,1)) returns 160 for a non-breaking space.

3

Clean the range with TRIM and SUBSTITUTE(…,CHAR(160),""), or repair it in place with Data ▸ Text to Columns ▸ Finish.

4

Check the ranges of any array formula match in size — a 40-row range multiplied by a 39-row one raises the same error.

5

Only once the cause is fixed, wrap the formula in IFERROR to keep a report tidy.

Ctrl+CthenCtrl+Shift+V+Cthen+Ctrl+VPaste values · WindowsMac

Need it as an auditable file?

Ships inside the linked template — formula-driven, unlocked, audit-ready.

View template

What this does

Excel raises #VALUE! when arithmetic meets something it cannot coerce into a number. The usual sources are imported figures stored as text, dates that never parsed, an invisible non-breaking space (CHAR(160)) pasted from a web page, and array operations across ranges of mismatched size. It is a type complaint, not a lookup failure — that is #N/A — and the fix is to repair the input rather than to hide the message. Most people learn this as a sequence of clicks and forget it by next week; learning it as a pattern instead is what lets you apply it to the next, slightly different version of the problem without starting from scratch. That is the difference this page is trying to make. For “value errors in excel”, the reliable version is a short checking loop, not just the first command that appears to work. Run it on a deliberately small range first, watch how the affected cells change, and only then apply the same setup to the full sheet. When this is a ribbon command, the selection matters more than the button: confirm the range, apply the command, then spot-check the output before saving. That is what makes a calculation you can defend to a CFO or an auditor useful in real work: repeatable, auditable, and not dependent on memory or luck.

A worked example

C2 holds =A2-B2 and returns #VALUE! because B2 contains "1,250 " as text from a web paste. =ISTEXT(B2) confirms it and =LEN(B2) returns 6 where 5 was expected. =VALUE(SUBSTITUTE(SUBSTITUTE(B2,CHAR(160),""),",","")) returns 1250 as a real number, and Data ▸ Text to Columns ▸ Finish fixes the whole column in one pass. A #VALUE! that gets suppressed instead of diagnosed turns a visible error into an invisible one, and the number keeps being reported. One habit worth forming early: name the cells that hold your inputs, so the formula reads in plain language instead of a string of cell addresses. A reviewer — or you in three months — can then follow the logic without decoding what B7 and D2 were supposed to mean, which is most of what makes a sheet maintainable.

In Google Sheets

Google Sheets handles this almost identically to Excel. The formula syntax above is the same, and the menu lives under a slightly different label rather than a ribbon tab. Use the platform toggle at the top of the page to switch every keyboard shortcut between Windows and Mac, and expect at most cosmetic differences in naming. Keep this page bookmarked for the next time the same question comes up. Better still, rebuild the example once in your own sheet — doing it yourself, with the tool above to check against, is what turns a copied formula into a technique you own. If you take one thing from this page on “value errors in excel”, make it the habit rather than the keystrokes: set the problem up with labelled inputs, reference those cells, and let Excel do the recomputing. Bookmark the page for the syntax, but do the example once in a blank sheet and check it against the tool above — five minutes of hands-on practice fixes the method in memory far better than re-reading, and it surfaces the small snags while they are still harmless. After that the technique is genuinely yours: faster than searching for it again, and reliable enough to drop into work that other people depend on.

Common mistakes

  • Wrapping the formula in IFERROR first, which hides a real data fault and lets the wrong total ship.
  • Replacing + with SUM to make the error disappear: SUM silently ignores text, so the result is quietly too low.
  • Expecting TRIM to remove a non-breaking space — it only strips ordinary spaces, so CHAR(160) needs SUBSTITUTE.
  • Assuming a right-aligned cell must be numeric; alignment can be set by hand and proves nothing.

Frequently asked questions

What is the difference between #VALUE! and #N/A?

#VALUE! means an argument has the wrong type. #N/A means a lookup found nothing. They have completely different fixes.

How do I find which cell causes it?

Formulas ▸ Evaluate Formula steps through the calculation and shows the exact operand that fails, and Trace Error draws arrows to the suspects.

Why does SUM work when + fails?

SUM ignores text values in its range, while the + operator tries to coerce them and errors. That difference is why a total can look fine and still be wrong.

Can I just hide it?

Yes, =IFERROR(formula,"") does that, but only do it after the underlying data is fixed.