Combine PDFs and images into an organized submission package with cover, section dividers, document index, page numbering, source ZIP, checksums, and final size/page preflight.
PDF bytes, image pixels, section names, generated indexes, ZIPs, and checksums stay in this browser. Nothing is uploaded to OpenFileTools.
1
Add and inspect sources
Build from PDFs and images without flattening everything.
PDF pages are copied structurally where possible. JPG, PNG, and WebP sources become static image pages. Originals can be preserved in the companion source ZIP.
Add PDFs and images to begin building the package.
Why this tool is different
Submission portals often require more than a merged PDF: supporting documents need a deliberate order, readable sections, a clear index, a predictable filename, and a final package that actually fits the portal's page and byte ceilings. This builder creates that package locally, preserves source files separately when requested, and validates the saved final PDF instead of assuming the plan will pass.
Requirements and recommendations
Build the package around the destination's real limits
Add the PDFs and images that belong in the submission, then review every source before combining.
Order sources, include or exclude individual PDF pages, and give each source a clear section title.
Choose optional cover, document index, section dividers, page numbering, and original-source ZIP output.
Enter the destination's final PDF filename, maximum bytes, and maximum pages, then judge the actual generated file against those limits.
If the byte ceiling still fails, use the explicit Compress PDF handoff and bring the compressed result back to recheck it against the same reviewed package.
How OpenFileTools processes it
Local processing, explicit choices.
OpenFileTools inspects every source locally, copies selected PDF pages with the browser PDF engine, embeds selected images onto generated paper pages, adds only the cover/index/divider/page-number elements you choose, saves one new PDF, reopens it for validation and all-page preview, then creates optional CSV, checksum, and source ZIP companion artifacts entirely in this browser. If an explicit compression step is needed, its returned PDF can be brought back for page-geometry checks, complete preview, fresh checksums, and re-evaluation against the same final limits.
Quick technical summary
What this tool changes.
Property
Behavior
Processing
Browser local; no source upload to OpenFileTools
Inputs
PDF, JPG, PNG, WebP
Primary output
One generated submission PDF
Companion outputs
Optional source ZIP, document-index.csv, checksum-manifest.txt, package ZIP
Strong compression
Explicit Compress PDF handoff, followed by optional replacement-PDF recheck in the builder
Organize supporting documents before combining them
Add PDFs and JPG/PNG/WebP images, inspect every source, order the source files, and open a PDF only when individual pages need to be excluded or moved. The simple Merge PDF route remains available for users who only need a basic concatenation.
Existing PDF page geometry is preserved when pages are copied.
Images are fitted onto generated Letter or A4 pages without stretching.
Section titles drive divider and document-index labels.
Generate navigation and companion evidence explicitly
The builder can add a cover, document index, section dividers, and page numbers, then create companion files for the source archive, document index, and SHA-256 checksum manifest. Every extra artifact is generated locally from the reviewed package plan.
source-files.zip preserves the selected original source bytes.
document-index.csv records section order, source filename, included source pages, and final start page.
checksum-manifest.txt hashes the generated PDF and original source files with SHA-256.
Recheck the actual final PDF against portal limits
The final PDF is reopened after saving, its real byte size and page count are measured, and the configured filename limit is applied to the actual download name. If a byte ceiling still fails, the tool offers an explicit local handoff to Compress PDF instead of hiding a destructive compression step inside package generation. The compressed result can then be brought back to this page for page-count and page-geometry checks, complete preview, refreshed checksums, and the same final-limit evaluation.
READY means only the configured technical checks pass.
Combining signed PDFs can invalidate digital signatures.
Document-level forms, bookmarks, attachments, scripts, and accessibility structures may not survive page copying unchanged.
Frequently asked
Questions, answered.
How is this different from Merge PDF?
Merge PDF combines PDFs in order. Submission Pack Builder adds mixed PDF/image sources, per-PDF page inclusion and order, section titles, cover/dividers, a document index, page numbering, companion files, and final technical preflight.
Does the source ZIP contain the generated PDF instead of my originals?
No. source-files.zip is built from the original selected file bytes. The generated submission PDF is a separate artifact.
Will signed PDFs remain digitally signed after combining?
Do not assume that. A new combined PDF is a different document, and the original signatures generally do not cover it. The builder surfaces this limitation and detects common signature evidence as a warning.
Does READY guarantee filing or application acceptance?
No. It means only that the configured PDF format, byte, page-count, and filename checks pass for the generated file.