Preparing PDFs for job application portals

By Filemynt Editorial · Last updated July 28, 2026

Applicant tracking systems and portal upload limits reward a boring, clean, correctly sized PDF far more than a fancy one. A practical checklist before you hit submit.

The portal is stricter than it looks

Job application portals are often built on older infrastructure with tighter, more literal size and format limits than a modern inbox. A resume that emails fine can still get silently rejected — or worse, silently truncated — by a portal that expects something smaller and plainer than you assumed.

Treat the upload field's stated limit as a hard rule, and treat 'it uploaded' as only the first sign of success. If the portal offers a preview after upload, use it — some systems accept a file and then fail to parse it correctly on the other end.

One clean file beats several scattered attachments

If the application allows one document, combine resume, cover letter, and any requested writing sample into a single PDF in the order a reviewer would want to read them, using Merge PDF. A recruiter juggling dozens of applications is far more likely to open one well-ordered file than hunt through three separately named attachments.

Name the combined file clearly and boringly: FirstnameLastname-Resume.pdf, not resume_final_v3(2).pdf. The filename is the first thing a human or a system sees, and an unclear name creates a small but real bad first impression before anyone reads a word of content.

Watch for old metadata revealing more than you intend

Resume templates get reused, edited, and passed between jobs constantly, and document properties can quietly retain the name of whoever the file previously belonged to, or the name of a previous employer used as the original author field. Strip Metadata clears those hidden fields before you submit, so the file you send is exactly what it appears to be.

This matters more than it sounds — a resume with someone else's name buried in its properties, or a cover letter whose metadata still says 'Draft — DO NOT SEND,' has genuinely cost people interviews.

Keep portfolio and writing-sample PDFs lean

If you are attaching a portfolio or work samples with images, screenshots, or design mockups, those files can get large fast, and portal limits for job applications tend to run smaller than general email limits — often just a few megabytes. Compress PDF with Balanced settings usually keeps images legible while bringing the file back under a typical portal cap.

Check a few sample images at real size after compressing, particularly if the portfolio's whole point is visual quality. A design portfolio that arrives blurry undermines the exact thing it is meant to demonstrate.

Avoid formatting choices that fight applicant tracking systems

Many portals run resumes through automated parsing before a human ever sees them. Heavily designed PDFs — multi-column layouts, text embedded inside images, unusual fonts — can parse into scrambled or missing text on the system's side even though the PDF looks perfect to your eye.

This is a document-design issue more than a Filemynt issue, but it interacts with format choice: if a portal explicitly prefers Word over PDF for parsing reasons, that preference is worth respecting even if PDF is generally the safer, more consistent format for human readers. Read PDF vs Word for sharing for the broader tradeoff.

Do not password-protect an application document

Protecting a resume with a password might feel cautious, but recruiting systems generally cannot open encrypted attachments, and a locked file simply gets skipped or bounced. Passwords make sense for contracts and sensitive personal paperwork; they are the wrong tool for a document you are actively trying to get someone to open.

A pre-submit checklist

Combined into one file if the portal expects one, in reading order. Named clearly. Metadata stripped of any previous author or employer traces. Under the portal's actual stated size limit, checked with a real zoom-in if it contains images. Not password-protected. Previewed inside the portal if a preview option exists.

Prepare all of this in Studio on one upload — merge, strip, compress — so you are not reassembling the same document from scratch for every application with slightly different portal requirements.

Related tools

Keep reading

Next steps