If you’ve spent any time job hunting recently, you’ve probably run into this debate somewhere in a forum thread, a career coach’s LinkedIn post, or a recruiter’s offhand comment: should your resume be a plain text file, or a polished PDF? It sounds like a small technical question, but it actually sits at the intersection of two very different systems — the software that screens your resume before a human ever sees it, and the human who eventually does. Get the format wrong, and you can lose out on an interview before your qualifications are even considered.

This isn’t a matter of personal taste. Text and PDF resumes behave differently inside applicant tracking systems (ATS), render differently across devices, and send different signals to hiring managers. Below, we’ll break down exactly how each format performs, when to use which, and how to hedge your bets so a formatting mistake never costs you a job.

Why This Debate Even Exists

Twenty years ago, this wasn’t much of a question. You wrote a resume, saved it as a Word document, and emailed it or printed it. PDFs existed, but they weren’t the default expectation, and ATS software was primitive or nonexistent for most companies below the Fortune 500.

Today, an estimated 75–99% of large and mid-sized employers use some form of applicant tracking system to filter resumes before a recruiter ever opens one. These systems parse your resume, extract text, match it against keywords from the job description, and often rank or filter candidates automatically. That single shift — from “a human reads this” to “software reads this first” — is the entire reason the text-vs-PDF conversation exists at all. A format that looks great to a human can look like garbage to a parser, and vice versa.

What “Text Resume” Actually Means

When people say “text resume,” they usually mean one of two things, and it’s worth separating them because they behave very differently:

1. A .txt file — literally plain text, no formatting, no bold, no bullet points beyond dashes or asterisks. This is the most stripped-down version, often used when pasting directly into an online application form’s text box.
2. A “plain text formatted” resume saved as .docx or .pdf — a resume that avoids complex formatting (tables, text boxes, columns, graphics) but is still saved in a standard document format. This is what most career advisors actually mean when they say “keep it simple for the ATS.”

The second interpretation matters more in practice, because almost no employer wants a literal .txt file as an attachment — it looks unprofessional and strips out even basic readability. What they’re really asking for is a resume that is structured simply even if it’s saved as a PDF or Word file.

What Makes PDFs Attractive

PDFs became the default resume format for a good reason: they preserve exactly what you designed. Fonts, spacing, alignment, and layout look identical whether the file is opened on a Mac, a Windows PC, or a phone. For a document meant to represent your professionalism, that consistency matters. A resume that shifts fonts or collapses a two-column layout into a jumbled mess on a recruiter’s screen makes a bad first impression regardless of how strong your experience is.

PDFs also can’t be easily edited by someone else, which some candidates find reassuring — no accidental changes, no version drift between what you sent and what the employer opens.

Where PDFs Can Backfire

Here’s the part most job seekers don’t find out until it’s too late: not all PDFs are created equal from a parsing standpoint, and older or poorly configured ATS software can genuinely mangle them.

The failure modes tend to cluster around a few specific design choices:

• Multi-column layouts. Many parsers read left to right, top to bottom, in a single pass. A two-column resume can get scrambled — your job title from the left column merges with a bullet point from the right column, producing nonsense.
• Text boxes and graphics. Text placed inside a text box, icon, or image (like a “skills” section styled as an infographic) is sometimes invisible to a parser entirely. If your contact info sits inside a designed header graphic, some systems fail to extract it at all.
• Tables. Similar issue — table cells can be read out of order or dropped.
• Non-standard fonts or embedded images of text. If a PDF was generated by “printing” a designed image rather than exporting real selectable text, it may not be parsable at all.
• Older ATS engines. Some legacy systems, particularly at companies that haven’t updated their hiring software in years, handle PDFs worse than newer platforms like Workday, Greenhouse, or Lever, which have generally improved PDF parsing significantly.

None of this means PDFs are unsafe by default. A clean, single-column PDF built with standard fonts and no embedded graphics parses just as well as a plain document in the vast majority of modern systems. The danger comes specifically from design-heavy PDFs — the kind built to look impressive in a portfolio sense rather than to survive machine reading.

Where Plain-Text-Style Resumes Win

A resume built with simple, linear formatting — single column, standard section headers (Experience, Education, Skills), no tables or graphics — is close to bulletproof for ATS parsing regardless of whether you save it as .docx or PDF. There’s simply less for the software to misinterpret.

This is also why some job boards and company portals explicitly ask you to copy-paste your resume into a text box rather than upload a file. In that scenario, only the actual text matters; formatting is irrelevant because the system strips it anyway. If you paste a resume that was designed with visual formatting in mind, you’ll often see broken line breaks, merged words, or missing bullet points in the text box — a strong sign that the same resume, submitted as a file, could confuse a parser too.

