Plain Text Resume: When You Need One and How to Format It

A plain text resume is exactly what it sounds like: your resume with every formatting trick removed. No bold, no columns, no custom fonts, no decorative lines. Just characters, in order, top to bottom, saved as a .txt file. It's the least visually exciting format in existence. (And yes, I am aware that I've built a career around caring about this. My 14-year-old thinks it's embarrassing too.)

Most people never need one. Some people need one urgently and don't know it yet.

This guide covers what a plain text resume actually is, when you specifically need it, how to convert yours in five steps, and — the part most guides skip entirely — how to use the plain text conversion as a free ATS audit on your current resume before you submit a single application.

What a Plain Text Resume Actually Is

Open Notepad on Windows, or TextEdit in plain text mode on a Mac. Copy everything from your current resume and paste it in. What you see on screen is approximately what an ATS parser extracts from a two-column Word document it couldn't parse correctly.

Plain text contains no formatting codes, no embedded fonts, no column structures the parser has to guess at. There are no hidden XML tags defining where one section ends and another begins. The text runs top to bottom, in the order it appears, without any structural ambiguity.

That's the point. When you submit a plain text resume, what the parser receives is exactly what you submitted. No interpretation required. No garbled section headers. No job titles merged with sidebar content into an unreadable string that the algorithm flags as nonsense and discards.

It's not beautiful. It doesn't need to be. Its one job is to be readable by every system that will ever encounter it — including systems built in 1998 that haven't had a meaningful update since then. On that metric, it succeeds where many professionally designed resumes fail.

For comparison: a PDF exported from Canva looks impressive on screen. Taleo, the ATS used by thousands of large employers in banking, healthcare, and government, frequently extracts garbled text from Canva PDFs because the file structure doesn't embed text in the standard order. A plain text file gives Taleo nothing to misread. The tradeoff is that it also gives the human reader nothing to admire — which is exactly the tradeoff you're making when you choose this format.

When You Actually Need One

Three specific situations make a plain text resume the right choice. Outside these three, there are almost certainly better options.

Pasting into application forms

Many online application portals — particularly Taleo, older iCIMS installations, and most government job boards — include a text box where you paste your resume content directly. When you paste a formatted Word document into these boxes, results vary from slightly garbled to completely unreadable.

The paragraph breaks disappear. The two-column layout collapses into a single stream with no predictable order. Bullet points become blank spaces. The parser receives a scrambled version of your resume and scores it accordingly.

Plain text pastes cleanly. Every field, every date, every job title lands where it's supposed to, because there's no formatting to corrupt in transit.

Email submissions where the format is unspecified

Some smaller companies and organisations outside the US ask candidates to email their resume without specifying a format. If you don't know whether the recipient's email client will render an attachment correctly, pasting a plain text resume directly into the email body removes the variable. The content is the email. Nothing can go wrong with the attachment because there is no attachment.

This is less common now than it was ten years ago, but it still appears regularly in government contractor postings, academic hiring, and certain non-profit roles.

Old databases and legacy job board systems

Certain industries — federal contracting, large healthcare systems, legacy financial institutions — still run on Taleo builds that haven't been updated in years. These platforms have the most restrictive file handling of any ATS currently in use. They were designed when the primary submission format was literally a text file, and their parsers have never fully caught up with modern document structure.

ATSFixer runs test resumes through Greenhouse, Lever, Workday, Taleo, and iCIMS every week. Optimising for Taleo covers every platform — it's the most demanding parser in the group. Plain text is the format Taleo handles most reliably, because it's the format Taleo was originally designed to receive.

How to Convert Your Resume to Plain Text

Five steps. First time takes about ten minutes. After that, two minutes.

Step 1: Paste into Notepad or TextEdit

Copy the full text of your resume from Word or Google Docs. Open Notepad on Windows (search for it in the Start menu) or TextEdit on Mac (then go to Format → Make Plain Text before pasting). Paste manually.

Do not use Word's "Save As .txt" option. Word's export frequently adds encoding artifacts, stray characters, and line break inconsistencies that create problems downstream. Paste manually, in plain text mode, every time.

Step 2: Fix the order

