2026-07-28

How to merge your resume, cover letter, and transcripts into one PDF for a job application

A huge share of job applications now funnel through some kind of applicant tracking system before a human ever opens the file — Jobscan's 2025 report on the Fortune 500 detected a usable ATS behind 97.8% of those companies' career pages, 489 out of 500, a number that's barely moved in years (98.2% in 2018, 98.8% in 2019, 97.4% in 2023, 98.4% in 2024). Many of those systems, and plenty of smaller companies' plain web forms besides, ask for exactly one file: your resume, cover letter, and sometimes transcripts, certificates, or work samples, uploaded as a single attachment. That single requirement is where a surprising number of avoidable mistakes happen — not because merging PDFs is hard, but because nobody tells you what merging quietly does and doesn't do to the pages you're combining.

Why "just attach one PDF" shows up so often

Some of this is genuinely about parsing — a single well-formed file is simpler for automated systems to ingest than three separate attachments arriving in an unpredictable order. Some of it is just upload-form design: Greenhouse's own support documentation lists .doc, .docx, .pdf, .rtf, and .txt as accepted formats with a 100MB ceiling per file, generous enough that a merged resume-plus- cover-letter-plus-transcript file will almost never be the problem — but plenty of other portals are far stricter, and the honest answer is that limits vary enough by platform that checking the specific posting is the only way to know for sure. Either way, Indeed's own career-advice guidance is worth repeating here: combine documents into one file specifically when an employer's instructions ask for that, not as a default habit, since some application systems genuinely expect resume and cover letter as separate uploads and penalize neither format for using it correctly.

Get the order — and the filename — right first

When a job posting does call for one combined file, order is not cosmetic. A common convention, per Indeed's guidance, is cover letter first since it functions as an introduction to what follows — but that's a default, not a rule, and instructions that specify an order should always win. Whatever order you land on, a clean page break between documents (rather than a stray half-empty page) and a plain, professional filename — your full name, nothing decorative, no version numbers left over from "resume_v4_FINAL_final2" — go a long way toward looking like someone who assembled the file on purpose. None of this requires special software: it's mostly about deciding the order before you start merging, since reordering pages after the fact in most tools means either starting over or manually dragging pages back into place.

The page-size trap nobody warns you about

Here's the part that catches people off guard: merging PDFs does not resize or standardize anything. A PDF page stores its own dimensions, and a merge tool that copies pages from one file into another copies that stored size along with everything else on the page — it does not scale a letter-size resume and an A4-size scanned transcript to match each other. If your resume was exported at US Letter (8.5" × 11") and a transcript or certificate was scanned on equipment set to A4 (8.27" × 11.69"), the merged file will genuinely contain both sizes side by side, page after page, with no resizing happening automatically. The same applies to orientation: a scanner or scanning app commonly captures a page in whatever orientation the sensor was in and then just marks that page as rotated for display, rather than re-encoding the image right-side-up — so a "landscape" page in your merged file is often really a portrait-sized page carrying a rotation flag, not a page that's actually wider than it is tall. Both facts are properties of the PDF format itself, not a bug in any particular merge tool — see NearPDF's own rotation post for the full mechanics of how that per-page rotation value works.

If the scanned page needs to be machine-readable, not just human-readable

There's a second, separate issue with scanned pages worth knowing about if the receiving system is an ATS: a scanned image has no text layer at all, and parsing software built to read resumes is explicit about what that means for it. One ATS vendor's own support documentation puts it plainly — "the ATS can't 'see' the text to parse it," because "the computer sees only an image, not the individual words," no matter how legible that image is to a person. The same article gives a quick way to check any PDF yourself before you submit it: try to click-and-drag to highlight text on the page. If text highlights, there's a real text layer underneath and parsing software can read it; if nothing highlights, that page is functionally a photograph, regardless of how it looks. This mostly matters for scanned transcripts, certificates, or reference letters merged in alongside a "real" text resume — the resume pages will parse, the scanned pages won't, and no merge tool changes that, because turning an image into machine-readable text is an OCR step, not a merging one.

A practical workflow

Put together, a realistic sequence for assembling a job-application PDF — entirely inside NearPDF's merge workspace, with nothing uploaded anywhere — looks like this: add your cover letter, resume, and any scanned transcripts or certificates to the workspace; drag pages into the order the posting asks for (or cover-letter-first if it doesn't specify); rotate any scanned page that's landed on its side using the same per-page rotate control described in NearPDF's rotation post; delete any blank divider pages a scanner added; and, if the combined document is long enough that "see page 6" needs to mean something unambiguous later, add page numbers before the final save. Save the result with a plain, professional filename. Before you actually submit it, open the finished file once and skim it in order — that thirty-second check catches an out-of-order page or a still-sideways scan far more reliably than assuming the merge went exactly as planned.

The honest limits, restated

None of this makes a scanned transcript's dimensions match your resume's, and none of it puts a text layer under a photograph of a document. NearPDF's merge tool reorders, rotates, deletes, and numbers pages, entirely on your device — it does not resize pages to a common size, and it does not run OCR. If a portal specifically requires a searchable, parseable transcript rather than a scanned image, the honest fix is getting a text-based version of that document (a school's official electronic transcript, for instance) rather than expecting any merge tool, this one included, to manufacture a text layer that was never there. For the much more common case — getting your own resume, cover letter, and supporting pages into one correctly-ordered, right-side-up file before a deadline — that's exactly what merging one PDF, entirely in your browser, is for.