Should You Send Your Résumé as a PDF or a Word File?

Short answer: send a PDF, unless the job posting or the recruiter asks for a Word file. In that case send Word, without arguing. The longer answer is about what each format protects, and what a hiring system needs to read your résumé at all.

What a PDF gets you

A PDF carries its fonts and layout with it. The hiring manager opening it on a laptop, in a phone's email preview, or inside a browser tab sees the page you designed. A Word file gets laid out again on every computer that opens it. If the reader doesn't have your font, Word swaps in another one with different letter widths, and your tidy one-page résumé can push its last two lines onto a second page.

There's a smaller benefit too. A .docx can quietly carry tracked changes and comments you forgot to clear. Nobody wants a recruiter clicking “Show Markup” and finding a note to yourself about the salary.

When Word is the right call

• The posting or the application form asks for .doc or .docx. Follow the instructions; that's the whole rule.
• A recruitment agency asks for Word. Agencies often reformat candidates' résumés onto their own template before sending them to a client, and that's far easier from an editable file.

If the upload form accepts both and says nothing either way, a PDF with real, selectable text is a safe choice.

Can software actually read it?

Many employers run applications through an applicant tracking system that pulls the text out of your file and sorts it into fields. It reads the text itself, not the picture of the page, and that matters more than the format:

• The text has to be real. Try selecting a line in your PDF. If the whole page highlights like a photo, it's an image, maybe a scan or a design-tool export, and to software it's blank.
• Keep key details out of images. A logo is fine, but your name, email, and phone number should be typed text, not part of a banner graphic or written only next to icons.
• Go easy on columns. Two-column layouts can get read straight across the page, so your skills sidebar ends up interleaved with your job history. A single column is the safest.
• Use plain section headings like Experience, Education, and Skills rather than clever ones.

For a rough preview of what software gets, run your PDF through PDF to Text and read the result top to bottom. If it's jumbled or empty, a parser will struggle too.

Keep one editable master

Write and update the résumé in Word or Google Docs, keep that file as your master copy, and make a fresh PDF each time you apply. Our Word to PDF tool uses stand-ins for common Office fonts like Calibri, Arial, and Times New Roman that match their letter widths exactly, so line breaks hold. A less common font may get replaced by something close but not identical. Open the PDF before you send it and check the page count and the last line of each section. If anything moved, export from Word itself (File → Save As → PDF) or switch to a standard font.

Lost the original and only have the PDF? PDF to Word gets you an editable file back. Expect to tidy some spacing afterwards. A scanned PDF won't give you editable text this way, so for a scan, pull the words out with PDF to Text with OCR switched on and paste them into a fresh document.

Name the file for the person downloading it

A recruiter with forty attachments called resume.pdf will appreciate Priya-Shah-Resume.pdf. If you tailor it per role, add the role: Priya-Shah-Resume-Data-Analyst.pdf. Leave out version numbers and the word “final,” and skip accented letters in the file name, since some upload systems mangle them.

Common questions

Should I attach both a PDF and a Word version?

Usually not. Two attachments of the same document look indecisive and make the reader choose. Send the format they asked for, or a PDF if they didn't say, and offer Word if they want it.

Is a résumé from Canva or another design tool OK?

It can be, if the export keeps real text. Check by selecting a line in the PDF. Design templates also lean heavily on columns, icons, and text inside shapes, which are the exact things parsers trip over, so for online applications a simpler layout is the safer bet.