Job search
A Resume Opens with Different Fonts: Preserve Layout Across Word and PDF
An actual synthetic DOCX and PDF experiment compares embedded resources, repairs inherited font references and checks an edited source without claiming another-device Word compatibility.
If a resume opens with different fonts, preserve the editable master before changing anything. Then check the font actually used by its styles, whether that font may be embedded, and the exported attachment. Check headings, symbols and paragraphs individually; a toolbar font name does not establish what every style uses or what another editor will render.
Follow the employer’s requested format. LandOffer publishes this guide and offers job-search tools; compare roles on LandOffer.ai and record the attachment instruction before choosing DOCX or PDF. This guide includes an actual local experiment using a wholly synthetic resume. We inspected document packages, edited a copy and checked three rendered PDFs. We did not open Microsoft Word or test another device, recruiter system or application parser.

Separate a missing font from a changed layout
Name the visible change before choosing a fix. Is one heading different, are all body paragraphs wider, or are only accented characters missing? Keep a reference PDF or screenshot of the intended page, then inspect the editable file’s paragraph styles and any direct formatting. A font change and a page-size change can produce similar symptoms without having the same cause.
Check the document’s paper size, margins, line spacing and paragraph spacing before compressing text to restore the old page count. Do not delete truthful experience or shrink the resume into unreadable type merely to force one page. Use the changed wrap to locate the formatting problem; preserve the resume’s verified facts.
If you obtained the document from a builder, verify that you have a real editable source. The separate DOCX export guide compares documented ways to obtain one. Here the task begins after you have the file: inspect its font resources and maintain a readable attachment after ordinary edits.
Check embedding support and the font’s permission
Microsoft’s font-embedding support page describes embedding in specified Office applications and versions, including Word for Microsoft 365 for Mac. It warns that not every font permits embedding. Its Windows instructions use File, Options, Save and the font-embedding controls; do not assume that path exists in every editor or web version.
Read the font’s license as well as its technical metadata. The OpenType OS/2 specification distinguishes installable, restricted, preview-and-print and editable embedding permissions. It also defines restrictions on subsetting and outline embedding. Those flags are not a reason to ignore the applicable license or alter the font’s permissions.
For an editable handoff, distinguish the whole font from a subset containing selected characters. Microsoft notes that character-only embedding reduces size but limits editing with that font. A newly added employer name or accented place name can require glyphs absent from a subset. Full embedding still does not guarantee that every receiving application supports the feature.
One detail needs caution: the support page’s sentence about “Do not embed common system fonts” appears inconsistent with its name. Microsoft’s separate Word property reference defines True as excluding common system fonts. We did not test that checkbox in Word; verify the setting in your actual version rather than inferring its effect from one sentence.
Completed experiment one: the same resume with and without a font part
We created a synthetic one-page resume for Ellis Morgan, with invented employers and an invalid example email domain. It contains ordinary headings, role dates, paragraphs and a character-check line with “Renée, café, résumé.” There is no real candidate information, confidential work or claim that those employers exist.
The font was Liberation Sans Regular 2.1.5, already included in the bundled local renderer. Its internal license field names the SIL Open Font License 1.1; the accompanying license permits embedding under its conditions. We retained the license text, copyright metadata and source-file hash. Its fsType value was zero. We did not install fonts, buy a license or change system or Office preferences.
Using Python document tools, we made two DOCX packages with identical document text and styles. One contains no embedded-font part. The other contains the full, 410,712-byte font resource, referenced from the font table, with the subset flag false. This was programmatic package construction, not a recording of Word’s Save dialog.
| Check performed | Actual local result | What it establishes |
|---|---|---|
| Text and style comparison | document.xml and styles.xml were byte-identical between the two final base files |
The comparison did not change resume content or intended styles |
| No-embedding package | No word/fonts/ resource; DOCX size 37,567 bytes |
This package did not carry the tested font |
| Full-embedding package | One full font resource and resolving relationship; DOCX size 248,544 bytes | Font data was present; the ZIP size is compressed, not the raw font size |
| Resource verification | Reversing the package’s font obfuscation reproduced the original font’s SHA-256 | The payload matched the saved full source font, rather than merely a font name |
| Missing-resource control | An in-memory copy with the font part removed failed the verification | The check detects this missing part; it is not a general Office compatibility test |
Microsoft’s font-part implementation note documents the obfuscated-font content type. That technical packaging mechanism does not confer a license, make the font a portable installation package or prove that Word will load our constructed file correctly.
The experiment encountered a real failure. An early manually serialized embedded package could be read by the Python document library but was rejected by the bundled renderer. Preserving the package’s XML namespaces resolved that loading failure. The rejected file and logs remain in the evidence; a successful package inspection alone would have missed it.
Inspect the actual font used in the PDF
We rendered both final base files with LibreOfficeDev 26.8.0.0.alpha0 on the same Mac, using an isolated renderer profile. Liberation Sans was already available in the bundled renderer’s own font resources. Each final base export produced one US Letter page, 612 by 792 PDF points. Their extracted text matched, and their rendered page pixels were identical.
That equality is a limited result. It does not demonstrate what happens when the font is missing, that the renderer loaded the embedded copy, or that another computer’s Word will behave identically. Removing installed fonts or forcing substitution would change the experiment; we did neither.
PDF inspection also caught a separate issue during preparation. Although the document styles named Liberation Sans, inherited theme references initially caused some PDF text to use Carlito. We removed those theme references inside the synthetic document and explicitly set its font references, then rerendered all three final files. The final PDF resources identified Liberation Sans throughout. This repair changed the fixture, not the machine’s font configuration.
The first visual pass also exposed an inherited blue rule beneath the title. We removed that template border and reviewed the new pages. Neither issue was established by the file extension or a font name alone. The point of the exercise is to inspect what was rendered, then save the corrected source that produced it.