If your resume had a two-column layout, the paste will likely scramble section order. Content from the left column and right column merges into a single stream based on the underlying file structure — which rarely matches what you see on screen.

Manually reorder everything: contact information at the top, then summary, then experience in reverse chronological order, then education, then skills. Top to bottom. No exceptions, no exceptions for any creative structural idea you had about putting skills first. Parsers expect this order. Give them what they expect.

Step 3: Replace formatting with text conventions

Plain text has no bold, no bullet points, no italic. You replace these with text signals that both humans and parsers can read:

• Section headers in ALL CAPS — EXPERIENCE, EDUCATION, SKILLS, SUMMARY
• A simple hyphen-space for list items (- like this)
• One blank line between sections
• Consistent date formatting throughout (Month YYYY, every time)

These conventions are readable by a parser built in 2024 and by a job board that hasn't had a UI update since the first Obama administration. Both audiences encounter plain text resumes. Both audiences can read these signals without difficulty.

Step 4: Check line length

Keep lines under 65–72 characters. Longer lines wrap differently across systems, sometimes breaking mid-word mid-phrase — not mid-sentence, but mid-word, which is the kind of thing that makes a recruiter's eyes slide right off the page. Set your Notepad window to approximately 80 characters wide and make sure nothing overruns that boundary. Bullet points should wrap at a natural break point, not mid-clause.

This is the rule most conversion guides forget to mention. It's also one of the rules most likely to cause problems if you skip it.

Step 5: Save as UTF-8

In Notepad: File → Save As → change the Encoding dropdown to UTF-8. In TextEdit, UTF-8 is the default for plain text files.

UTF-8 preserves special characters — accented letters in names, the occasional em dash you chose to keep — without substituting garbled symbols. ASCII is technically compatible with everything, but UTF-8 handles names and characters that pure ASCII doesn't. For a document that might travel through three different systems before reaching a human, UTF-8 is the safer choice.

Formatting Rules That Keep ATS Parsers Happy

These aren't aesthetic choices. They're technical requirements for a format that has, by definition, no formatting to fall back on.

• Section headers in ALL CAPS. EXPERIENCE, EDUCATION, SKILLS, SUMMARY. Parsers look for these exact patterns to identify where sections begin and end. ALL CAPS is the plain text equivalent of an H2 heading tag — it signals structure where there is no visible structure to signal it.
• Hyphens for list items. A simple hyphen followed by a space. No asterisks, no bullet character symbols, no en-dashes. A hyphen is readable across every system that will ever touch this file, including the ones that predate broadband internet.
• Spaces for indentation, never tabs. Tabs render differently in different systems. A tab that looks like four spaces in Notepad might render as eight characters in the receiving system, breaking the visual alignment of every indented line. Use spaces. Count them. Be consistent.
• No tables or columns. If you had a two-column skills grid, convert it to a comma-separated list or a single-column list. Parsers that handle tables at all handle them inconsistently. Don't give them a chance to get it wrong.
• No special characters. Em dashes, curly quotes, trademark symbols — replace them with plain ASCII equivalents. An em dash becomes two hyphens (--). A curly quote becomes a straight quote. These details matter for legacy systems running on 8-bit encoding where a special character becomes a placeholder box and then gets parsed as nothing.
• One field per line in the contact section. Name on line one. Phone on line two. Email on line three. LinkedIn URL on line four. No pipes, no inline separators, no creative arrangements. One field per line, every time.

The result looks minimal. That is the intended outcome. A plain text resume that looks boring is a plain text resume that's doing its job. (A plain text resume that looks impressive is probably trying to do something plain text structurally cannot support, and failing in ways you can't see until the parser reports back.)

The Part No One Mentions: Plain Text as an ATS Audit

Here's what most plain text resume guides skip entirely: you don't have to be submitting a plain text resume to benefit from running the plain text test.

Copy your current resume — the PDF or DOCX you're actively submitting to jobs — and paste it into Notepad. Read it. That's approximately what the ATS parser extracts from your document when it runs it through the system.

Most people are genuinely surprised by what they find. The order is wrong. The skills sidebar content lands in the middle of the experience section. Job titles are separated from their company names. Dates appear three lines away from the role they belong to. The contact information is in the header zone that some parsers skip entirely.

