NearPDF

2026-09-09

FAFSA opens October 1 — how to combine, and when not to combine, your verification documents into one PDF

Every fall, two FAFSA deadlines run at the same time and get confused with each other. One is the calendar date everyone reads about: the next FAFSA form opens to the public, and by law that opening cannot slip. The other is quieter and much more mechanical — a student already flagged for verification has to get a specific stack of tax and identity documents into a specific financial aid office portal, in a specific shape, by a school-set deadline that gets far less press. This post is about the second deadline, because it is the one where a page-level PDF tool actually helps, and because the instructions students find — when they read them at all — turn out to contradict each other from one school's website to the next.

The date that cannot move

The open date is not a tradition, it is a statute. Under the FAFSA Deadline Act, an amendment to the Higher Education Act of 1965 passed after 2023's disastrous rollout, the Department of Education "must certify the form's launch by September 1, and launch by October 1" every year, with no exceptions written into the law. The Department certified the 2026–27 form on that schedule, and the 2027–28 FAFSA is on track to do the same: general availability on October 1, 2026, per the Department's own certification process.

Verification runs on a separate, quieter clock that most students only discover after they are already on it. The 2026–2027 Federal Student Aid Handbook is the manual schools themselves follow, and its verification chapter says a student's FAFSA Submission Summary and Institutional Student Information Record "will indicate if a student is selected for verification," after which the school "must require students selected for verification ... to submit the documentation by the date specified by your school." The Handbook requires the school to hand the student three things — "a clear explanation of their role in the process," "a list of documents they need to submit," and "deadlines they must meet and the consequences of failing to meet them" — but it leaves the actual mechanics of assembling those documents entirely up to each school's own portal. That gap is where the contradictory advice lives.

"Combine it" and "don't combine it" are both right, for different documents

Read enough financial aid office FAQ pages and you will find both instructions stated as firm rules, sometimes by different offices in the same state. The University of Houston's document upload instructions say plainly that "documents comprised of multiple pages should be combined into a single PDF file first, and then uploaded," and give the exact example that matters here: "if your tax transcript consists of 6 pages, please scan all 6 of those pages and save it as one PDF file." UCF's financial aid office answers the seemingly opposite question — can I upload all of my required documents in one file? — with "No, it is not recommended. To prevent delays in processing, we recommend that you create one file for each required document," naming parent tax documents and student tax documents as the example pair that should stay apart, each under UCF's 3 MB per-file cap.

The two rules are not actually in conflict; they are answers to different questions. UH's own page states the boundary directly: "if the multiple scanned pages are applicable to multiple To-Do List items, you must separate them so that only the correct documents are being uploaded into the appropriate To-Do List item." Put together, the rule every school is really applying is: combine the pages that belong to one document, keep separate the documents that answer separate requirements. A six-page transcript is one document split across six scans — merge it. A parent's tax return and a student's tax return are two different checklist items that happen to both be "tax documents" — keep them apart, even though nothing about the paper itself tells you that.

The two file types that get rejected everywhere, NearPDF included

Underneath the combine-or-separate question sits a second, purely mechanical one: what actually counts as an acceptable PDF. UIC's financial aid office publishes a short Document Upload Guide that bans two file types by name: "Do not use 'PDF Portfolio' or 'Secured PDF' file types," and separately, "File should not be password protected." The guide also states a rule that maps directly onto a merge tool's page order — "the worksheet you are submitting should be the first (or top) page of your packet" — and a scanning instruction worth following before you ever open NearPDF: "Scan each side of your document(s) if it is double sided with information."

A Secured PDF is exactly the password-protected file the guide separately warns about, and it is also the one category NearPDF cannot open at all. NearPDF's merge and split engine loads every file with pdf-lib's PDFDocument.load(); when that call reports the file is encrypted, NearPDF does not silently drop it — it lists the file by name as "password-protected and skipped" (see loadAll() in src/merge.worker.js). That is a useful early warning, not a limitation to fight: a file NearPDF refuses to open is, by UIC's own written rule, a file the financial aid portal will refuse too. Remove the password before you scan it into anything, not after.

