NearPDF

2026-10-09

The IRS will reject a 501(c)(3) application that isn't one PDF — how to build the single file Form 1023 actually requires

The IRS's own FY 2025 Data Book puts a number on how many organizations go through this process every year: "The IRS closed 145,202 applications for tax-exempt status in FY 2025," and "approved tax-exempt status for 88.6% of these applications." Nearly all of those filings for 501(c)(3) status go through Form 1023 on Pay.gov, the federal government's own payment and forms portal — and Pay.gov gives an applicant exactly one place to upload supporting documents. Its own Form 1023 start page is direct about it: "You'll have to create a single PDF file (not exceeding 15MB) that you will upload at the end of the application." Not a folder of attachments, not one file per document — one PDF, assembled correctly, before the application can even be submitted. How NearPDF's merge, organize, rotate, and delete tools build that exact file, entirely on your device.

What has to be inside the one PDF, in writing

The IRS's own page on required attachments to Form 1023 spells out exactly what belongs in that single file, item by item: an "Organizing document (required)"; "Amendments to the organizing document in chronological order (required if applicable)"; "Bylaws or other rules of operation and amendments (if adopted)"; a signed "Form 2848, Power of Attorney and Declaration of Representative" if one applies; a signed "Form 8821, Tax Information Authorization" if one applies; "Supplemental responses" for any answer that "won't fit in the provided text field," plus any additional supporting information the organization wants to include; and, optionally, an "Expedite request." The same page adds a formatting rule easy to miss on a supplemental-response page: "Put the organization's name and Employer Identification Number (EIN) on each page of the supplemental response" and "identify the Part and Line number to which the information relates" — so a loose page of extra explanation has to carry its own identification, not just float at the end of the file hoping an examiner connects it to the right question. The IRS lists its attachments in that order without stating they must appear in that exact sequence, but matching it is the simplest way to hand an examiner a file organized the way the agency's own checklist already expects.

Separate files on your computer vs. the one PDF Pay.gov accepts Same Form 1023 attachments, two very different outcomes Separate files, no single PDF ArticlesOfIncorporation.pdf Bylaws_scanned.pdf (upside down) Form8821_signed.pdf PartV_explanation.docx → Pay.gov has nowhere to put four files After merge · organize · rotate Organizing document, first Bylaws, rotated right side up Form 8821, in order Supplemental response, EIN labeled → one PDF, under 15MB, uploaded once Pay.gov's own Form 1023 start page, verbatim "You'll have to create a single PDF file (not exceeding 15MB) that you will upload at the end of the application." Contents: organizing document, bylaws, Form 2848/8821 if applicable, supplemental responses, expedite request if applicable. "If your PDF file exceeds the 15MB limit, remove any items over the limit" and "contact IRS Customer Accounts Services at 877-829-5500." The IRS closed 145,202 applications for tax-exempt status in FY 2025 (88.6% approved). Sources: Pay.gov Form 1023 start page; IRS.gov Form 1023 attachment pages; IRS Data Book, FY 2025.
Same supporting documents, assembled two different ways — Pay.gov's upload field only accepts one of them.

The 15MB ceiling, and what happens when you cross it

Pay.gov's limit is specific and unforgiving: "You'll have to create a single PDF file (not exceeding 15MB) that you will upload at the end of the application." Scanned paper — a certified copy of articles of incorporation, an older set of bylaws run through an office scanner at high resolution — is usually what pushes a combined file over that line, not the typed portions of the application itself. Pay.gov's own instructions for what to do next are blunt: "If your PDF file exceeds the 15MB limit, remove any items over the limit" and "contact IRS Customer Accounts Services at 877-829-5500 for assistance on how to submit the removed items" separately. That's a real, avoidable detour — re-scanning a document at a lower resolution just to shrink it risks making it harder to read, exactly the kind of page an examiner might come back and ask about. Separately, IRS.gov's own page on electronic attachments confirms that typed answers run into the same single file, not a second upload: when a response "won't fit in the provided text field," "the organization can submit the balance of the response within the single PDF document required as part of Form 1023" — meaning a long answer to one question and a scanned bylaws page end up needing to live inside the very same file, assembled correctly, on the first try.

What NearPDF actually does for the assembly

Each piece the IRS's own attachment list names maps onto a specific NearPDF tool. The merge tool combines the organizing document, any amendments, the bylaws, a signed Form 2848 or 8821, the supplemental-response pages, and an expedite request into the one PDF Pay.gov's upload field actually accepts — instead of a folder of separate files it has nowhere to put. The organize tool reorders pages by drag-and-drop once everything is combined, so amendments land in the chronological order the IRS's own page requires and the rest follows the sequence its checklist already lists, rather than whatever order the files happened to be saved in. The rotate tool straightens a scanned organizing document or bylaws page a copier or phone camera saved sideways — a detail that matters directly, since a rotated, legible page is one an examiner can actually review, where a sideways scan often just gets flagged and sent back. And when the combined file creeps past Pay.gov's 15MB ceiling, the delete tool removes the specific pages pushing it over — a duplicate certified copy, a blank scanner-feed page, an oversized photo appendix — instead of re-scanning everything at a lower resolution, which is exactly the "remove any items over the limit" step Pay.gov's own instructions describe. None of this uploads anywhere to happen; the only upload that ever occurs is the one the organization makes itself, directly to Pay.gov, once.

The honest limits

NearPDF doesn't know whether your organizing document or bylaws actually satisfy your state's nonprofit corporation law, or whether your organization even qualifies for 501(c)(3) status in the first place — those are legal questions a founder, often with an attorney's or accountant's help, has to settle before a single PDF is ever assembled, and getting them wrong is a very different problem than getting the file format wrong. It can't verify that your EIN is correct, confirm a Form 2848 or 8821 was filled out and signed properly, or know which Part and Line a supplemental response is actually about — the IRS's own instruction to label that on every page is something the filer still has to do by hand. It also doesn't track where your application sits in the IRS's own queue: the "80% of Form 1023 application determinations within 191 days" figure, and the much shorter 22-day figure for Form 1023-EZ, come directly from the IRS's own site and have nothing to do with file assembly — an application that's correctly built can still take months to be reviewed. This isn't legal, tax, or nonprofit-formation advice, and nothing here replaces the IRS's own instructions or an attorney's review of your specific filing. What NearPDF handles is the mechanical step Pay.gov's own single upload field makes unavoidable: turning a stack of separate organizing documents, bylaws, forms, and responses into the one, correctly consolidated, under-the-limit PDF Form 1023 actually requires.