Your Excel formula is showing as text because the cell is formatted as Text before you enter the formula, or the entry was forced into text mode by a leading apostrophe or a preceding equals sign. Excel reads the cell's number format first. When that format declares the contents as Text, Excel stores your formula string literally and never sends it to the calculation engine.
The calculation pipeline and where parsing breaks
Every keystroke you commit triggers a short sequence. Excel first inspects the cell's number format, then checks the entry string for a leading apostrophe or an already-text prefix, then decides whether the content is a formula or a literal. Only after those checks does it hand an equals-prefixed string to the formula parser, which tokenizes functions, operators, and references and builds a dependency tree.
That ordering explains the symptom. A cell set to the Text format is preclassified as non-calculating storage. Excel still accepts your equals sign, but it treats everything after it as characters, not syntax. Nothing reaches the parser, so no calculation event fires. The cell displays exactly what you typed, including the leading equals.
The same gate applies to the leading apostrophe. An apostrophe is Excel's explicit "store as text" override, and it is consumed on entry, so the apostrophe itself is hidden. If you see a formula in the formula bar with a visible leading apostrophe, or you see an equals sign rendering as plain characters in the grid, the parser was bypassed. This is why the fix is almost never "retype the formula" and almost always "change the storage class first."
Why Text format wins over formula entry
The format check precedes parsing because Excel treats cell format as a declaration of intent. Users who format a range as Text often want part numbers, ZIP codes, and leading zeros preserved. Honoring that intent means suppressing automatic interpretation, including formula interpretation. This is a design choice, not a bug.
The consequence is that the format is sticky in a specific way. Changing the format back to General does not retroactively reparse existing strings. Excel recalculates formats when the cell is edited or when you invoke a re-entry action, not when you change the format alone. A cell that stored "=A1+B1" as a 6-to-8-character text string stays text until something forces a fresh entry event.
There is a second layer most explainers miss: the global option "Enable automatic percent entry" and the related "Error checking" rules interact with this. The green triangle error indicator for "text formatted cell containing a number" is a diagnostic, not a fix. Clicking it and choosing Convert to Number converts values, not formulas, so it can appear to do nothing when your content is an equals string.
Scale of the problem and how often it appears
Text-stuck formulas are among the most common spreadsheet support questions, and the affected ranges are usually large. Imported CSVs and vendor exports routinely arrive with columns preformatted as Text, which can mean hundreds to thousands of cells in a single column. One misformatted template can propagate the issue across every workbook copied from it.
A rough diagnostic: if the status bar shows Count but not Sum or Average when you select your range, the cells are being read as text. Numbers formatted as text will not aggregate, and formulas stored as text will not evaluate. Both symptoms share the same root cause. In a 1,000-row column, retyping each cell manually at roughly 3 to 5 seconds apiece costs close to an hour. Bulk re-entry methods take seconds, which is why the mechanism matters more than the trick.
Edge cases that mimic or mask the problem
Not every text-looking formula is a format problem. Some entries are genuinely text by user intent, and some parser failures come from other layers.
Leading apostrophe: the apostrophe is the direct text override and may be invisible in the formula bar if the cell was pasted. Preceding space or nonbreaking space: an entry like " =A1" begins with a space, so Excel never sees the equals sign as the first character and treats the entry as text. Imported CSV with quote characters: surrounding quotes from the export can survive import and turn the whole formula into a literal string. Cell formatted as Text after entry: reformatting an already-entered formula to Text can convert the display behavior and, on re-entry, store the string literally. Show Formulas mode toggled on: this displays formulas as text across the whole sheet without changing storage, so it is a display state, not a format defect. Grouped or protected sheets: edits can silently fail, leaving the old formula string in place and looking unchanged.
The counterintuitive detail: in some pasted cases the formula bar shows the equals sign and the value looks correct, yet the cell will not recalculate. That pattern points to the cell having been stored as an array or shared formula from an external source, not to the Text format. Checking the format is always step one, but do not assume it is the only cause.
Common misconceptions and what actually happens
Misconception one: pressing F2 and Enter fixes it. Pressing F2 and Enter forces a re-entry event, which does fix a Text-formatted cell only if you change the format first. Without a format change, the re-entry stays text. The format is the gate; F2 is just the trigger.
Misconception two: the formula needs to be retyped from scratch. Most bulk cases need only a format change plus a re-trigger action, such as the Text to Columns trick on a single column or a Find and Replace of the equals sign with itself. Retyping a thousand rows is a waste of an hour.
Misconception three: deleting the leading apostrophe in the formula bar is enough. For a single cell, yes. For a column, the apostrophe may be part of the stored string, and deleting it means touching each cell. Paste-bypass and Text to Columns handle this in bulk.
Misconception four: the green error triangle is a reliable signal. It flags numbers stored as text. An equals string stored as text is not a number, so the indicator may stay silent even though the calculation is broken. Absence of the warning proves nothing.
Practical actions with concrete thresholds
Treat these as a decision sequence, not a menu. Reconcile the two thresholds carefully: if a column has roughly 20 or fewer affected cells, fix them individually; above about 20, batch methods are faster than manual entry at roughly 4 seconds per cell.
For a single cell: select it, confirm the format is not Text, press F2 then Enter, or use Ctrl+Shift+U to remove a leading apostrophe. Verify by checking the status bar shows a computed value.
For a column or range: select the range, set format to General, then open Data > Text to Columns, click Finish without changing delimiters, and let Excel re-enter each cell through the parser. This is the highest-yield single action and typically resolves an entire column in seconds.
For pasted imports: paste the data first into a plain text editor, strip surrounding quotes, then paste into Excel with the target range already set to General. Do not preformat the destination column as Text unless you know the content should stay literal.
For stubborn cases: a Find and Replace on the equals sign (replace "=" with "=", using the "match entire cell contents" option off) triggers re-entry across a range. Confirm the results with a SUM over a known test subrange before trusting the whole sheet.
Red flag: formulas that reference a sheet with a name containing spaces but no quotes will parse as text-looking entries, because the parser rejects the reference and falls back to literal storage. Red flag: an imported column where only the first row evaluates usually means the Text format was applied to the whole column after a partial fix. Red flag: cells that display a leading equals while the formula bar hides it may be in Show Formulas mode; toggle with Ctrl+` before changing formats.
Comparison of fix methods
| Method | Best for | Effort | Risk | Re-enters as formula |
|---|---|---|---|---|
| Reformat to General plus F2/Enter | Single cells | Low | None | Yes, per cell |
| Text to Columns (Finish only) | Whole columns | Low | Low, if delimiters untouched | Yes, whole range |
| Find and Replace "=" with "=" | Mixed ranges | Low | Medium, can touch other cells | Yes |
| Paste into Notepad then back | Imported CSV | Medium | Low | Depends on paste options |
| Manual retype | A handful of cells | High | Low | Yes, slowly |
| Convert to Number button | Numeric text only | Low | Does nothing for equals strings | No |
Timeline of what happens on entry
| Stage | Time (typical) | What Excel does | Failure if text-formatted |
|---|---|---|---|
| Keystroke commit | Less than 1 ms | Reads cell number format | Skips parsing |
| Apostrophe check | Sub-millisecond | Flags explicit text override | Stays literal |
| Parser handoff | 1-2 ms | Tokenizes functions and references | Never invoked |
| Dependency build | 2-10 ms | Builds calculation tree | No tree, no chain |
| Recalc event | On edit or F9 | Updates downstream cells | Nothing to recalculate |
| Display render | Immediate | Shows value or string | Shows the string |
Limitations and the deeper caveat
Formatting alone does not guarantee evaluation. Excel also has a global setting, "Automatically enable error checking" on the Formulas options page, and workbook-level calculation set to Manual, both of which can make a correctly formatted formula look frozen. Check the calculation mode in the status bar before assuming a format problem. If it reads Manual, press F9; a formula that suddenly evaluates confirms the culprit was calculation mode.
One more professional caveat: text-stuck formulas can be deliberate. Spreadsheet models sometimes store formula strings in a documentation column on purpose, and bulk "fix" operations can destroy those annotations. Before running a batch method over an inherited workbook, sample a few cells in the target column and grep for leading equals signs in your file's raw XML if the model is large. The fix is safe only when the text storage was unintended.
This article is general educational information about spreadsheet behavior, not a software warranty or a substitute for testing changes in a copy of your workbook. Verify fixes on a duplicate file before applying them to production data, and consult your organization's spreadsheet or IT support for workbook-level settings you do not control.