Tools
Fileraz
Try jpg to png, compress image, pdf…
PDF tools
Think about what people actually merge and split. Signed contracts and their appendices. Bank statements for a mortgage application. Payslips, medical letters, tax returns, scans of a passport. PDF operations cluster around exactly the documents you would least like to leave on someone else's server, which is why the processing location is not an abstract concern here.
Splitting is the clearest case. The usual reason to split a document is that someone asked for one page and the other pages contain things they have no business seeing. Uploading the whole file to extract that page defeats the purpose of extracting it. Doing it locally does not.
One caution regardless of where processing happens: removing a page is not redaction. Text hidden behind a black box drawn in another application is still text in the file, and metadata can travel with the pages you keep. If something genuinely must be unreadable, use a proper PDF editor's redaction feature and check the output before sending it.
Browser-side processing is not strictly better, and the last row is the honest cost of it. Here is the trade in full.
| Typical server-based tool | Fileraz | |
|---|---|---|
| Where your PDFs are processed | Uploaded to the operator's servers | In your browser tab, on your own device |
| What the operator can see | The file contents, while processing and in any retention window | Nothing — the file is never transmitted |
| Usage limits | Commonly a daily cap or a size cap, with a paid tier above it | No cap, because your conversions cost us nothing to run |
| Account required | Often, for anything beyond the basics | Never — there is no public sign-up at all |
| Speed | Upload time, queue time, then download time | Starts immediately; bounded by your own hardware |
| Large or complex files | Handled well — server hardware does the heavy lifting | Bounded by your device memory, and may fail where a server would not |
Worth knowing before you start, rather than after.
Merge PDF and Image to PDF accept up to 20 files; every other tool takes one PDF at a time.
Image to PDF: JPG and PNG only; original size or fit to A4/Letter; rotation in Original size mode.
PDF to Image: PNG or JPG at 1×–3× scale; optional page range; PDF.js bundled with the page.
Split: every page as a ZIP, or a range into one PDF; extract, delete, and reorder use 1-based ranges (e.g. 1-3, 5); delete refuses to empty a document.
Rotate: 90° steps on the whole file or a range; page boxes turn, text stays selectable.
Watermark and page numbers: flattened drawings on every page — diagonal Helvetica mark, centered 1 / N footer; an existing footer shows both sets.
Metadata editor: title, author, subject, keywords, producer, creator, and both dates — info dictionary only, not XMP.
Compress: Safe structural cleanup, or Lossy JPEG flatten (text becomes non-selectable).
Protect PDF: AES-256 password in this tab — no recovery if you forget it. Unlock PDF removes a known password so other tools can open the file.
Encrypted PDFs must be unlocked elsewhere before any tool on this page can open them.
The merge runs in your browser using pdf-lib, so the documents are never transmitted. Verify it for yourself: open your browser's developer tools, select the Network tab, and run a merge — you will see no request carrying your file.
JPG and PNG. Other formats, including WebP, HEIC from an iPhone, and TIFF, need converting to JPG or PNG first. You can do that with the image converters on this site.
No cost, no account, no watermark, and no daily cap. Merge PDF and Image to PDF accept up to 20 files each; the other tools take one file at a time. File size is bounded by your device memory rather than by a rule we set.
Because it strips structural bloat and unused objects but does not recompress images, which is what makes most large PDFs large. A scanned document will see little benefit. The tool page explains what to do instead.
Not yet. Real PDF encryption needs cryptography support our browser-side library does not provide, so that tool reports itself unavailable rather than producing a file that only looks protected. Use Preview on macOS, Adobe Acrobat, or qpdf --encrypt.
An encrypted PDF cannot be read without its password. Remove the protection first with a tool that has it, then bring the unlocked copy back here.