Does a LibreOffice resume pass an ATS in 2026?

Does a LibreOffice resume pass an ATS in 2026?

Yes — applicant tracking systems read the file you upload, not the program that produced it, so a CV written in LibreOffice Writer parses exactly as well as one written in Word once you export it properly. This matters more than usual right now, because LibreOffice has just turned privacy into a selling point. The Document Foundation confirmed that "no AI" counts as a feature: version 26.8, released in August 2026, listed the absence of generative AI among its highlights, and the project says it won't add AI to the default installation. No telemetry, no documents quietly shipped to remote servers, no component that needs network access to work.

That position clearly struck a nerve. Coverage this month notes the release passed a million downloads in its first week — reportedly the strongest opening in the project's history — and a good share of those downloads are people who simply don't want their documents feeding a model. Fair enough. But a CV is a strange document to write in private, because its whole purpose is to be read by a machine you don't control. The moment you upload it to a careers portal, a parser strips it to plain text, guesses where your job titles end, and decides whether a recruiter ever sees your name.

So the privacy win and the parsing problem are separate questions, and only one of them is solved by your choice of editor. Writer gives you a clean, local, free tool with full control over styles — genuinely good raw material for an ATS-friendly CV. It also gives you text frames, multi-column page layouts and a template gallery full of designs that break parsers. The rest of this article covers the export settings that keep your file readable, the layout choices that quietly destroy it, and a two-minute test that tells you which side of the line your CV sits on.

Should you upload an ODT file, a DOCX or a PDF?

Upload a text-based PDF by default, a DOCX when the form specifically asks for Word, and never the native .odt. ODT support across tracking systems is inconsistent rather than absent, which is the worst possible situation: some enterprise systems do list OpenDocument among accepted formats, while others leave it off entirely — Greenhouse, for instance, publishes a supported list of .doc, .docx, .pdf, .rtf and .txt with no .odt on it. Workday is configured per employer, so acceptance varies from one careers site to the next. You can't audit which build you're facing from the outside, and an "unsupported format" error is the kindest failure mode available.

Keep the .odt as your editing master. It's the format Writer handles losslessly, it's where your styles survive intact, and it's the file you open next time a job ad lands. Then export a delivery copy per application. Here's the contrarian part: for LibreOffice users specifically, I'd trust a text-based PDF over a DOCX. The standard advice says DOCX parses most reliably, and that's broadly true — but it assumes Word produced the file. Writer's DOCX export is itself a conversion step, and conversion is exactly where frames, table spacing and contents fields get mangled.

Two practical constraints worth respecting. Keep the file comfortably under 5 MB, since many employer Workday configurations cap uploads around that mark even though other systems allow far more. And never password-protect or digitally sign the PDF you submit; security wrappers block parsers the same way they block editing, and your application dies silently before anyone reads a word. Name the file plainly — something like firstname-lastname-cv.pdf. If the application form offers a format preference, follow it exactly rather than guessing, and if it offers both PDF and Word, pick PDF unless the ad says otherwise.

Which LibreOffice export settings keep your CV readable?

Use File → Export As → Export as PDF, and on the General tab tick "Tagged PDF (add document structure)" while leaving Hybrid PDF, Archive (PDF/A) and the form options switched off. Tagged PDF writes the document's structure into the file — headings, paragraphs, lists — which is precisely the scaffolding a parser uses to tell a job title from a bullet point. The file grows a little; that's a trade worth making every time. Hybrid PDF embeds a full copy of the ODF document inside the PDF, which makes the file roughly half again as large and hands the employer your editable source for no benefit. Switch it off and remember it stays on for future exports until you do.

On the Security tab, leave everything blank. No open password, no permissions password, no restriction on content extraction — that last setting in particular tells software it may not copy text out of the file, which is exactly what a parser needs to do. If you want the extra assurance, also fill in File → Properties with your name and a sensible title, and check Tools → Options → LibreOffice → User Data so the document doesn't go out carrying someone else's details from a borrowed machine. None of this is cosmetic housekeeping; metadata is the first thing some systems read.

For DOCX delivery, use File → Save a Copy and choose Word 2007-365 (.docx) rather than overwriting your master. Stick to fonts that survive the trip: Liberation Sans and Liberation Serif are metric-compatible with Arial and Times New Roman, and Carlito matches Calibri, so a recruiter opening the file in Word sees the same line breaks you did. Then open the exported DOCX back in Writer and read it. If you're starting from scratch rather than patching a decade-old layout, a chat-based CV builder with ATS-friendly templates removes the export guesswork entirely, since the PDF and Word files come out already structured for parsing.

Which LibreOffice layout choices break ATS parsing?

Text frames, multi-column page layouts, tables used for alignment, and anything placed in a header or footer are the four features most likely to wreck your CV in a parser. Frames are the worst offender in Writer specifically, because OOXML has no equivalent concept — export to DOCX and the frame gets converted into a drawing object, sometimes splitting into a shape plus a separate textbox, with text landing outside its borders. Users have documented table spacing and contents-field formatting disappearing on the same round trip. A frame that looks like a tidy sidebar in Writer can arrive as a floating picture that the parser either ignores entirely or dumps mid-sentence.

Two-column CVs fail for a simpler reason: the parser reads in a linear order, so a skills column beside your work history gets interleaved line by line with it. "Python" ends up wedged between your employer and your dates, and the resulting text salad doesn't map to any field the system expects. If you've built your layout from side-by-side columns, that's worth rebuilding as a single column before you apply again. One column, top to bottom, is the only layout rule that holds across every system — and it doesn't have to look dull.

Put your contact details in the body of the document, not the page header, since some parsers skip headers and footers altogether — losing your phone number is a spectacular own goal. Build hierarchy with Writer's paragraph styles (Heading 1, Heading 2, List Bullet) rather than manually bolding and resizing text, because styles are what Tagged PDF and DOCX export turn into machine-readable structure. Skip icons for phone and email, skip graphical skill bars, and keep dates in a consistent written format like "Mar 2022 – Jun 2025". For Hebrew or bilingual CVs, Writer 26.8's automatic paragraph direction detection helps, but still check the exported file for reversed punctuation.

How do you test your own CV's parsing before you apply?

Open your exported file, select all the text, and paste it into a plain text editor — that stripped-down version is roughly what the tracking system sees. Read it in order. If your name appears first, your sections stay in sequence, each job keeps its employer, title and dates together, and no bullet has fused with the one beside it, your file parses. If the skills column has shredded itself through your work history, or whole blocks have vanished, you've found the problem before a recruiter found a reason to skip you. This test costs two minutes and catches the majority of layout failures.

Run three more checks. In a PDF viewer, try selecting a single word of body text: if the cursor won't grab it, you've exported an image and nothing will be read. Use Ctrl+F to search for a keyword from the job ad — "Kubernetes", "accounts payable", whatever matters — and confirm the viewer actually finds it in your file, not just in your intentions. Then open your exported DOCX back in Writer and compare it against the master, paying attention to table spacing and anything that used to live in a frame. LibreOffice's DOCX export is good, not lossless, and the difference shows up in exactly those places.

Once the mechanics are clean, the open question is whether the content earns an interview, and that's where a second read helps. A free CV analysis scores your uploaded PDF, Word file or image out of 100 and breaks it into five categories — experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility — alongside a visual layout analysis that shows how your structure reads. Paste the job description in and it lists the skills you're missing, then generates ATS-friendly rewrites in six templates that mirror the ad's keywords. Keep writing in LibreOffice for privacy; just don't guess about the file you send.

Frequently asked questions