QuickMergeFeatures & Capabilities
A page-by-page list of what QuickMerge actually does today. Every capability below links to the tool that performs it, its measured limits, or the privacy proof — nothing here is a plan or a promise.
Comprehensive File Processing Suite
QuickMerge covers the common PDF, image, text and data tasks — merging, splitting, compressing, converting, OCR, redaction and more. See the full tool list. Each tool runs on modern browser APIs and established open-source libraries, so the work happens on your device rather than on a server.
Browser-Based Architecture
QuickMerge uses local browser processing for supported operations through libraries such as pdf-lib and pdf.js and standard JavaScript file APIs. Some libraries use Web Workers, while many operations and orchestration steps still use the main thread. You can watch the network panel in your browser's developer tools while running the workflow you intend to use.
Privacy by Design
Every core tool is built to keep your file on your device: for supported operations, the file is read and processed in the browser and is never uploaded. This reduces document exposure by keeping processing local. It can support a privacy program, but it does not by itself make an organization compliant with GDPR, CCPA, or any other law. The measured, per-tool detail is on the limits and browser support pages.
Performance
Local processing avoids the upload and download round trip.
- Some libraries use Web Workers; many operations still use the main thread
- Large or complex jobs can temporarily make the tab unresponsive
- Files are held in memory, not written to a server
- Loaded resources may be cached by your browser; offline availability is not guaranteed
- Measured throughput limits are on the limits page
Privacy
Privacy comes from where the work happens, not from a server you have to trust.
- Supported tools process files on-device, with no upload
- No file is stored on a server — verify in DevTools
- No account is required to use the core tools
- Analytics loads after permission; advertising is disabled. Optional scripts share the page context; see the privacy disclosures.
Reliability
Behaviour is checked before release, and the limits are stated rather than hidden.
- Browser capabilities and historical test coverage are documented on browser support; every device/browser combination has not been verified
- Clear messages when a file or browser is not supported
- Each tool is tested with representative files before release — see how we test
- Each upload control states its application guard. Historical size tests cover a subset of workflows; see measurement coverage.
Choose a workflow by the result you need
A local tool can be useful while still being the wrong fit for a particular file. Check the original and the receiving application's requirements before deciding.
| Task | Use this workflow when | Choose another approach when |
|---|---|---|
| Recover editable text | PDF to Word extracts a usable text layer into paragraphs. | You need original columns, images or tables rebuilt. Edit the authoring source if available. |
| Read a scan | OCR recognizes printed text for you to correct. | Handwriting or critical records need reliable transcription. Compare every important value with the source. |
| Meet a PDF byte limit | Compression can reduce image detail when that is acceptable. | You must retain selectable text, interactive fields or signature validation. Optimize the source or use a workflow that preserves those features. |
| Mark a document | Sign PDF places a visible signature image. | The recipient requires a certificate-backed signature or audit trail. Use its designated signing workflow. |
| Share a sensitive file | Supported operations run locally; inspect the exact workflow and decline analytics if preferred. | Your organization requires approved software, retention controls or a compliance assessment. Local processing alone does not establish those requirements. |
Technical Specifications
Supported File Formats
PDF Operations
Image Processing
System Requirements
Start with an up-to-date browser and a small copy of your file. Requirements depend on the selected engine and the document; there is no verified universal minimum version or RAM threshold.
- Browser: Enable JavaScript. Some operations require WebAssembly, Workers, Canvas or modern file APIs. See capabilities and test coverage.
- RAM: Compressed file bytes do not predict decoded memory use. If a tab stalls, try a smaller batch or extract only the pages you need.
- Storage: Leave room for saved results and keep originals until you reopen and check the downloads.
- Internet: Needed to load the page and each tool's processing engine; the file itself is processed on your device and is not uploaded