How to Make a Resume in Word Without Losing Your Name
How to make a resume in Microsoft Word that a screening filter can actually read, why the built-in templates hide your name, and how to save it.
How to make a resume in Microsoft Word that a screening filter can actually read, why the built-in templates hide your name, and how to save it.

To make a resume in Word, start from a blank document and build a single-column layout, instead of the built-in templates. Word's resume templates hide your contact details in the header region and in text boxes, which most screening filters skip entirely. Save it with File, Save As, PDF.
You open Microsoft Word, go File, New, type "resume," and pick the clean one with the blue sidebar. You swap in your name, tab down to add a job, and the cursor jumps somewhere you did not click. Your phone number sits in a strip at the very top that you cannot select like normal text. An hour later the page looks sharp, you send it, and you hear nothing. The layout was not the problem you thought you were solving. It was the one you created.
Word is a fine, free-if-you-already-own-it way to build a resume. The built-in resume templates are the part that quietly works against you, and nearly every guide opens by telling you to use one.
The takeaways
The built-in templates fail in a way you cannot see. To hold their tidy look, Word's resume templates lean on three constructions: an invisible table for the two-column layouts, floating text boxes for side panels, and the document's actual header and footer region for the contact strip along the top.
Those last two are the ones that cost you interviews. An applicant tracking system (ATS), the software that reads and files your resume before a person opens it, parses the main body of the document. It treats the header and footer region as page furniture and usually ignores it, and it treats a text box as a floating object it can skip. So when the template tucks your name, phone, and email into the header, or your skills into a side text box, the parser reads right past them. On screen the resume looks complete. In the system it can land with no name attached.
I know these layouts because I built JobScalr's own CV parser to handle exactly them: multi-column, text-box, and header-tucked files that normally get scrambled. Writing a reader that recovers text from those layers taught me how routinely a plain screening filter does not bother, and the header region and text boxes were the two spots that most often came back empty. You cannot assume the employer's parser is as patient. For the underlying rules, the rest of our résumé and CV formatting guides go deeper, and the closest one here is what an ATS-friendly resume format looks like.

Start from a blank document and keep everything in the main body. It sounds slower than a template and it is barely different, because you were going to retype every field anyway. Here is the whole build:
Two of those steps deserve a reason, because they are the ones people undo first.
Step 5 rules out tabs for a reason that is invisible on screen. When you press Tab to push a date to the right margin, you have not created a column, you have inserted a character. A parser reading the line gets your job title, a tab character, and the date all as one run of text, and it has to guess where the title ends. Some guess wrong and file your dates as part of the employer name. A plain line with the date at the end of it, or on its own line underneath, never has that ambiguity.
Step 4 has a small upgrade worth taking. Instead of bolding your headings by hand, apply Word's Heading 2 style from the Home ribbon (then right-click the style, Modify, and set it to a plain font at the size you want). Visually it lands in the same place. Structurally it marks those lines as headings in the file itself, which gives a parser one more signal about where "Experience" stops and "Education" starts. Manual bold is not a mistake and it will still parse. Styles are just the free upgrade, and they make the whole document easier to restyle later.
That is the entire method, and it survives the software because there is nothing exotic for a parser to trip on. For the content that goes inside this frame, section by section, we have a separate walkthrough on how to make a resume in the right order; this post is only about doing it in Word. If Word is not where you want to work, the same single-column logic applies to a resume in Google Docs.
You do not have to trust any of this, including my version of it. There is a two-minute test that shows you roughly what the software gets, and it works on any resume, from any template, including ones you built years ago.
Open your resume. Select everything (Ctrl+A, or Cmd+A on a Mac), copy it, and paste it into a plain text editor: Notepad on Windows, TextEdit switched to plain text on a Mac, or any empty box that cannot hold formatting. All the styling falls away and you are left with the raw text, in the order the file stores it.
Now read what came out, and check three things:
One honest caveat: this is an approximation, not a simulation. Parsers differ, and a good one recovers more than Notepad does, including some header text and some table content. What the test tells you reliably is the shape of the risk. If your name survives a plain paste, every parser will find it. If it does not, you are betting your application on the employer having bought a better one than average.
Run the same test on the PDF after you export it. Open the PDF, select all, copy, paste. If nothing comes out, the file was flattened into an image somewhere and no software can read a word of it.

