How to combine monthly report pdfs into a single file
- Step 1Lock down a standard section order — Define the monthly pack structure once: executive summary, financials, then each department in a fixed order. Because the merge panel has no drag-to-reorder, this order is simply the order you load files — a consistent naming convention (
01_summary.pdf,02_finance.pdf) makes the monthly run repeatable. - Step 2Collect each team's PDF export — Gather the month's PDFs — print-to-PDF from Excel/Word, or direct exports from Power BI, Tableau, or your accounting system. Any valid PDF works regardless of the tool that produced it.
- Step 3Drop the reports into the merger in section order — Add files to PDF Merge in your standard sequence. Each tile shows name, size, and page count so you can sanity-check before running. Remove and re-add to fix any out-of-order file.
- Step 4Trim oversized BI exports if needed — High-resolution dashboard exports can be large. On free tier (2 MB/file) or just to keep the pack lean, pre-shrink image-heavy reports with PDF Compress (Aggressive) before merging.
- Step 5Run the merge and download the pack — With at least two reports queued, click Process. The engine appends every page in order into one new PDF — all locally. Download the consolidated pack (named from the first file, e.g.
summary.merge.pdf). - Step 6Add page numbers for the distributed version — Run the merged pack through PDF Page Numbers so the board can reference 'page 14' across the whole document, then circulate by email or your portal.
What carries over into the monthly pack — and what doesn't
Based on the actual merge behaviour: pages are copied into a fresh document, so page-level content survives but document-level structure (outline, forms, metadata) does not.
| Aspect | Behaviour on merge | Implication for reporting |
|---|---|---|
| Charts, tables, images | Preserved exactly — copied, not recompressed | BI dashboards and financial charts stay sharp |
| Orientation & page size | Preserved per page — landscape and portrait coexist | Wide dashboards keep their orientation in the pack |
| Bookmarks / outline | Not carried over | No clickable section tree; use page numbers instead |
| Form fields (AcroForm) | Not preserved as a working form | Flatten interactive report templates first |
| Title / author metadata | Not copied — output starts clean | Set the pack's own metadata afterward if needed |
| Selectable text | Preserved for text-based exports | Reviewers can still copy figures from the pack |
Report sources and how they merge
Practical notes for the tools finance and ops teams export from.
| Source tool | Typical export | Merge note |
|---|---|---|
| Excel / Word (print to PDF) | Portrait or landscape, selectable text | Merges cleanly; text stays selectable |
| Power BI / Tableau / Looker | Often landscape, image-heavy | Large files — pre-compress on free tier; orientation kept |
| Accounting system (P&L, balance sheet) | Portrait, text-based | Merges cleanly; numbers remain copyable |
| Slide deck → PDF | Widescreen 16:9 page size | Kept at its own size beside Letter/A4 pages |
| Scanned sign-off sheet | Image-only page | Embedded as-is; not searchable unless OCR'd |
Cookbook
Standard monthly-pack assemblies. Since load order is document order, each example lists the exact sequence to drop files in.
Standard board pack assembly
A repeatable end-of-month order. Use a numeric naming convention so the load order is unambiguous every month.
Load order: 01_Executive_Summary.pdf (2 pages, Letter) 02_Finance_PnL.pdf (4 pages, Letter) 03_Ops_Dashboard.pdf (1 page, A3 landscape — kept) 04_Sales_Review.pdf (6 pages, 16:9 deck export) 05_HR_Headcount.pdf (2 pages, Letter) Merged: board_pack.merge.pdf — 15 pages, sizes preserved.
Pre-compress a heavy BI export before merging
A Power BI dashboard exported at 4.2 MB exceeds the free 2 MB cap and bloats the pack. Compress it first.
Step 1: PDF Compress (Aggressive) on Ops_Dashboard.pdf
target 1 MB → Ops_Dashboard.compress-lossy.pdf (~0.9 MB)
Step 2: Merge:
01_Summary.pdf
Ops_Dashboard.compress-lossy.pdf
03_Finance.pdf
Note: aggressive compression rasterises pages — dashboard text
is no longer selectable. Use it only for image-heavy reports.Number the pack for distribution
The board references pages by number. Add continuous numbering after merging the whole pack.
Step 1: Merge → board_pack.merge.pdf (15 pages)
Step 2: PDF Page Numbers, position bottom-center, start 1
→ 1..15 across the entire pack
Result: a single referenceable document for the meeting.Split last month's pack back into sections
Someone wants just the finance section from a past pack. Reverse the assembly with a range split.
board_pack_april.pdf — Finance is pages 3-6 PDF Split by Range → "1-2, 3-6, 7-15" → three PDFs: summary, finance, the rest Or PDF Extract Pages "3-6" for finance only.
Combine four weekly reports into a monthly roll-up
Each week's status was a separate PDF. Stack them chronologically into one monthly file.
Load order: Week1_status.pdf Week2_status.pdf Week3_status.pdf Week4_status.pdf Merged: monthly_rollup.merge.pdf — weeks in order. (Free tier: this is 4 files — merge in two passes of 2, or upgrade to Pro for one pass.)
Edge cases and what actually happens
Sections came out in the wrong order
By designThere is no drag-to-reorder in the merge panel — files combine in the order added. Remove the misplaced report and re-add it at the right point, or merge and then fix the sequence with PDF Reorder. A numeric file-naming convention prevents this on the recurring monthly run.
A BI export exceeds the 2 MB free limit
Limit reachedImage-heavy Power BI/Tableau exports often top 2 MB. On free tier the file is blocked with an upgrade prompt. Shrink it first with PDF Compress (Aggressive) (optionally to a target size), or upgrade to Pro (50 MB per file).
The pack needs more than 2 reports on free tier
Limit reachedFree merging handles 2 files per batch, once per day. A five-section pack exceeds that. Merge in stages (combine two, then add the next two in another pass), spread across days, or upgrade to Pro for a single unlimited-file merge.
Mixed portrait and landscape pages in one pack
ExpectedA landscape dashboard sitting between portrait financials is normal — each page keeps its own size and orientation, and nothing is rotated or scaled. If you need a uniform orientation/size for printing, normalise with PDF Resize (and PDF Rotate for orientation) after merging.
Source reports had a clickable section outline
Not preservedBookmarks/outlines from individual reports are not merged into the combined pack — the result has no outline panel. Add PDF Page Numbers for reference, or rebuild a section outline in a desktop editor if the board pack format requires one.
An interactive report template (form) was merged
Form not preservedIf a report is a fillable template, its form fields won't function in the merged pack. Flatten it first with PDF Flatten so the entered figures become static content that survives the merge.
A report PDF is password-protected
RejectedA report that requires a password to open can't be read for merging and will fail to load. (Permission-only restrictions are ignored, so a print-locked but openable report merges fine.) Strip the open password first via PDF Remove Password.
Aggressive compression made text unsearchable
ExpectedPDF Compress (Aggressive) rasterises each page to an image, so selectable text is lost — by design, in exchange for size. If reviewers must copy figures, use lossless PDF Compress instead, or compress only the image-heavy reports and leave text reports untouched.
Frequently asked questions
Can I merge PDFs from different tools like Excel, Power BI, and our accounting system?
Yes. Any valid PDF merges regardless of the application that produced it — Excel/Word print-to-PDF, Power BI/Tableau/Looker exports, slide-deck PDFs, and accounting-system reports all combine into one file. Page content is copied exactly, so each report looks identical to its standalone version.
Will charts and dashboards lose quality when merged?
No. The merge copies pages without re-encoding, so charts, sparklines, and high-resolution dashboards stay pixel-exact. Quality only changes if you deliberately run a report through PDF Compress (Aggressive) beforehand to reduce file size.
Do bookmarks from the individual reports carry over?
No. Merging copies pages but not each source's document outline, so the combined pack has no clickable section tree. For navigation, add continuous pagination with PDF Page Numbers; rebuild bookmarks in a desktop PDF editor if your board-pack format specifically needs them.
Can I reorder the reports in the merge panel?
No — there is no drag-to-reorder. Reports merge in the order you add them, so load them in your standard section sequence (a numeric naming convention like 01_, 02_ helps). To fix an order mistake, remove and re-add the file, or rearrange the merged result with PDF Reorder.
Is there a file size limit on the reports?
On free tier, each file must be ≤ 2 MB and ≤ 50 pages, and you can merge 2 files per batch once a day. Pro raises this to 50 MB and 500 pages per file with unlimited files per merge — enough for full board packs with heavy BI exports. Oversized exports can be shrunk first with PDF Compress (Aggressive).
Will a landscape dashboard get squashed to portrait?
No. Each page keeps its own size and orientation, so a landscape A3 dashboard sits unchanged among portrait pages — nothing is scaled or rotated. If you want a uniform layout for printing, normalise the merged file with PDF Resize and PDF Rotate.
Is the selectable text in my reports kept after merging?
Yes, for text-based exports (Excel/Word/accounting PDFs). Because pages are copied rather than rasterised, the underlying text layer is preserved, so reviewers can still select and copy figures. Text becomes non-selectable only if you first ran the report through aggressive (image-based) compression.
How private is this for unpublished financial data?
Fully private. The merge runs entirely in your browser via pdf-lib; no report data is uploaded to any server. Only an anonymous run counter (no content) is saved when you are signed in, and you can opt out. Unpublished revenue and forecast numbers never leave your machine.
How do I make the pack referenceable by page number?
Merge the whole pack first, then run it through PDF Page Numbers so numbering is continuous across all sections. Numbering the combined file (rather than each report) ensures 'page 14' means the same thing to everyone in the meeting.
Can I pull one section back out of last month's pack?
Yes. Use PDF Extract Pages to pull a page range into a new file, or PDF Split by Range to break the pack into sections. Your original files are never modified — every operation produces a new download.
Does the merged pack inherit a report's author or title metadata?
No. The combined file is created fresh with empty metadata rather than copying any single report's title or author. This avoids a misleading 'authored by Finance' on a multi-team pack; set the pack's own metadata afterward in your reader if you want it.
What if a report is a scanned sign-off sheet?
It merges fine — the scanned image page is embedded as-is at its original resolution. It won't be searchable, though, because a scan has no text layer. If you need the sign-off text to be findable, run PDF OCR on that page before or after merging.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.