Field codes are how Word quietly does the boring math for you. Page numbers. Cross-references. “Chapter 12” labels that don’t fall apart when you move scenes around. And yes, they can also make you want to throw your laptop.
Look, I write and edit book manuscripts for a living. When I’m helping an author clean up a draft before formatting, field codes are usually the first thing I poke at. Because the draft might look fine. Until you update fields. Then everything either snaps into place or… doesn’t.
Table of Contents
Field codes are Word’s backstage crew
Here’s what I mean. Word has two layers: what you see, and what Word is actually calculating behind the curtain. A field is basically an instruction that says “show the current page number here” or “show the text of that heading over there.”
Most of the time, authors don’t notice fields until something breaks. Like a table of contents that lists the wrong page numbers. Or a cross-reference that stubbornly points to an old heading.
I recommend getting comfortable toggling between the pretty view and the code view. Because once you can see what’s going on, Word stops feeling haunted.
Microsoft’s own Word documentation lists over 100 distinct field types, from PAGE and REF to DATE and TOC.
Field result vs field code
The “field result” is what you normally see. Like “17” for a page number. The “field code” is the instruction. Like { PAGE }.
And yes, those braces matter. More on that in a second.
Why authors trip over fields
Because books move. Constantly. You cut a chapter. You add an epigraph. You shift a scene. Suddenly every “see page X” reference is wrong. Fields can fix that automatically. Or they can stay stale for weeks because nothing forced them to update.
In a Microsoft Office team blog post about field behavior, Word updates many fields at print/preview time, but not all fields update automatically during editing.
The three shortcuts I use every single day
I’m not a fan of memorizing a hundred commands. I am a fan of three.
Alt plus F9 toggles all field codes
Alt+F9 flips the whole document between results and codes. If your manuscript suddenly fills with curly brace stuff, don’t panic. You just hit the toggle.
Shift plus F9 toggles one field
Put your cursor in a field and hit Shift+F9. You’ll see the code for just that field. This is how I debug a single broken cross-reference without turning the whole draft into a robot script.
F9 updates fields
Select what you want updated, then hit F9. That’s the move. I usually do Ctrl+A first (select all), then F9.
According to Microsoft support documentation, pressing F9 updates the selected fields, and Ctrl+A then F9 updates fields across the entire document selection.
And yes. Sometimes Word asks whether to update just page numbers or the entire table. Pick the entire table if you changed headings. Page numbers only if you just nudged spacing.
Curly braces will make you cry if you type them wrong
Real talk: you can’t type field braces with your keyboard. Not the real ones. Typing { and } gives you regular braces, and Word won’t treat that as a field. It’ll just sit there like plain text and mock you.
To insert a field properly, I recommend either:
- Insert the field from Word’s menu (Insert tab, Quick Parts, Field).
- Or use Ctrl+F9 to insert the special braces, then type the field code inside them.
Microsoft’s support pages explicitly differentiate field braces inserted by Ctrl+F9 from typed braces, noting typed braces won’t create a working field.
I learned that the hard way. Years ago. I “built” a custom REF field by typing braces. Looked perfect. Did nothing. I blamed Word. It was me.
Page numbers, section breaks, and the stuff that ruins your front matter
Authors doing front matter always hit the same wall. Roman numerals in the opening pages. Arabic numerals starting at Chapter 1. And Word gets weird unless your sections are set up correctly.
PAGE and NUMPAGES fields
{ PAGE } shows the current page number. { NUMPAGES } shows total pages. Put them together and you get “Page 5 of 312”.
But. NUMPAGES counts based on the document’s current pagination. So if your section breaks are messy, the count can feel off.
SECTIONPAGES and SECTION
Sometimes you want “Page X of Y” for just the current section (like a separate appendix). That’s when SECTIONPAGES matters.
I’m not saying you’ll need this for every novel. You won’t. But for nonfiction with appendices? It pops up.
The author gotcha with section breaks
“Next Page” section breaks are usually the right choice for restarting page numbering at Chapter 1. “Continuous” breaks can be fine for columns or layout tricks, but they confuse authors because they don’t visually scream “new section.”
Microsoft’s pagination and section break guidance explains that page numbering is controlled per section, and restarting numbering requires a section break, not just a page break.
Cross-references that don’t rot when you revise
Cross-references are where field codes feel magical. Or infuriating. Depends on the day.
If you manually type “See Chapter 14,” you’ll forget to change it later. Everyone does. If you use a cross-reference field, Word can keep it aligned with the heading it points to.
REF fields are the workhorse
When you insert a cross-reference through References tab, Word is usually dropping a REF field behind the scenes. It points to a bookmark or heading.
So when Chapter 14 becomes Chapter 16, the REF can update. Usually. Assuming you update fields.
PAGEREF is for “see page” references
Want “see page 203”? That’s PAGEREF territory. It’s tied to a bookmark too.
I recommend bookmarking key items in nonfiction: figures, tables, exercises, the big “Step 1” sections. Then PAGEREF stays accurate even when you insert new material earlier in the book.
What breaks cross-references
Deleting the referenced heading can break the link. So can heavy copy-paste between documents, depending on how Word carries bookmarks along.
Microsoft’s support docs on cross-references note that cross-references are fields and must be updated to reflect changes to the referenced item.
Table of contents fields and why they go stale
I’ve had authors tell me “my TOC is cursed.” No. It’s just a field. A picky one.
TOC field basics
The table of contents is a TOC field that pulls from built-in heading styles. That’s the deal. If you styled your chapter titles as normal text and made them big and bold manually, Word won’t see them as TOC entries.
And if you later apply Heading 1 properly, the TOC won’t update until you tell it to.
Update page numbers vs update entire table
Word gives you two choices. Page numbers only. Or the full update.
Page numbers only is faster and fine when headings didn’t change. But if you changed chapter titles, or added a new subheading, you need the full update. Otherwise the TOC will keep showing old text and you’ll think you’re losing it.
Microsoft’s TOC help guidance describes the two update modes and confirms that updating the entire table is required to refresh headings and structure changes.
Word field switches that authors actually care about
Field switches are the little modifiers inside the code. They’re why two TOCs can behave differently. Or why one date field updates and another stays frozen.
Thing is, you don’t need all switches. Just a few that come up in book work.
Date fields that won’t betray you
{ DATE } updates automatically depending on Word settings. If you put today’s date in your manuscript for a submission package, you might want it to stay fixed. That’s when you use { CREATEDATE } or you just convert the field to text.
Because nothing says “sloppy” like sending an agent a file where the “prepared on” date changed because you opened it again.
Microsoft’s field reference differentiates DATE (current date) from CREATEDATE (document creation date) and SAVEDATE (last saved date).
StyleRef for running headers
Want the current chapter title in the header automatically? StyleRef does that by pulling text formatted in a particular style, like Heading 1.
This is the clean way to keep headers accurate when you rename chapters. No manual edits across 300 pages.
Ask and Fillin for template style workflows
These are niche. But I’ve seen them in manuscript templates, especially for nonfiction workbooks. They prompt you for values (author name, book title) and then reuse them.
And yes, they feel old-school. Because they are.
Locking fields, unlinking fields, and when I do each
This bugs me: authors either never lock fields, or they lock everything and forget why. There’s a middle ground.
Lock a field when you want stability
Select the field. Hit Ctrl+F11 to lock it. Now it won’t update when you run F9.
I lock fields when I need a snapshot. Like a final “Word count as of submission day” note in a cover page. Or a date that must not change.
Unlink a field when you want plain text forever
Select the field. Hit Ctrl+Shift+F9. That converts it to static text. No going back unless you undo.
I unlink fields when I’m handing a file to someone who will mangle it. Not always intentionally. But it happens. Copy editors. PDF converters. Random upload portals.
Microsoft documents Ctrl+Shift+F9 as the shortcut to unlink fields, replacing the field with its current result.
Troubleshooting field codes like a calm person
When fields act up, I don’t start by rewriting the whole document. I start with three checks. Quick. Boring. Effective.
Check whether you’re seeing codes
Alt+F9. Done. Half the “my page numbers disappeared” emails I get are just someone stuck in code view.
Update in the right order
Cross-references, TOC, lists of figures. They rely on other things. So I usually update the whole document (Ctrl+A, F9). Then update the TOC explicitly (right-click TOC, Update Field). That sequence tends to behave.
Check for broken bookmarks
If you see “Error! Reference source not found,” that’s a missing bookmark. Word isn’t being dramatic. It literally can’t find what the field points to.
Microsoft’s Word error message documentation identifies “Error! Reference source not found” as a broken bookmark or deleted referenced item in cross-references.
Fix is usually reinsert the cross-reference. Or recreate the bookmark. Annoying. But not mysterious.
My practical workflow for authors before you hand a manuscript off
I’m going to be blunt. Most formatting headaches I see started as “I didn’t want to touch anything technical.” Fair. But you don’t need to become a Word wizard. You just need a repeatable check.
- Save a backup copy. Seriously.
- Ctrl+A, then F9. Update everything.
- Right-click the TOC. Update entire table.
- Scroll for errors like “Reference source not found.” Fix those now.
- Decide which fields should be frozen (dates, specific notes). Lock or unlink them.
When I’m working with Adazing clients, I’ll often do this before we generate final files. It’s not glamorous. It prevents weird surprises later.
Want help setting up a clean Word workflow for your book, templates included? I’d point you here: Adazing resources for authors.
FAQs for Mastering Field Codes in Word
Why do I see a bunch of code instead of my page numbers and headings?
You probably toggled field code display. Hit Alt+F9 to switch back. If it’s just one weird spot, click into it and use Shift+F9.
Why won’t my table of contents update even after I click update?
Two common reasons. Your chapter titles aren’t using built-in heading styles. Or you updated page numbers only, not the entire table. Try applying Heading 1 to the real chapter headings, then update the entire table.
Can I create my own field codes from scratch?
Yes. Use Ctrl+F9 to insert real field braces, then type the code inside. But honestly? I recommend inserting from the Field dialog first, then tweaking. It reduces typo pain.
My cross-references say Error! Reference source not found. How do I fix that fast?
The referenced bookmark or heading is gone. Find the spot you meant to reference, recreate the bookmark or heading, then reinsert the cross-reference. After that, update fields with F9.
How do I keep a date from changing every time I open the document?
Use a non-changing field like CREATEDATE if it fits. Or convert the date field to text by selecting it and pressing Ctrl+Shift+F9. I do this a lot on submission cover pages.
Will field codes survive when I copy chapters into a new Word document?
Sometimes. Sometimes not. Cross-references that rely on bookmarks are the fragile ones. I usually update fields after the move and spot-check cross-reference targets. If the book is heavy on references, I prefer keeping everything in one master file until late in the process.