The Human Factor: What Recruiters Actually Prefer

It’s worth separating the ATS question from the human-reader question, because they don’t always point the same direction.

Once a resume clears the automated screen, a recruiter or hiring manager is going to open it — and at that stage, a well-designed PDF generally reads better than a bare-bones document. Subtle use of bold, spacing, and a clean single-column layout helps a human scan your experience quickly, which matters when a recruiter is spending an average of six to eight seconds on an initial resume glance. A resume that looks like an unformatted wall of text can come across as low-effort, even if the content is strong.

There’s also the print/attachment factor. If a hiring manager forwards your resume internally, prints it for an interview panel, or opens it on a phone, a PDF guarantees it looks the same everywhere. A Word document might reflow oddly depending on the software version opening it; a plain text file has essentially no visual structure to lose or preserve.

So the honest answer is that PDFs still win for human-facing polish — the risk isn’t the format itself, it’s overdesigning the format.

So Which Should You Actually Use?

Here’s the practical framework, rather than a flat rule:

Use a PDF when:

• You’re uploading directly to a job posting as a file attachment.
• The application explicitly allows PDF (most do).
• Your resume uses simple, single-column formatting with standard fonts (Calibri, Arial, Georgia, etc.), no tables, and no text boxes.
• You want to guarantee visual consistency for human reviewers.

Use plain text (or paste as plain text) when:

• The application has a “copy and paste your resume” text box instead of a file upload.
• You’re applying through an older company career portal that explicitly warns about PDF compatibility issues.
• You’re emailing your resume directly in the body of an email as a backup to an attachment.

Avoid entirely, regardless of format:

• Multi-column “modern” templates from design-first resume builders, unless you’ve tested how they parse.
• Resumes where your name, email, or phone number are part of a graphic header rather than real text.
• Skill “graphics” like bar charts or star ratings representing proficiency — these are unreadable to both parsers and many humans.

A Simple Way to Test Your Resume Before You Apply

You don’t have to guess. A quick, practical test: open your PDF resume, select all the text (Ctrl+A or Cmd+A), copy it, and paste it into a blank text document or a plain email. If everything comes out in the correct order — your name, then contact info, then your most recent job with its bullet points, in the order you intended — your formatting is parser-friendly. If sections merge, bullet points disappear, or your contact information ends up in a strange location in the pasted text, your layout needs simplifying before you submit it anywhere with an unknown ATS.

This five-minute test catches the majority of formatting issues that would otherwise silently filter you out of consideration, and it works regardless of which resume builder or word processor you used to create the file.

Should You Submit Both Formats?

In situations where you’re not limited to a single upload — for example, when emailing a hiring manager directly or submitting through a portal that allows multiple attachments — there’s a reasonable case for keeping a plain, ATS-safe version on hand alongside your polished PDF, and sending whichever fits the application’s instructions. This isn’t necessary for every application, but it’s a useful habit if you’re applying to a mix of large corporate employers (more likely to run older ATS software) and smaller companies or direct outreach (where a well-designed PDF will make a stronger visual impression).

What you shouldn’t do is submit two different resumes to the same posting hoping one gets through — most systems will flag duplicate applications, and it can look disorganized.

The Bigger Picture: Format Is a Filter, Not a Substitute

It’s easy to get so focused on the text-vs-PDF question that you lose sight of the obvious truth: format determines whether your resume gets read, not whether it gets you hired. A perfectly parsable resume with weak, generic bullet points will still lose to a slightly riskier PDF with strong, quantified achievements — assuming it clears the ATS at all. Spend real time on the content itself: specific numbers, clear outcomes, and language that mirrors the actual job posting’s keywords, since most ATS platforms are doing keyword matching regardless of file format.

Think of formatting as a gate you need to pass through, not a strategy that wins the job on its own. Get the gate right — simple, clean structure, tested for parsing — and then put your real effort into making the content on the other side of that gate impossible to ignore.

Key Takeaways

• Most mid-size and large employers use ATS software to screen resumes before a human sees them, which is why format matters at all.
• PDFs are generally safe for modern ATS platforms, but only when built with simple, single-column layouts and no embedded graphics or tables.
• “Plain text” resumes matter most when an application specifically asks you to paste your resume into a text box rather than upload a file.
• Human recruiters still prefer the visual polish of a well-formatted PDF once your resume clears automated screening.
• Test your resume by copying and pasting its text into a blank document — if it comes out clean and in order, it will likely parse correctly.
• Formatting only gets your resume read. Strong, specific content is what gets you the interview.