Completed experiment two: edit the source and verify a fresh PDF
For the second completed asset, we reopened the embedded DOCX with the local Python document library and appended a diagnostic line containing Zürich and Ω. The original resume facts stayed unchanged. The new line is explicitly a local review note, not a career achievement or text a candidate should copy into an application.
We saved the edited source and repeated the package and PDF checks. This tests a local edit-and-export workflow; it is not a Word editing session or a second-device handoff.
| Acceptance item | Completed result | Remaining boundary |
|---|---|---|
| Editable source | The edited DOCX reopened and saved; size 248,658 bytes | No Microsoft Word editing test |
| Full font retained | The font resource remained byte-identical to the embedded base package | No proof of recipient-side font loading |
| Fresh export | The edited source produced one US Letter PDF page | A different renderer could wrap differently |
| Added characters | PDF extraction retained Zürich and Ω; the page image showed readable glyphs | No claim about every language or glyph in the font |
| PDF font resources | Each font resource had an embedded TrueType font stream and a subset-style name | PDF subsets are separate from the full font in the DOCX |
| Page inspection | All three final page images were opened; no clipping, overlap or missing characters were seen | This is local rendering evidence, not ATS or recruiter verification |
The PDFs contained embedded font subsets even though one source DOCX carried no font resource. This shows why DOCX embedding and PDF embedding need separate checks. A PDF exporter can use a font available locally; a good-looking PDF does not retroactively prove that its editable source is portable.
The edited PDF’s extracted text differed from the base only through the added diagnostic line’s content. Character-bound checks stayed inside the page, and the visual review checked headings, dates, accents and the bottom of the document. Text extraction helped verify content; it did not replace looking at the page.
For this fixture, we retained the editable source and the fresh PDF as a matched pair. The decision record marks local package, edit and export checks complete, while Word on a recipient device remains untested. That is a more useful handoff than calling the file “universally compatible.”
Choose a readable fallback without losing editability
If a font cannot legally be embedded, choose a licensed alternative and inspect the entire resume after replacement. Use the alternative consistently through the relevant styles and direct formatting. Expect headings or long bullets to wrap differently; repair spacing and page breaks in the source rather than making a disconnected PDF-only correction.
Keep the employer’s requirement in control. When DOCX is mandatory, a PDF can be a visual reference only if the submission process allows it; it cannot silently replace the requested editable attachment. When PDF is requested, export it from the checked current source and inspect that export, rather than sending an older PDF that happens to look better.
For a genuine recipient check, use the actual application and device arrangement available to you, with permission. Record the version, whether editing was needed and which page changed. If you cannot perform that check, say so. A local renderer comparison remains useful but answers a smaller question.
Do not send a standalone commercial font file to resolve someone else’s missing-font problem unless the license permits that distribution. Embedding permission, installation rights and redistribution are separate questions. When the rights or receiving software remain uncertain, consider a licensed replacement and recheck its layout.
Keep a source and attachment acceptance record
Before sending, record the source version, requested format, font names and license basis, exported filename and pages reviewed. After a meaningful source edit, export a fresh attachment and recheck the affected pages. A file-size increase is a clue that something changed, not proof that every font was embedded correctly.
Compare visible content with your verified resume facts. Check dates, links, headings and special characters; then separately inspect any application fields populated from the file. Successful rendering cannot establish correct field mapping or interview prospects.
Use LandOffer.ai to compare suitable roles and their submission requirements. Keep one authoritative editable source for each intended resume variant, and derive the outgoing attachment from it. The completed local checks above help explain a font problem; they do not promise unchanged layout across all Word versions, devices or hiring systems.
Sources and Further Reading
- Microsoft Support: Benefits of embedding custom fonts — application-specific embedding, editing and font-permission guidance, checked October 23, 2026.
- Microsoft OpenType specification: OS/2 fsType — embedding permission flags and restrictions.
- Microsoft Word: DoNotEmbedSystemFonts — property definition; no Word UI test performed.
- Microsoft implementation note: Font Part — obfuscated font-part content type.


