You spent an evening getting your CV onto exactly two pages, with the dates lined up on the right and a neat little phone icon next to your number. Then a recruiter opens it on a laptop you have never seen, in an app you did not choose, and gets three pages, a stray heading at the bottom of page two, and an empty square where the phone icon used to be. You will never know, because nobody writes back to say "your file looked broken."
This is the part of CV formatting almost nobody tests. What you see on your own screen is a private preview.
Your screen is the only place it is guaranteed to look right
A CV document does not carry a picture of itself. A Word file is a set of instructions: use this font, at this size, with these margins, put this block here. Every machine that opens it follows those instructions with whatever it has installed. When everything it needs is present, you get your layout. When something is missing, the software improvises, and it does not tell the reader it improvised.
That is why "it looks fine on my laptop" proves very little. Your laptop has your fonts, your version of Word and your screen width. A hiring manager reading your CV on a phone on the train shares almost none of that.
PDF is far more stable, but a badly exported PDF carries the same problems, so the format alone does not save you. (Whether to send PDF or Word is a separate decision.)
The quiet failures that change what a recruiter sees
None of these produce an error message. The file opens, it looks roughly like a CV, and the damage is in the details.
A font that is not on their machine
You picked a typeface you liked, maybe a free download. The recruiter does not have it. Their software swaps in a fallback font, usually something wider or narrower than yours. Every line rewraps. A bullet that fit on one line now takes two, the section headed "Education" slides down, and your two-page CV becomes two pages and four lines. That fourth line sitting alone on page three looks careless, even though you did nothing wrong on your own screen.
Word opened somewhere that is not Word
Plenty of people open .docx files in Google Docs, Apple Pages, a mail client's built-in viewer, or an older Word release on a company laptop. Each one interprets spacing, tab stops and section breaks slightly differently. Right-aligned dates drift left. Line spacing tightens or opens up. A table you used for layout suddenly shows its borders.
Two columns on a phone
A two-column layout reads well on an A4 page. On a phone, a PDF viewer either shows the whole page shrunk down until the sidebar text is unreadable, or a reflow mode tries to turn your columns into one stream and gets the order wrong. Your skills sidebar can end up wedged between two job entries. Recruiters read on phones more than candidates assume.
Icon fonts that turn into boxes
Those small icons for phone, email, location and LinkedIn are often characters from an icon font rather than images. If that font is not embedded or installed, each icon becomes an empty rectangle or a random letter. Your contact line now opens with a row of boxes, which is the first thing a reader looks at when they want to call you.
Text boxes, headers and footers
Text boxes are anchored to a position on the page, and that anchoring is exactly what other apps handle worst. A box can jump to the next page, overlap the paragraph below it, or vanish from view. Putting your name and contact details in the document header has a similar risk: some viewers shrink headers, some hide them, and some previews skip them altogether. How parsing software treats headers is a separate issue; here the point is that a human may not see the box.
A PDF without embedded fonts
Exporting to PDF is supposed to freeze the layout. It only does that fully when the fonts are embedded in the file. Some export settings, print-to-PDF drivers and online converters leave fonts out or embed only part of them. The PDF then relies on the reader's machine to supply the font, and you are back to substitution, just with a file extension that makes you feel safe.
The test almost nobody runs
Here is the check that catches nearly all of this, and it takes ten minutes.
- Email the final file to yourself. Use the exact file you will send, with the exact name, as an attachment, not a link to a cloud copy.
- Open it on a different device. A phone first, then a computer that is not yours if you can borrow one: a partner's laptop, a library machine, a work computer.
- Open it in a different app. If it is a Word file, upload it to Google Docs and open it in whatever free office suite is around. If it is a PDF, open it in the mail app's preview and in a browser.
- Look at it at phone width without zooming. Can you read your name, your current job title and the first two bullets? Is the order of sections still the order you intended?
- Count the pages. If your two-page CV became three anywhere, something reflowed.
The question is not "does my CV look good?" It is "does my CV look the same everywhere a recruiter might open it?"
Write down what changed. Each difference points at one of the causes above, and the fix is usually small.
Fixes that hold up on any machine
Export a real, text-based PDF with fonts embedded
Export from your editor's own PDF export rather than a third-party converter or a print driver, and pick standard or high-quality output over the smallest file. Then check the result: open the PDF and try to select a line of text. If you can highlight words, it is text-based. If the whole page selects as one image, it is a flattened export. Most PDF readers also list, in the document properties, which fonts the file contains and whether they are embedded.
Stay close to fonts that are widely installed
You do not need a dull CV, but a typeface that ships with the major operating systems survives far better than a niche download. The choice of font is covered elsewhere; the rendering rule is simple. If you love an unusual font, keep it to the PDF, embed it, and never send that layout as an editable Word file.
Drop text boxes, icon fonts and layout tables
Build the page from normal paragraphs and tab stops. Put your name and contact details at the top of the page body, not in the header. If you want icons, make sure the text next to each one stands on its own: a contact line that still reads well with the icons stripped out is the safe version.
Design for one column, even if you show two
If you keep a two-column layout, put the sections that matter most in the main column, and keep the sidebar short and optional. Then do the phone-width check again. Someone skimming on a phone should still meet your current role before your list of languages.
Name the file like a person will see it
"CV_final_v3_NEW.pdf" looks careless in a download folder. Use your name and the document type, for example "Firstname-Lastname-CV.pdf", with no special characters. It is the first thing the recruiter sees, before the page itself.
If you generate your CV with a builder such as Postulit, which turns a LinkedIn profile into an exported CV, the same rule applies: download the export and run the test on it before you send it anywhere.
A short pre-send checklist
Before any application goes out, run through this once:
- The file is a PDF exported directly from your editor, with selectable text.
- The page count is the same on your phone, on another computer and in a browser.
- Your name, phone number and email appear in the page body and read correctly with no icons.
- No text boxes, and no content hiding in the header or footer.
- The file name contains your name and nothing like "final" or "v2".
The fix for a broken render is rarely a new template. It is ten minutes of opening your own CV the way a stranger would, then removing whatever did not survive the trip. Do that once with your current file today, and keep the version that looks the same everywhere.