Tool guide
About PDF
Browser-side PDF utilities for merge, split, and re-save workflows when pdf-lib and canvas can handle your file.
Many teams need a one-off PDF merge before email but cannot install Acrobat on a locked laptop. This tool loads pdf-lib client-side: you select files, reorder if needed, and download a combined PDF. Splitting produces one PDF per page zipped for print shops. Compression here means rewriting streams—results vary by how the source PDF was produced.Treat this page as temporary scaffolding, not a document-management system. Encrypted PDFs, damaged cross-reference tables, complex forms, and some embedded fonts can exceed what a browser library can do. Large merges eat memory: Mobile Safari is likelier to kill the tab; desktop Chrome or Edge is safer. After processing, open the output in a desktop reader and check page order, rotation, and fonts. PracticalKit does not store merge files on its origin—the work runs in your tab.
Common use cases
- Combine scanned receipts into one attachment under a portal’s upload cap.
- Split a 200-page export into single pages for a binder naming scheme.
- Re-save a bloated export from a design tool to see if object streams shrink.
- Merge cover, body, and appendix PDFs in the right order for colleagues without a desktop suite.
- Finish a merge offline from a cached copy of this page on weak hotel Wi‑Fi without sending contracts to a random online service.
Merge
Choose PDF files
Split into one PDF per page
Split & download zip
Re-save (may shrink some files)
Pages to PNG (zip)
PDF tools
Merge
Merge & download
Split into one PDF per page
Re-save (may shrink some files)
Pages to PNG (zip)
Extract text to .docx
How to use PDF
- 1
Choose the operation
Merge expects multiple PDFs; split works on one input; compress/re-save targets a single file. Read the on-page note for password-protected inputs—they are not supported. Decrypt with an authorized tool first. Do not force the wrong mode hoping it works.
- 2
Select files locally
Use the file picker; bytes stay on your device. Wait for the progress indicator on large merges—100+ pages can take tens of seconds. If memory is tight, merge in batches and do one final merge.
- 3
Download and spot-check
Open the output in your desktop reader: verify page order, rotation of landscape scans, and fonts before sending externally. Confirm filename and page count once more.
- 4
If something fails
Keep originals; browser PDF stacks do not repair corrupted xref tables. This is not a redaction tool—hidden layers may still exist in the object stream.
Tips and limits
- Keep originals; browser PDF tooling does not repair corrupted cross-reference tables.
- Mobile Safari may abort merges above available RAM—use desktop Chrome or Edge for big jobs.
- This is not a redaction tool; hidden layers may still exist in output.
- Heavy scans sometimes shrink better if you compress page images first, then rebuild the PDF.
- Confirm page order in the UI before download—fixing later costs more.
Frequently asked questions
- Does merge upload my PDFs?
- Processing uses pdf-lib in your browser. PracticalKit does not store files for the merge operation itself.
- Why did compression barely change size?
- Already-optimized PDFs or image-only pages may not shrink. Try exporting images separately if you need aggressive size reduction.
- Can I merge encrypted PDFs?
- Not in the current build. Decrypt with an authorized tool first.
- Why does the split zip contain many tiny PDFs?
- Per-page output suits print shops and archival naming. Multi-page ranges in one file are better done with desktop software.
About this tool page
Files, PDFs, and media in the browser
“PDF” reads files you select in the browser. Where the implementation allows, bytes are processed with Web APIs or WASM on your device without PracticalKit storing the file on our servers for the conversion itself. You trigger result downloads; we do not keep training copies or a server-side queue for this tool’s conversions.
PDF, image, audio, and video workflows can be memory-heavy. Success depends on file size, resolution, encoding, and device RAM. If the browser aborts or freezes, try a smaller asset, a simpler format, or desktop software for very large productions. Encrypted PDFs, complex forms, and hundreds-of-megabyte scanned books are known edge cases that belong on streaming desktop tools.
Policies and editorial pages