2026-08-22

Applying for an apartment in peak rental season? Combine your pay stubs, ID, and references into one clean PDF

Apartment hunting has a rush hour, and we're in it. Apartment List's research team has measured the rental market's seasonality directly: searches climb steadily from January to a July peak, and actual moves "begin ticking up in March and increase dramatically to their peak in August." The same team's pricing research finds rents hit their annual high in June and July, with summer bringing "20% to 30% more competition" for listings before the national median rent slides roughly 1.6% to its November low. Late August, in other words, is the tail end of the most crowded weeks of the rental year — and when several applicants want the same unit, the application that's complete, legible, and submitted first has a real edge. A surprising amount of that speed comes down to something unglamorous: whether your documents are ready as clean files before you find the apartment, or assembled in a panic after.

What you'll actually be asked for

The core list barely varies. Zillow's renter documentation guide and Apartment List's own checklist agree on the standard ask: a photo ID, proof of income — typically your most recent two to three months of pay stubs — plus rental history and references from previous landlords. Zillow's rental application, one of the most widely used online, lets an applicant upload up to five documents per income source to verify income: pay stubs, W-2s, tax returns, bank statements, employment offer letters, or rental-assistance documentation. Five slots sounds generous until you do the arithmetic on your own paperwork: someone paid biweekly has six or seven stubs covering three months, a freelancer might reasonably want to show a 1099, two bank statements, and an accountant's letter, and plenty of smaller landlords skip the portal entirely and ask you to email "your documents" — singular attachment strongly implied. Either way you end up at the same mechanical problem: more loose files than the channel comfortably takes.

One slot, one clean file

This is squarely a merge problem, and it's what NearPDF's merge tool does entirely in your browser: add each PDF — the stubs your payroll portal exports one at a time, the bank statement, the scanned reference letter — and every page appears together in one grid of thumbnails. Drag them into a sensible order (most recent pay stub first is the convention, since it's what a screener checks against the rent), rotate any page your phone scanned sideways, and save one file per upload slot — three months of pay stubs as a single PDF, say, instead of seven loose ones. If a landlord wants everything as one packet, the same merge handles that too: ID first, income documents next, reference letters last, one file with one clear filename like lastname-rental-application-2026-08.pdf. Two snags worth knowing in advance: payroll and bank portals sometimes export password-protected PDFs, and NearPDF can't open an encrypted file — it's skipped from the merge automatically, so remove that document's password first. And if you discover after merging that a landlord wants a different order, you don't redo anything: NearPDF's reorder tool opens the combined file and lets you drag its pages into a new sequence.

Send the pages they asked for — not your whole financial life

There's a quieter reason to prepare these files deliberately. A rental application packet is about as sensitive as personal paperwork gets — income, employer, account activity, ID — and Zillow's own help pages note that income-verification documents uploaded to its application remain viewable by the landlord for 60 days. You can't control that retention window, but you can control what's in the file. A bank statement export often runs dozens of pages when the landlord only needs the ones showing your name, the account summary, and the deposits that match your stated income. NearPDF's delete tool opens the statement, shows every page as a thumbnail you can preview full-size, and lets you remove the pages that aren't part of what was asked — locally, before anything is sent to anyone. One honest caution: deleting removes whole pages only. It is not redaction — NearPDF has no tool for blacking out an account number on a page you keep, so a page either stays in, complete, or comes out.

Where NearPDF's job starts and stops

The boundaries are the same ones NearPDF's other document-packet guides draw. Paper documents — a reference letter that arrived by mail, a paper stub — become PDFs with a phone scanning app first; NearPDF has no photo-to-PDF step, though the sideways page such scans tend to produce is exactly what the per-page rotate control in the merge grid is for, as covered in the rotation post. The page-order and mixed-page-size traps of merged application packets are the same ones described in the job-application merge post. And if you're sending documents to a landlord you found through a channel you can't verify — a too-good listing, a "landlord" who can't show the unit — the reasoning in the resume-watermarking post applies with more force here, because a rental packet contains strictly more sensitive information than a resume. Verification of who you're sending to comes first; no PDF tool substitutes for it.

The honest limits

NearPDF doesn't know any landlord's document list, doesn't verify that a pay stub is recent enough or that your income clears a screening threshold, doesn't compress a file that's over a portal's size limit, and doesn't redact anything. What it does is the assembly step in between: taking the PDFs your payroll portal, bank, and phone scanner already gave you, and turning them into the few clean, ordered files a rental application actually takes — merged, reordered, rotated, and trimmed entirely on your device, which is exactly where documents this sensitive should stay until the moment you choose to send them.