Local-first PDF tools
Most file tools run in the browser, so common PDF work does not require uploading a document to start.
Merge, compress, convert, sign, secure, OCR, and organize PDFs. Most website tools process files locally in your browser; server-side tools and API workflows are clearly labeled.
Popular tasks
Start with the highest-intent PDF jobs people use every day, with routes backed by the existing tool catalog.
Combine multiple PDF files into one document. Free online PDF merger with drag-and-drop reordering.
Reduce PDF file size while maintaining quality. Free online PDF compressor for smaller files.
Convert PDF to editable Word (DOCX) documents. Preserve formatting and layout.
Convert Word documents (DOCX) to PDF. Preserve formatting and layout in your converted documents.
Convert JPG images to PDF. Combine multiple JPG files into a single PDF document.
Convert PDF pages to JPG images. High-quality extraction with customizable resolution.
Make scanned PDFs searchable with OCR. Extract text from images and scanned documents.
Password protect PDF files. Add encryption and set permissions.
Why choose iTextMaster
A local-first website experience and a Credits-based API can live in the same product without confusing users.
Most file tools run in the browser, so common PDF work does not require uploading a document to start.
Tools that require rendering, URL fetching, or API processing state that path before you submit data.
Use API Credits for backend jobs, batch flows, and product integrations while keeping manual website tools free to try.
Task paths
Choose the intent first, then jump into the exact tool, guide, or API page.
Merge, alternate, grid-combine, or package PDF files.
Compress and clean PDFs before sending or archiving.
Extract text, tables, or Word-ready content from PDFs.
Encrypt, redact, flatten, or remove metadata before sharing.
Use API endpoints for backend and workflow automation.
Developer API
Turn common PDF work into backend jobs with simple pricing, clear examples, and related website tools for manual testing.
Pricing
Combine multiple PDFs into one ordered document from your backend, batch job, or product workflow without building PDF merge infrastructure.
Open API pageExtract page ranges or divide large PDFs automatically so your app can produce focused packets, attachments, or archives.
Open API pageRender trusted HTML into PDFs from your backend for reports, receipts, statements, and generated documents.
Open API pageCapture public webpages as PDF from backend jobs, monitoring systems, or customer-facing export flows.
Open API pageTurn invoice JSON into polished PDF invoices from your billing system, admin panel, or automation workflow.
Open API pageApply deterministic redaction areas from review decisions, coordinates, or compliance workflows.
Open API pagePrepare OCR automation for scanned PDFs and connect it with cleanup, crop, and export workflows.
Open API pageGuides
Use guides for planning and document handling decisions before opening a tool or wiring the API.
A practical guide to merging PDFs locally in the browser, preserving order, reviewing the output, and deciding when API automation is appropriate. contracts, invoice packets, school forms, and internal reports that should stay close to your device.
A guide to reducing PDF file size while preserving text readability, scan clarity, images, and sharing requirements. large PDFs that must fit email, portal, or chat attachment limits.
A guide to preparing scanned PDFs with OCR before exporting editable Word documents, with checks for text recognition and layout quality. scanner or phone-camera PDFs that need editable Word text.
A guide to checking and removing PDF metadata before sharing documents outside your team or organization. PDFs that leave your team, client folder, or internal workspace.
Trust & privacy
Privacy claims stay specific: local tools, clear server disclosures, and separate billing for API automation.
Browser-based tools handle common PDF work on your device.
Rendering and URL-fetching tools explain the processing path before submission.
API Credits are for automation calls, not normal website tool usage.
The website avoids ad tracking cookies for the PDF tool experience.
Core browser workflows use proven open-source PDF libraries and WebAssembly where appropriate.
Localized entry points help users find the right tool in their own language.
FAQ
Have more questions? Visit our full FAQ page
For most file tools, no. They process files locally in your browser. Server-side website tools and PDF API requests disclose their processing path before you submit data or integrate the API.
Browser-local PDF tools are free to use on the website. Some server-side website tools may apply fair-use or abuse-prevention limits, and API calls for automation are billed with Credits.
No. API Credits are used for automation calls made with an API key. Normal website tool usage does not consume API Credits.
Tools that need URL fetching, browser rendering, or backend automation, such as Webpage to PDF, HTML to PDF, and PDF API endpoints, use server-side processing and disclose that before submission.
Use browser-local tools when you need files to stay on your device. For any tool that says it uses server-side processing, review the disclosure and your own confidentiality requirements before submitting data.