Help center
Clear answers about privacy, local processing, supported tools, file limits, browser compatibility, and what to do when a PDF fails.
Updated for the current browser-based PDF toolset.
Find answers by topic.
For core tools such as merge, split, compress, rotate, protect, unlock, watermark, page numbers, and PDF to image, files are processed in your browser. They are not uploaded to our server for those operations.
It means the file is read by the page in your browser tab, processed by JavaScript or WebAssembly, and the result is generated on your device.
Yes. Open the browser Network panel, run a tool, and watch requests. You should only see page, script, font, model, or WASM assets loading, not your PDF content being sent as an upload.
No. Passwords entered for local PDF protection or unlocking are used in the browser execution flow and are not stored by PDFRover.
The site includes PDF merge, split, compress, edit, sign, convert DOCX to PDF, image to PDF, PDF to image, extract images, protect, unlock, rotate, remove pages, extract pages, reorder pages, watermark, page numbers, header/footer, overlay, compare, booklet, crop, metadata tools, redaction, and create PDF.
Yes. Add multiple files, then adjust the file order before running the merge tool. The output follows the order shown in the list.
Most browser-based PDF work depends on your device memory and browser limits. If a very large file fails, try closing other tabs, using a desktop browser, splitting the file first, or reducing image-heavy pages.
Many tools work on modern mobile browsers, but large files and multi-file workflows are more reliable on desktop browsers because they have more memory and easier file management.
Not always. Simple documents usually convert well. Complex tables, rare fonts, floating objects, and advanced Word layout features may need review after conversion.
Rendering depends on PDF fonts, transparency, images, and browser canvas behavior. PDFRover uses PDFium/PDF.js based rendering paths to keep results close to standard viewers.
OCR is intentionally hidden for now. Scanned image-only PDFs can be viewed or converted to images, but searchable text extraction is not exposed as a public tool yet.
First check that the file is actually a PDF or the expected format. If it came from an e-signature or bidding system, try opening it in a standard PDF viewer and exporting a normal PDF copy.
Open the downloaded file in another PDF viewer such as Chrome, Edge, Preview, or Acrobat. If the downloaded file is correct but the inline preview is not, it is likely a preview renderer issue.
The browser may need to load the WebAssembly engines and PDF rendering assets. After the first load, subsequent operations are usually faster while the tab remains open.