Document Tools

Document tools handle the conversion and inspection jobs that happen before a file is opened in Acrobat, Word, or Excel. Right now the category is small but focused: one live tool that decodes a Base64 string into a real PDF you can preview and save, plus a roadmap of converters and editors landing over the coming weeks. For PDFs generated from an API payload, an email attachment pasted into a note, or a developer console dump, this is the first stop.
What you can do with document tools

Decode a Base64 string into a proper PDF file, preview it in the browser, and download the real binary: Base64 to PDF.
Save yourself an Acrobat Pro subscription or a sketchy online converter when all you have is text-encoded document data from a JSON API response or a signed webhook payload.

Reach for document tools when the input is a text-encoded document (Base64, data URI, hex bytes) and the output should be a real file readable by Acrobat, Word, or Excel. If the conversion is between image formats instead, the image category covers PNG, JPG, and WebP. If the goal is inspecting structured text like JSON or XML, the JSON tools are closer.
The Document toolkit

Tool
What it does
When to use

Base64 to PDF
Decodes a Base64 string into a PDF file, renders it in an embedded preview, offers download. Validates the header so a non-PDF blob fails loudly rather than silently saving garbage.
Reading a PDF that an API returned as a JSON string, inspecting an email attachment pasted from a DevTools network tab, or verifying a signed document payload before passing it further.

Coming to the Document toolkit
The category is actively expanding. These are the converters and editors planned for upcoming releases, grouped by job. They will appear at /tools/{slug}/ as each one ships.

PDF core operations: merge PDFs, split a PDF into pages, extract specific pages, rotate, reorder, delete pages, compress.
PDF conversion: PDF to Word, PDF to Excel, PDF to PowerPoint, PDF to JPG or PNG, images to PDF, HTML to PDF.
PDF editing: add page numbers, add watermark, fill form fields, remove passwords from protected PDFs, remove metadata.
Office formats: DOCX to PDF, XLSX to CSV, PPTX to PDF, EPUB to PDF, RTF conversion.
Inspection: extract text from scans via OCR, inspect PDF metadata, check accessibility tags.

Each one will follow the same pattern as Base64 to PDF: client-side, no upload, instant result.
How to choose the right document tool

If you have a Base64 string that claims to be a PDF, start with Base64 to PDF. The tool validates the PDF signature before saving, so you will know immediately if the blob is corrupted or mislabeled.
If your Base64 payload is actually JSON, XML, or text, use the matching decoder in the JSON tools or a general Base64 decoder in the developer category.
If the file came in as a data URI (data:application/pdf;base64,...), strip the prefix before pasting into the tool. The encoder accepts raw Base64 only.

Frequently asked questions
Q: Why decode Base64 to PDF in the browser instead of a native tool?
Most APIs return PDFs as Base64 inside JSON responses. Saving the JSON to disk, writing a Python script to decode and save the PDF, and opening it in a viewer takes three minutes. A browser tool does it in one click with no install.
Q: Is the PDF uploaded anywhere?
No. Base64 to PDF runs fully client-side. The browser decodes the string into a Blob and creates a local download link. Nothing crosses the network. The browser network tab confirms zero requests.
Q: What happens if my Base64 is not actually a PDF?
The tool inspects the first bytes of the decoded output. A real PDF starts with %PDF-. If those bytes are missing, the tool shows a clear error instead of saving a broken file that would fail on open.
Q: When will the rest of the PDF toolkit launch?
Tools are shipping on a rolling basis. The fastest way to know when a specific one is live is to check the category page here, where every new tool appears automatically once published.
Related categories
Document work often starts or ends in an adjacent toolkit. If the source is a developer payload with tokens, hashes, or cryptographic signatures, the developer category holds the encoders and decoders. For JSON-wrapped document payloads or API responses, the JSON tools help inspect and clean the envelope before extracting the document. When the output you want is actually an image (a cover page, a diagram, a screenshot), the image category is the right place.