A PDF Portfolio is a different failure mode, and a sneakier one, because the file opens fine. A portfolio is built around separate embedded documents bundled behind a single cover file, not a shared page tree — which is exactly why Adobe's own portfolio feature shows a cover screen first and loads each contained file separately when you click into it. A page-based tool that reads a PDF's own page tree, as NearPDF's merge and split tools do, only ever sees the pages the portfolio file itself exposes — typically just that cover — not the documents bundled inside it. That is also, presumably, exactly why UIC bans the format outright rather than leaving it to trial and error: there is no reliable way for either a school's intake system or a page-level tool to know a document is missing until someone opens the result and finds one page where there should be six.

Same subject, different files: what to merge and what to keep apart Based on published upload rules from three U.S. financial aid offices (UH, UCF, UIC). Combine into one PDF Keep as separate files All 6 pages of one tax transcript one document, several scan passes → merge tool, in page order Parent tax documents vs. student tax documents two separate checklist items — merging them delays processing, per UCF's own FAQ Both sides of a double-sided page front and back of the same sheet → rotate if needed, then merge in order Signed worksheet vs. the ID it references often two separate checklist rows — check the portal's own list before merging either one in Rule that applies before either column: put the worksheet or cover sheet on top UIC: "the worksheet you are submitting should be the first (or top) page of your packet" Rejected everywhere, NearPDF included Password-protected ("Secured") PDFs — NearPDF names the file and skips it PDF Portfolios — a page-based tool only ever sees the cover, not the files inside
What three real financial aid offices actually ask for: merge same-document pages, keep different requirements separate, and neither a portal nor NearPDF can open a locked or portfolio-style file.

Building the actual files with NearPDF

Start from the scans, not from a blank workspace. Photos and scanner output that already sit as individual PDF pages — most phone scanning apps and every flatbed scanner's own software save straight to PDF — go into NearPDF's workspace, one requirement at a time. Two small cleanup steps are worth doing before anything gets merged, because a phone-scanned stack of financial documents almost always needs them: a page shot at an angle or upside down should be straightened with the per-page rotation control before you save, and any stray blank page a double-sided scan pass leaves behind a single-sided sheet is worth deleting the way the blank-pages workflow describes, rather than sending a financial aid office a packet with an unexplained empty page in it.

Once a single document's pages are in the right order — worksheet or cover sheet first, exactly as UIC's guide asks — the merge tool combines them into that one file. The part worth resisting is merging further than that: a parent's and a student's tax documents, or a signed worksheet and a separately-required identity document, stay as their own files even if you happen to build both in the same NearPDF session, because the portal on the other end is checking them off as separate line items. Nothing in NearPDF enforces that boundary for you — the tool only knows about the pages you feed it, not your school's checklist — so the checklist itself, not the workspace, is what decides where one PDF ends and the next one begins.

The honest limits

NearPDF's own size ceiling is generous by design — 500 MB total on a normal desktop, or 50 MB per file and 100 MB total on phones and low-memory devices — and every school's cap in this post is far below that: UCF's 3 MB per file, UIC's 5 MB, UH's 25 MB per PDF. That gap matters in one direction only. NearPDF's own limits will essentially never be the bottleneck; your school's will be, and NearPDF has no compression feature to close that gap after the fact — the only way it makes a file smaller is by removing pages. If a merged file comes out over your portal's limit, the fix has to happen upstream, at the scan itself: rescan at a lower resolution (UIC's own guide already tells students to "scan in the lowest resolution that results in a legible document"), not in NearPDF after the pages are already combined.

NearPDF also cannot repair a document that arrives as a Portfolio or with a password already on it — both have to be fixed, or requested again in a plain, unlocked form, before they reach the workspace at all. And nothing here tells you whether you are actually selected for verification, or what your specific school's checklist contains: that notice comes from your FAFSA Submission Summary and your financial aid office, exactly as the Federal Student Aid Handbook describes, not from a PDF tool. What NearPDF actually does is the mechanical half once you already know what is required — turning scans that already exist into files shaped the way each rule on this page actually asks for, entirely on your device, before any of them reach an upload button.