For most online applications, save as PDF. Open File, Save As (or Export), and choose PDF. A PDF holds your layout on any device, cannot be edited by accident, and, saved this way from Word, keeps selectable text a parser can read. Confirm it: open the PDF and try to highlight a line. If the text selects, the file is readable; if it does not, something flattened it to an image.
There are two real exceptions, and this is where the blanket "always PDF" advice trips people. First, if the posting or the application portal asks for a Word file, send the .docx; ignoring the instruction reads as not following directions. Second, third-party recruiters often ask for Word specifically, because they redact your contact details and drop in their own before passing you to the client. Follow whichever the recipient names. When nobody specifies, PDF is the safer default. We compare the two formats in full in PDF versus Word for an ATS.
You can, and whether you should depends on where you are applying more than on any universal rule.
Two columns are the risky one. If you build them with a table, a parser reads the table cell by cell, and where it starts and stops is up to the software. Your skills sidebar can end up spliced into the middle of a job description, or dropped. If you want the visual density of two columns without the parsing gamble, the usual compromise is a single column with a short comma-separated skills line near the top, which reads fast for a human and stays unambiguous for the software.
Photos depend on the market, and this is where blanket English-language advice misleads people. In Germany, Austria, and much of continental Europe, a photo on a CV is conventional and its absence gets noticed. In the US, the UK, and Canada, recruiters often discard a resume with a photo, because it creates a discrimination-liability problem for them. The same file can be correct in one country and wrong in the next, so let the target market decide. The same split applies to date of birth, nationality, and how strictly you must account for employment gaps: a German CV is expected to leave no unexplained gap, a UK one is not. This is the part JobScalr adjusts per target country.
Word's other design features are mostly safe in moderation. Bold, italics, standard bullet lists, and horizontal rules all parse fine. What causes trouble is anything that floats: text boxes, WordArt, SmartArt, icons, charts, and images with text baked into them. If a piece of information exists only inside a graphic, treat it as invisible to the software.
Yes, for the ordinary case: you already own it, you want a document you control offline, and you are applying through online forms. Word does all of that well the moment you skip the template gallery.
It is not the right tool for everyone. If you are applying for a design or brand role where the resume doubles as a work sample, a plain Word document undersells you, and a layout tool fits better. One honest limit holds across all of it: no template choice and no file format rescues content that does not match the posting. The layout only decides whether your real match gets read.
Most are not, because they place contact details in the header region and use text boxes or two-column tables, and screening filters commonly skip those layers. A blank single-column document you build yourself is the more reliable choice than trusting a specific template to parse.
Delete the header entirely and retype your name and contact line as the first lines of the main body. Double-click the header area, select everything in it, delete, then close the header. If your name only lived up there, the parser was never reading it.
You can, but it is usually slower than starting fresh. You would need to move header content into the body, delete every text box and paste its text back in as normal lines, and unpick any table columns. Rebuilding from a blank document is faster and leaves nothing hidden.
A standard body font at 11pt, with your name a few points larger, reads cleanly for both a person and a parser. Arial, Calibri, and Georgia are safe. Avoid decorative or condensed fonts, and do not shrink below 10pt to force everything onto one page.
Send PDF unless the posting, the portal, or a recruiter asks for Word. PDF preserves your layout everywhere and keeps selectable text when you save it from Word. Keep the editable .docx as your working copy so you can tailor it for the next application.
Set margins between 0.5 and 1 inch under Layout, Margins. Word defaults to 1 inch, which is a fine place to leave it. One page is the norm until you have around ten years of relevant experience, after which two pages are expected. When you run long, cut early roles and trim bullets down to the ones that match the posting; shrinking the margins and the font is the move that makes a page unreadable at 9pt.
Cut content before you touch formatting. Drop roles older than about fifteen years to a single line each, delete bullets that describe routine duties instead of results, and remove the objective statement if you have one. If you are still two lines over after that, reducing line spacing slightly or tightening margins toward 0.5 inch is the safer squeeze, because it does not make the page harder to read the way a 9pt font does.
Yes, the single-column method is identical in both. The only difference is where the export lives: in Word Online it is File, Download, Download as PDF, and on Mac it is File, Save As with PDF chosen in the format dropdown, or File, Export. Run the copy-and-paste check on the result either way, since browser-based exports occasionally behave differently from the desktop app.
Sharpen your next application.
See your honest match score before you send, then tailor your CV and cover letter to the exact posting. Your first analysis is free.
Put this into your next application.
See JobScalr →