Turn a Rough Resume Draft Into a Polished PDF

Plenty of resume advice assumes you're starting from nothing. Often you're not — you have an old resume, a half-finished Word document, or a wall of notes about your last three jobs. The writing exists; what's missing is a document you'd actually be willing to send.

That's a different, much faster job than writing a resume from scratch. Here's the whole path.

Step 1: Get your existing content in, don't retype it

The slowest possible approach is opening a blank builder and copying your draft across field by field. Skip it. Most modern builders can take an existing file — PDF, DOCX, or pasted plain text — and pull your name, roles, dates, and bullets into structured fields automatically.

In our builder, that's the import flow: upload the file you already have (or paste the text), and it extracts your details into editable fields rather than making you re-enter them. What takes twenty minutes by hand takes about thirty seconds, and you spend your actual effort on the part that matters — fixing the content, not transcribing it.

Two things to check after any import, in any tool: dates (formats get mangled more often than anything else) and bullet structure (a paragraph that should be three bullets sometimes lands as one block). Both are quick to fix once, and neither is worth avoiding import over.

Step 2: Fix the content before you fix the design

The temptation once your text is in is to start picking fonts. Resist it for five minutes and do the higher-leverage pass first:

• Cut anything that isn't earning its line. Old jobs unrelated to what you're applying for now, "References available upon request," duties that could describe anyone in the role.
• Put a number in your top three bullets. If a bullet says what you were responsible for rather than what changed because of you, it's not finished — how to make a resume stand out covers this in depth.
• Match the posting's language. If the job says "SQL" and your draft says "database experience," change it. That's the single highest-value edit for getting past screening software, per our ATS-friendly resume guide.

Ten minutes here does more for your chances than any amount of template shopping.

Step 3: Pick a layout and check it at real page size

Now the design. The thing to watch isn't which template looks nicest in isolation — it's how your specific content sits in it. A draft with five jobs and long bullets fills a page very differently than one with two jobs, and a layout that suits one will look sparse or cramped in the other.

This is where a true-to-size live A4 preview earns its keep: you can see immediately whether you're at one tight page or spilling three lines onto a second one. If a layout doesn't fit your content, switching templates in a builder that keeps your text intact costs seconds, so it's worth trying two or three before settling.

Step 4: Export the PDF — and check it's a real one

Export as PDF, not Word. A PDF holds its layout on every device and email client; a .docx can reflow depending on who opens it and which fonts they have.

Then run one quick check most people skip: open the exported PDF and try to select your name with the cursor. If the text highlights, you have a real text-based PDF that screening software can read. If nothing selects, the file is effectively an image, and an ATS will extract nothing from it no matter how good the resume is. Our guide to evaluating a builder's ATS compatibility covers what else to look for in the exported file.

Also worth confirming: no watermark, and no missing final section because a free tier truncated the export. Both are common enough to check for rather than assume.

Step 5: Export a TXT version too — here's when you'll want it

A plain-text (.txt) export is a genuinely useful second file, and most builders don't offer one. Three situations where it saves you:

• Application forms with a "paste your resume" box. Pasting from a PDF often drags in broken line breaks and stray characters. Pasting from clean plain text doesn't.
• Older or stricter ATS portals that specifically ask for plain text, or that visibly mangle uploaded files.
• A quick readability sanity check. Plain text is roughly what a parser sees. If your resume still reads in a sensible order with all the important content present as text, it'll parse well. If sections appear scrambled or something's missing entirely, that's a real formatting problem worth fixing.

In our editor, both formats are on the Download menu, both watermark-free on the free plan. Export the PDF for the actual application, keep the TXT around for paste-into-a-box forms and as a parser preview.

The whole thing, end to end

Import your existing draft → cut and sharpen the content → pick a layout and check it at real page size → export a text-based PDF → keep a TXT copy for paste-in forms. Fifteen minutes, most of it spent on the writing rather than the formatting, which is the right split.

Frequently asked questions

Will importing my old resume lose my formatting? It intentionally discards the old formatting and keeps the content — that's the point. Your text moves into structured fields, then a template supplies fresh, consistent formatting. If you liked your old layout, you're better off picking a similar template than trying to preserve the original file's styling.

Should I send the PDF or the TXT version to employers? PDF, essentially always. TXT is a utility file for paste-into-a-box forms and for checking how a parser sees your content — not something to attach to an application unless a posting explicitly asks for plain text.

My draft is just notes, not a real resume. Does this still work? Import handles messy input better than you'd expect, but the more it looks like a resume (roles, companies, dates, bullets), the cleaner the extraction. If your notes are truly unstructured, our 8-step guide to making a resume is the better starting point.

Is exporting to PDF from Word good enough? It can be, if the layout is ATS-safe and the export produces selectable text. The common failure isn't the PDF conversion itself — it's that the underlying Word template uses tables, text boxes, or header-trapped contact info that parse badly. Run the select-the-text check either way.