The Resume File and Delivery Reference, One Row per Format and Channel

You are about to send the same resume to another destination, and the only open question is which file and which name. This reference is for the volume applier who is submitting one set of materials across dozens of channels and does not want to re-argue "PDF versus Word" at every posting. Find the row for your exact channel and file type, send the version that parses, and move on.

Every public answer treats this as one debate with one answer, and it assumes a single channel: the portal upload. That is wrong. The paste box, the recruiter email, the referral forward, the shared link, and the image-export trap each behave differently, and a choice that is correct for one silently fails another. So this is organized as a lookup, not an essay. Read the two tables and the failure-mode section closely; skim the rest.

What does the format choice actually decide?

The format choice decides whether a machine can read your resume at all, and the two published tests I have agree on the direction even where they disagree on magnitude. DOCX is the lower-risk default; a text-based PDF is a close second on modern systems; a designed or image PDF is a silent failure.

The clearest single number is the gap between what a file looks like and what a parser sees. One test across six major ATS platforms scored DOCX at 97%, text-based PDF at 76%, and designed PDF at 53%. A separate test scored DOCX at 96.7% against 91.3% for text-based PDF. Treat these as vendor-run estimates rather than audited benchmarks, but the ranking is stable across both.

The derived gaps from Test 1 are what matter for a default rule: DOCX beats designed PDF by 44 points and text PDF by 21 points. That is why, when you do not know the system, DOCX wins. It is also why the "always PDF" advice you see everywhere is only safe when a human opens the file directly.

Which file goes to which channel?

Match the artifact to the channel, not to a universal rule. The short version: DOCX for unknown and legacy portals, text-based PDF for modern portals and human email, plain .txt for paste boxes and no-attachment email, and an attached file rather than a link for referrals.

The reason a single rule fails is that channels differ in what touches your file first. A portal hands it to a parser. A paste box hands it to a form field that strips styling. A recruiter reads an email attachment with human eyes. A shared link depends on permissions you set and filters you do not control. Here is the lookup, one row per channel.

• Portal upload, unknown or legacy ATS: Send DOCX, single column, contact in the body. This covers Taleo and iCIMS, the strict legacy engines where PDF section-extraction can fall below the roughly 80% reliability floor.
• Portal upload, modern ATS (Greenhouse, Workday): Text-based PDF is fine; Greenhouse shows no measurable DOCX advantage, and Workday handles both equally. Keep it single column either way, because multi-column layouts break in both formats.
• Paste box: Paste from a maintained plain .txt master. Never paste from a styled document.
• Recruiter email, attachment allowed: Text-based PDF so the human sees clean formatting; it reads directly and the parse risk is low.
• Recruiter email, no attachments (some anti-spam policies): Plain text in the body, taken from your .txt master.
• Referral forward or shared link: Attach a file. If a link is unavoidable, set access to anyone-with-the-link and test it in an incognito window.

What are the documented per-system limits?

Each ATS has hard limits that override your format preference, and they are published. Know the size caps and accepted types before you upload, because most silent failures happen inside these numbers rather than at the format layer.

The trap here is that the size a system will accept is far larger than the size it will parse. Greenhouse accepts files up to 100 MB but cannot parse anything over 2.5 MB. So a 4 MB file uploads with a green confirmation and yields no extracted data at all. Read the parse limit, not the upload limit.

Two rows deserve extra caution. Taleo ships with a 1 MB default attachment limit and no native parser unless a third-party integration is enabled, which is why a simple DOCX is the reasonable fallback when you see upload warnings. USAJOBS caps at 5 MB and, since September 27, 2025, at two pages, and it does not accept PDF portfolio files.

Text or image: the one test that catches a silent zero

Run the highlight test on every PDF before you send it, because an image-based PDF looks perfect and parses to near zero. This is the single highest-leverage check in the whole workflow, and it takes about thirty seconds.

Open the PDF in any browser and try to highlight a sentence with your cursor. If individual words select and you can copy them into a text editor, the file has a text layer the parser can read. If the cursor selects rectangular regions or highlights the whole page as one blue box, the file is an image and its ATS score will be near zero.

There is a subtler variant worth knowing. Some templates render section headers like "PROFESSIONAL EXPERIENCE" as a vector shape rather than text. The body highlights fine, but the header is parser-invisible, so the parser cannot find your experience section. Test the header text itself, not just the body paragraphs.

Upload succeeded and resume parsed are different events, and only one of them gets you read.