A software engineer came to us with a two-column resume he'd had professionally designed — skills sidebar on the left, experience on the right. He'd applied to dozens of roles without a single callback. When he pasted the resume into Notepad, the left and right column content had merged into a single scrambled stream. The parser was reading his name, then a skills bullet, then a job title, then his phone number — all in sequence, with no structural context. It had no idea where one section ended and another began. His ATS score: 12 out of 100. He switched to a single-column layout without changing a word of content. New score: 71. Interview request that same week.

ATSFixer data shows that 1 in 3 resumes submitted through Workday are corrupted during parsing due to columns, tables, or text boxes. The Notepad test catches every one of those problems before you submit. It costs nothing and takes 90 seconds. There is no reason not to do it before every application.

Open Notepad. Paste. Read it as if you're a parser that has no visual context, no assumptions about layout, no understanding of what a resume is supposed to look like. If the content doesn't make sense to you in that mode, it doesn't make sense to the algorithm either — and 63% of recruiters say they've rejected resumes for formatting issues alone, not missing qualifications.

This is the most useful thing a plain text resume can teach you, even if you never actually submit one.

A Plain Text Resume Template You Can Use

Copy this into Notepad or TextEdit directly. Do not open Word and paste it there first — the formatting will immediately begin trying to help you in ways that are not helpful.

FIRST LAST
(000) 000-0000
email@email.com
linkedin.com/in/yourprofile
City, State

SUMMARY
2-3 sentence summary with primary keywords from the job description.
Mirror the exact phrasing from the role. Not your phrasing. Theirs.

EXPERIENCE

Job Title -- Company Name
Month YYYY - Month YYYY (or Present)
- Accomplishment with a result or metric
- Accomplishment with a result or metric
- Accomplishment with a result or metric

Job Title -- Company Name
Month YYYY - Month YYYY
- Accomplishment with a result or metric
- Accomplishment with a result or metric
- Accomplishment with a result or metric

EDUCATION

Degree, Major -- Institution Name
Month YYYY

SKILLS
Skill One, Skill Two, Skill Three, Skill Four
Skill Five, Skill Six, Skill Seven

CERTIFICATIONS
Certification Name -- Issuing Body, YYYY

A few notes on using this template:

• The double hyphen in "Job Title -- Company Name" is two standard hyphens, the plain text equivalent of an em dash. Either reads correctly. The double hyphen is safer across older systems.
• Skills as comma-separated lines is more parser-friendly than a multi-column skills grid. The algorithm extracts individual terms either way, but a clean list eliminates any ambiguity about where one term ends and the next begins.
• Delete sections you don't have. A blank CERTIFICATIONS header with nothing under it confuses some parsers into treating the following section as certifications content. If you have no certifications, remove the heading.
• The summary is not optional for ATS. Keywords in the summary score twice — once as a dedicated parsed field, once in full-text search. Skipping it is like leaving half the scoring opportunity on the table. Not great, as tables go.

For a deeper look at how resume sections interact with ATS scoring, the guide to resume sections every ATS looks for covers the field weighting in more detail.

When Plain Text Makes Things Worse

Honestly: most of the time, a plain text resume is the wrong choice.

If you're applying to a company using a modern ATS — Greenhouse, Lever, Workday, or recent iCIMS installations — a clean single-column PDF parses correctly and looks professional to the human who opens it. You don't need plain text. What you need is a document without columns, text boxes, or embedded graphics, saved as a PDF with selectable text rather than a scanned image.

The difference matters. When a modern ATS receives a well-formatted DOCX or PDF, it extracts the text correctly and scores it against the job description. When a recruiter opens the same file, they see a professional document. A .txt file submitted to that same modern ATS scores identically on the algorithm — but when the recruiter opens it, they see something that looks like it came from a dial-up era. That's a disadvantage you created by optimising for a scenario that didn't apply to this application.

