Introduction
Reports, scanned records, portfolios and application packages often arrive as several PDFs and image files that must be delivered in one order. Desktop suites can perform the task, but quick browser-side merging removes installation and upload steps.
The utily.tools PDF & Image Merger accepts mixed files, supports drag-and-drop ordering and can produce a combined PDF or a long image depending on the selected workflow.
Page composition rather than text concatenation
A PDF is a structured collection of indirect objects, page trees, fonts, images and content streams. Two PDF byte sequences cannot simply be appended. A merger creates a new document and copies selected page objects while preserving their resources.
Raster images do not contain PDF pages, so the merger creates a page with dimensions derived from the image and embeds the compressed pixels into its content. Orientation and scaling determine whether the output preserves native dimensions or targets a standard paper size.
Technical foundations and behavior
A merger parses each source object graph, copies the selected pages and all reachable resources, remaps indirect object references, constructs a destination page tree and serializes a new cross-reference structure. Raster inputs require image objects, color-space metadata and page content streams that position the pixels in PDF user space.
Ordering and resource copying
The selected sequence becomes the destination page order. Copied pages must retain their media boxes and reachable fonts, images, graphics states and color spaces. Encrypted, malformed or rights-restricted sources require explicit policy and may not be safely processed.
Image dimensions and quality
Using pixel dimensions as PDF points changes physical print size because a point is 1/72 inch. A production workflow may read DPI metadata or scale into A4/Letter boundaries. Re-encoding through canvas can lose metadata and introduce JPEG artifacts.
Resource and complexity limits
Merging may hold compressed sources, parsed object graphs, decoded images and the destination simultaneously. Peak memory can greatly exceed file size, especially for raster content. Large workflows therefore need explicit size limits, incremental processing where possible and validation against decompression bombs or cyclic object graphs.
Real-world applications
Application package
A cover letter, form, certificates and scanned identification become one ordered PDF for submission.
Monthly reporting
Independently generated charts and departmental PDFs are combined into one consistent delivery artifact.
Photo documentation
Site photographs are ordered and embedded as pages alongside a written inspection report.
Standards and deeper technical reference
PDF object graph and page tree
PDF became ISO 32000 and represents a document as an object graph containing dictionaries, arrays, names, strings, streams and indirect references. The document catalog points to a page tree whose leaf Page objects define ordered pages. Each page references content streams, resources, media boxes, annotations and inherited attributes.
A merger cannot safely concatenate file bytes. It parses each source, copies selected page objects and every reachable dependency into a new object graph, remaps indirect references, builds a new page tree and writes a cross-reference structure and trailer.
| Feature | Why it is difficult | Practical expectation |
|---|---|---|
| Fonts and images | Referenced through page resources | Must be copied and deduplicated safely |
| Forms | Field names and shared AcroForm state can collide | May require flattening or field renaming |
| Bookmarks | Destinations reference source pages | Often not preserved by simple page copying |
| Digital signatures | Cover exact byte ranges | Any rewritten merged document invalidates prior signatures |
| Encryption | Objects depend on source security handlers | Usually requires decryption before copying |
| Tagged PDF | Structure tree connects semantic content to pages | Accessibility metadata may need specialized merging |
Converting images into PDF pages
An image is embedded as an image XObject and painted by a page content stream through a transformation matrix. Pixel dimensions do not define physical page size until mapped to PDF user-space units, conventionally 72 points per inch. EXIF orientation, alpha channels and color profiles require deliberate handling.
JPEG can often be embedded without recompressing its DCT stream; PNG generally requires decoding and embedding pixel data with appropriate compression and transparency. Scaling should preserve aspect ratio and avoid accidental upsampling that increases file size without adding detail.
Memory, malformed files and local privacy
Local merging can keep documents private because inputs need not leave the device. It still needs limits: parsing multiple PDFs, decoding images and serializing the result can hold several copies in memory. Sequential processing and bounded object or stream sizes reduce peak resource use.
PDF is a complex active format. Reject encrypted or malformed input cleanly, cap object and stream sizes, and do not assume a newly merged file is safe merely because parsing succeeded. Viewer JavaScript, attachments and actions may require sanitization in security-sensitive workflows.
Primary specifications and references
- PDF 2.0 specification, ISO 32000-2PDF Association / ISO
- Adobe PDF Reference archiveAdobe
Conclusion
PDF merging rebuilds a document from copied pages and newly embedded images. Page geometry, image decoding, resource preservation and memory limits determine output quality.
My preference is local browser merging for ordinary, non-confidential jobs that fit comfortably in memory, with dedicated server workflows for very large or archival documents. Try the utily.tools PDF & Image Merger and read the splitter and creator articles for complementary operations.