How to name the file so both machines and humans find it

Name the file first-and-last-name first, with a separator and a keyword, under 40 characters, no special characters. The filename rarely affects ranking, but it fails on both ends when it is wrong: validators block bad characters, and recruiters who search their own database by your name cannot find you.

The reason the human side matters is scale. In Refolk's index of professional profiles there are 137,853 recruiters and talent acquisition specialists in the United States, 9,792 in the United Kingdom, and 5,446 in Germany. That US figure is 14.1 times the UK and 25.3 times Germany. These are the people typing your name into a search box weeks after you applied, and a file called Document1.pdf is invisible to them.

Follow the convention below. If the posting states its own naming rule, that rule wins, because a stated convention is a compliance test disguised as a formatting note.

Priya_Raman_Data_Analyst_Resume.docx
Priya_Raman_Resume.pdf
Avoid: Resume.pdf, Document1.docx, priya-resume-FINAL-v3.pdf
Never use: & / # or other special characters

Note one system-specific quirk: Taleo's mobile paste-parse stores your pasted text as a file it names itself, in the pattern FirstName_LastName_RequisitionNumber_LanguageSymbol.txt, converting spaces in your name to underscores. You do not control that name, which is one more reason the paste box is its own channel with its own rules.

The procedure for one submission

Work one submission at a time, in order, and each step ends in a checkable "done" condition. This is the whole method; the tables above are what you consult inside steps 1 through 3.

Steps 5 and 6 have an ordering ambiguity worth naming: some guidance says name the file before you test the export, others say test first and name last. It does not matter for the parse result, so I put naming last to keep the human-facing detail out of the way until the file is proven readable. If you prefer, swap them.

At volume, steps 2 through 4 are where the time goes: reading each posting, tailoring the content, and exporting a clean artifact per destination. That is the friction Refolk is built to remove. Refolk writes your resume from your own history, tailors it to each posting, and scores how well you actually fit, so the per-submission work collapses to choosing the channel row and confirming the parse.

How this goes wrong: failure modes and false positives

Most failures here are silent, and they share a pattern: the file looks correct to you because you are the one person for whom it works. Each row below pairs the failure with the false positive that hides it and the local check that exposes it.

Two of these deserve emphasis. The Workday header strip is a channel-specific bug, not a design flaw: Workday removes headers and footers on extraction, so a contact block placed there vanishes from the parsed profile and the recruiter has no way to reach you. Put your email and phone in the document body. The Restricted-link failure is the most common technical miss on referrals: Google Drive files default to Restricted, so the recruiter hits access-denied and rarely requests access. Because you own the file, it always opens for you, which is exactly why you must test it logged out.

Where government and academic rules invert the private-sector default

Federal and academic systems flip the private-sector advice on purpose, so do not carry your portal defaults into them. Government advice recommends PDF, and academic platforms force it, for reasons that have nothing to do with legacy parsing.

USAJOBS routes through USA Staffing, which parses both PDF and Word reliably, so it states no format preference. It recommends PDF to preserve formatting and lock the page count, which matters because resumes are capped at two pages as of September 27, 2025 and 5 MB. It also accepts DOC, DOCX, RTF, TXT, ODT, and image types, but not PDF portfolio files. Academic hiring is stricter still: when you upload to a dossier service like Interfolio, the system automatically converts every document to PDF regardless of what you sent. In that world, the PDF-versus-DOCX question is moot, so spend your effort on layout and page count instead.

If your search spans employers on different systems, it helps to know which one a target uses before you submit. Refolk can surface that: a search like the one below returns the people whose stack tells you which row to use.

Keep the reference current and the batch consistent

Run the checklist below on every submission, and keep a version log so your materials stay identical across the cycle. The system-specific numbers here can change, so the durable skill is the check, not the current value.

Re-verify the moving parts by mechanism rather than memory. Size and parse caps are published in each vendor's support docs; confirm them when a posting names a system you have not used lately. Federal rules change by policy date, so the two-page limit and 5 MB cap are the kind of fact to re-check against USAJOBS help pages before a federal push. The highlight test never expires, because it tests a property of the file itself.

The payoff of the log is consistency at volume. When a recruiter calls three weeks later and pulls up "the resume you sent," you want to know exactly which version that was. Record the destination, the artifact, and the filename in one line per submission, and the whole cycle stays coherent even when you are applying to dozens of companies with the same core materials.