Honestly, most "ATS-optimised" resume templates on Canva and Pinterest are not ATS-optimised. They have columns, text boxes, decorative elements, and graphics that break every major parser. But the solution to that problem is a clean single-column PDF — not necessarily a plain text file. Plain text is the answer to specific, identifiable submission scenarios. It's not a universal upgrade from a poorly formatted document. It just trades one set of problems for a different one.

If you're applying to a company with fewer than 50 employees, they likely don't use an ATS at all. A hiring manager at a 20-person startup reads your resume the same way they'd read a menu — top to bottom, in whatever format it arrives. Don't convert to plain text for a human reader who'd prefer a document they can actually read comfortably. Save the plain text version for the systems that need it and send a formatted document everywhere else.

The rule of thumb: use plain text when the submission method explicitly requires it (a text box in an application form, an email body paste, a federal or legacy system), or when the Notepad audit reveals your formatted resume is being corrupted on parse. In every other case, start with a clean single-column resume format, test it with ATSFixer before you apply, and send the PDF.

Frequently Asked Questions

What is a plain text resume?

A plain text resume is a version of your resume saved as a .txt file with no formatting — no bold, no columns, no custom fonts, no bullet point symbols. All text is standard ASCII or UTF-8 characters. It's used when applying through systems that can't parse formatted documents correctly, such as old job board text boxes, government application portals, and legacy ATS platforms like Taleo.

When should I use a plain text resume?

Use a plain text resume in three situations: when pasting your resume into an online application form text box, when emailing your resume as body text rather than an attachment, and when applying to employers using legacy ATS systems (common in federal government, healthcare, and large financial institutions). For most modern job applications through Greenhouse, Lever, or Workday, a clean single-column PDF is the better choice.

How do I convert my resume to plain text?

Copy your resume content from Word or Google Docs and paste it manually into Notepad (Windows) or TextEdit in plain text mode (Mac). Fix the section order manually if it scrambled during paste, replace bullet points with hyphens and section headers with ALL CAPS, keep lines under 65–72 characters, and save as UTF-8 encoding. Do not use Word's "Save As .txt" — paste manually for cleaner results.

Is a plain text resume better for ATS?

Not universally. Modern ATS platforms — Greenhouse, Lever, Workday — parse clean single-column PDFs correctly. Plain text is better for legacy systems like Taleo and old iCIMS installations that struggle with complex document formatting. The safest approach is to run the Notepad test on your current formatted resume: copy and paste it into Notepad to see what a parser actually extracts. If the result is garbled, fix the formatting before using plain text as a last resort.

How do I format a plain text resume?

Use ALL CAPS for section headers (EXPERIENCE, EDUCATION, SKILLS). Use a hyphen-space for list items. Use spaces for indentation, never tabs. Keep contact information one field per line. Avoid special characters like em dashes, curly quotes, and trademark symbols — replace them with standard ASCII equivalents. Keep line lengths under 65–72 characters to prevent mid-word line breaks in systems with narrow text fields.

How do I save a plain text resume?

In Notepad: File → Save As → set the file name with a .txt extension → change the Encoding dropdown to UTF-8. In TextEdit on Mac, plain text mode is selected under Format → Make Plain Text before saving. UTF-8 encoding preserves accented characters and special punctuation without substituting garbled symbols. Save with a clear filename — FirstLast_Resume_PlainText.txt — so it's identifiable in an inbox or application queue.

What's the difference between submitting a PDF and a plain text resume?

A PDF with selectable text (not a scanned image) is parsed by modern ATS systems and looks professional to human readers. A plain text .txt file is parsed reliably by both modern and legacy systems but looks minimal to a human. For most applications, a well-formatted PDF is the better submission. Plain text is the fallback for application forms that won't accept file uploads, email body submissions, and legacy systems where PDF parsing is unreliable.

Can I use Notepad to check my current resume before applying?

Yes — and this is one of the most useful things you can do before any application. Copy your current resume content from whatever format you're using and paste it into Notepad. Read what comes out. That's approximately what an ATS parser extracts from your document. If the content is out of order, garbled, or missing sections, fix the underlying formatting before you apply. ATSFixer data shows that 1 in 3 resumes submitted through Workday are corrupted during parsing due to columns and text boxes — the Notepad test catches all of them in 90 seconds.