Choose a task—convert, OCR, merge, compress, check, clean, protect or sign—and run it in your browser. Selected document content is processed on your device, but the browser, device, loaded code and downstream recipient still belong to the security boundary.
Working blobs stay in tab memory and are not persisted in IndexedDB, Cache Storage, or BytesPDF server storage.
The site still downloads HTML, JavaScript, worker, and codec assets. Supabase can handle account, subscriber, and consent-audit data; Formspree can receive contact submissions; consented analytics and configured error reporting are separate from PDF content.
Read the complete data inventory →One selected PDF at a time.
The file is checked against the 150 MB desktop or 50 MB mobile input limit and read in the current tab.
The preset controls supported image re-encoding. Scans and photographs can change; born-digital vector text is not rasterized.
Your browser tab inspects and rewrites supported content using this device's CPU and memory. Processing time varies by file and device.
The result is a separate file. If the generated version is not smaller, BytesPDF returns the source instead.
Whole-file ordering and rotation controls.
Desktop supports up to 20 files and 150 MB combined; mobile supports up to 10 files and 50 MB combined.
Arrange whole source files and apply the available source rotation controls.
The merge step copies visible pages into a new document in the selected order.
Check page order, orientation, links, forms, bookmarks, annotations, attachments, and other structures you need.
A reliable PDF workflow starts with the source, uses only the changes the recipient needs, then checks the exact copy before it is sent. These linked tools cover common steps without asking you to upload the selected document to BytesPDF.
Convert supported Word or Excel files to PDF. For a text-based PDF, the PDF-to-Word beta can recover editable paragraphs, but it does not preserve the source layout or pictures.
Finish edits first, then merge or compress a separate copy. Check page order, content, metadata and the recipient’s size rules before sending.
BytesPDF is a set of user-run browser tools, not PDF workflow automation software. It does not currently offer a public conversion API, scheduled jobs, no-code triggers, or Salesforce/n8n connectors. Each task is started by you; review every output before relying on it.
Compression and merge reject files with a detected signature ByteRange rather than claiming a cryptographic signature will survive a rewrite.
Password-protected inputs are rejected. Unlocking must happen through an authorized workflow elsewhere.
BytesPDF does not certify PDF/A conformance. Keep the archival master and use an appropriate external validator.
A separate browser-local OCR tool can add a searchable English text layer to supported scans. Recognition may contain errors; review the result. Compression itself does not run OCR.
Compression clears common descriptive and XMP fields. It is not a forensic sanitizer for every attachment, annotation, image value, or application-specific object.
The published cap is an input rule, not a promise that every file below it will fit a particular device's available memory.
A valid-looking PDF is not proof that every bookmark, form, annotation, attachment, tag, color profile, or recipient-specific requirement survived. Save the output as a separate copy and test the features your workflow uses.
Open the output-review checklist →No account, signup or email is required at any point: process the file and download the result in the same session. Processing time and results depend on the PDFs and device.
