IFERROR — The Protective Clause

Syntax breakdown

IFERROR takes just two arguments. Both are required.

Five working examples

Every example uses the same 24-row sales log as the IF and IFS family pages. Same Q1 2026 data, plus supplementary tables for quota and product-code demonstrations.

The cascade pattern, visualized

Nested IFERROR is the pattern most beginners struggle with. Here's exactly how Excel reads a 2-level cascade — one attempt at a time, falling through on error:

The 7 Excel error types, side-by-side

Excel has exactly 7 error types. Here's what each one means, what causes it, whether IFERROR/IFNA/ISERROR catch it, and whether wrapping is even the right response:

IFERROR vs IFNA vs ISERROR — a three-way comparison

Three functions in the "check for errors" family. Same problem, different tools. When to reach for which:

Interactive playground

The IFERROR cheat sheet — 10 patterns for daily use

Copy any of these, adapt the ranges to your data, and you're covered for the most common IFERROR scenarios:

Common IFERROR pitfalls

IFERROR itself rarely errors — but the way people use it does. Six scenarios to avoid:

IFERROR is IF, specialized for errors

Companion functions worth knowing

Natural wrap targets — functions IFERROR commonly guards

Excel version compatibility

IFERROR shipped in Excel 2007. For older versions, use the IF+ISERROR pattern:

When to use IFERROR vs. alternatives

Use IFERROR when…

• Multiple error types are expected. A formula that could DIV/0 AND miss a lookup.
• You want compact syntax. Cleaner than IF+ISERROR.
• Cross-version compatibility matters. Works in Excel 2007+ everywhere.

Use IFNA instead when…

• You're wrapping a VLOOKUP, XLOOKUP, MATCH, or INDEX/MATCH.
• The ONLY expected failure is "not found."
• You want other bugs (REF, VALUE, NAME) to surface as they should.

Use XLOOKUP's built-in fallback instead when…

• You're on Excel 365 or 2021 and using XLOOKUP anyway.
• The 4th argument of XLOOKUP is a native "if not found" — no wrap needed.

Use IF+ISERROR (legacy) when…

• You must support Excel 2003 or earlier.
• The success and error branches need genuinely different logic (like multiplying success by 2, or logging errors somewhere).

Don't wrap at all when…

• The error indicates a real bug (REF, VALUE, NAME) — fix the bug instead.
• The formula can't produce an error (wrapping a constant is pointless).

How IFERROR actually works

The algorithm

IFERROR evaluates the first argument. If the result is any of the 7 error values (#DIV/0!, #VALUE!, #REF!, #NAME?, #N/A, #NULL!, #NUM!), IFERROR discards it and evaluates the second argument instead. Otherwise, it returns the first argument's value.

Short-circuit evaluation

The second argument is only evaluated if the first errors. This matters when the fallback is expensive — like another VLOOKUP or a complex calculation. In a cascade like IFERROR(A, IFERROR(B, C)), C is only computed when both A and B fail.

The value once — vs the legacy pattern

IFERROR evaluates value exactly once. The legacy IF(ISERROR(x), fallback, x) pattern evaluates x twice — once for the ISERROR check, once for the return value. For complex formulas (large VLOOKUPs, nested SUMIFS), this doubles the calculation cost. IFERROR is measurably faster on real workbooks.

What "error" means to IFERROR

• Excel errors: the 7 hash-prefixed values are all caught.
• Empty cells: NOT errors. IFERROR passes empty results through.
• Zero: NOT an error. Only DIV/0 is; a legitimate 0 result is returned as-is.
• Text where number expected: depends — some functions coerce, some return VALUE.

Performance notes

IFERROR is fast — comparable to any two-argument function. Two considerations:

• Deep cascades. Nested IFERROR calls compound. A 5-level cascade is 5 potential formula evaluations, though short-circuit keeps most cases at 1-2.
• Volatile fallbacks. If your fallback is NOW() or TODAY(), the whole IFERROR becomes volatile-triggered, recomputing on every recalc. Prefer static fallbacks or reference cells that hold volatile values.

Faster than the legacy pattern

IFERROR runs the inner formula ONCE. IF+ISERROR runs it TWICE. On a workbook with 100,000 IFERROR-wrapped VLOOKUPs, that's a real difference — often 30-40% faster recalc times when migrating from IF+ISERROR.

How to write an IFERROR from scratch

1. Identify the fragile formula

   Ask: "What could break here?" Division by an empty cell, a VLOOKUP against a table that might not contain the key, a SUM over cells that might be text.

2. Wrap it as the first argument

   Copy the fragile formula into =IFERROR(...). Nothing else changes about the formula itself.

3. Choose your fallback deliberately

   Number for aggregations, text for display, empty string for "act blank." Not a random value — pick one that makes sense downstream.

4. Prefer IFNA if it's a lookup

   If N/A is the only expected failure, use IFNA. This is often the right call — you WANT to know if you get a REF error.

5. Chain for cascades, not for safety

   Nested IFERROR is for progressive fallback (try this, then that). It's NOT for wrapping "just in case" — that path leads to bug-swallowing.

Functions used with IFERROR

Frequently asked questions

Templates that use IFERROR

8 of our 10 templates use IFERROR — anywhere lookups or ratios might fail on missing data: