RookPDF documentation

RookPDF is a web application that runs entirely in your browser. There is nothing to install or download before using the tools. Open rookpdf.site in a supported browser, choose a tool from the tools page or the homepage, and upload a file to begin.

Each tool has its own workspace with a file upload zone. Select a PDF or image from your device and the tool will process it locally. When processing finishes, a download button appears so you can save the result directly to your device.

You can use RookPDF without creating an account. Guest Mode gives full access to every PDF tool. Signing in is optional and is used only for saving preferences such as your theme choice and download name settings. No account is required to merge, split, compress or convert files.

Keyboard shortcuts are available throughout the application. Press Ctrl or Cmd plus K to open the global search bar, which lets you find tools and pages quickly. Press Ctrl plus U to trigger a file upload in the active workspace when supported.

RookPDF is built around local browser processing. When you open a file in any tool, the file is read from your device by the browser using the standard File API. The PDF is parsed and modified using client-side JavaScript libraries including pdf-lib and pdf.js. The finished result is offered as a download. The file never leaves your browser.

RookPDF does not upload, transmit, cache or store the content of any document you process. File names, page content and image data stay on your device. There is no server-side PDF processing pipeline and no cloud storage for user documents.

Account data is limited to authentication credentials and user preferences such as theme and language settings. This data is stored separately from any document content and is never combined with or linked to the files you process in the tools.

Analytics and advertising use anonymized usage data and are loaded only after you consent via the on-site consent banner. You can decline analytics and advertising at any time through the consent settings. See the privacy policy for full details.

RookPDF works in current versions of Chrome, Edge, Safari and Firefox on desktop and mobile. The tools rely on modern browser APIs including File, Blob, ArrayBuffer, canvas rendering and local downloads. Keeping your browser up to date ensures the best compatibility.

For PDF to Word and OCR tools, RookPDF uses client-side text extraction and the Tesseract.js OCR engine. These features work best in Chrome and Edge due to their V8 JavaScript engine performance. Safari and Firefox are supported but may be slower on very large documents.

Mobile browsers are supported for most tools. The interface adapts to smaller screens with a responsive layout and touch-friendly controls. Some advanced features such as high-DPI PDF rendering may be limited by available device memory on phones.

RookPDF can function as a Progressive Web App. Once the application has loaded, it caches core assets so that previously visited pages load quickly. Full offline operation depends on which tools you use and whether the browser has cached the required processing libraries.

If a PDF fails to open, the file may be password-protected, corrupted or in an unsupported format. Password-protected PDFs can be unlocked first using the Unlock PDF tool, which removes encryption locally before you pass the file to other tools.

Very large PDF files may cause slow processing or browser warnings due to memory limits. RookPDF warns you when a file exceeds 150 MB. For the best experience with large documents, use a desktop browser with sufficient available memory and close other tabs to free resources.

If a conversion tool produces unexpected output, check that you selected the correct output format and settings. For example, PDF to Word works best with text-based PDFs rather than scanned images. For scanned documents, use the OCR Assisted mode in the PDF to Word tool to extract text from images.

If downloads do not trigger, verify that your browser allows downloads from rookpdf.site and that no browser extension is blocking the download. Some privacy extensions intercept download requests. Temporarily disabling such extensions can help identify the cause.