File Tools
Process, convert, and transform files directly in your browser. All processing happens client-side — your files never leave your device.
File conversion without the privacy risk of uploading sensitive documents. These tools convert, view, and transform images, PDFs, spreadsheets, and video entirely in your browser.
25 tools availableImage Format Converter
Convert between JPEG, PNG, WebP, BMP, GIF, and HEIC image formats
CSV/Excel Viewer & Editor
View, edit, sort, and filter CSV and Excel files in the browser
Document to PDF Converter
Convert HTML, Markdown, and text documents to PDF
PDF to Word/Excel Converter
Extract text and tables from PDF files into Word or Excel format
Video to GIF Converter
Convert video clips to animated GIFs and GIFs to video
Image Background Remover
Remove backgrounds from images using AI-powered detection
Images to PDF
Combine images into a single PDF file
Add Watermark to PDF
Stamp text or image watermarks onto PDF pages
Compress PDF
Reduce PDF file size in your browser
Merge PDF Files
Combine multiple PDFs into one document
Add Page Numbers to PDF
Add page numbers to PDF pages in your browser
Protect PDF with Password
Encrypt a PDF with a password (128-bit RC4)
Rotate & Flip PDF
Rotate PDF pages and mirror them horizontally or vertically
Split PDF
Split a PDF into pages, ranges, or fixed-size parts
PDF to JPG/PNG
Convert PDF pages to JPG or PNG images
Unlock PDF
Remove the password from a PDF file
Invoice & POS Bill Generator (PDF)
Create GST invoices & POS cash bills as PDFs
Crop & Resize PDF
Crop margins or resize PDF to a paper size
Extract Text & Images from PDF
Extract text to .txt or pull images out of a PDF
Flatten PDF
Flatten PDF forms & remove annotations
PDF Hash & Fingerprint Generator
Hash any PDF (MD5 & SHA) plus a content fingerprint
Invert PDF Colors / Dark Mode
Invert PDF colors or make a dark-mode copy in-browser
Edit PDF Metadata
Edit or strip PDF document metadata (Title, Author, keywords)
PDF Privacy & Metadata Risk Scanner
Scan a PDF for sensitive data & metadata exposure, on-device
PDF to Markdown / HTML / Text
Convert PDF text to Markdown, HTML, or plain text
A file format is a contract, and every converter here is checking it
Everything here runs in the tab: the File API defines a Blob as "immutable raw binary data", so the bytes a converter reads are the bytes the browser was handed. What still goes wrong is format-level, and each failure has a published rule behind it.
A PDF describes pages, and PDF/A is the constrained subset built for archives
The Library of Congress states the archival form plainly: "PDF/A-1 is a constrained form of Adobe PDF version 1.4 intended to be suitable for long-term preservation of page-oriented documents for which PDF is already being used in practice." The constraint explains why an archiving pass refuses encryption and external dependencies. If the output must be readable in ten years, convert toward PDF/A; if it must stay editable, keep the plain PDF.
An image announces its type in the first eight bytes
The PNG specification puts it flatly: "The first eight bytes of a PNG datastream always contain the following hexadecimal values: 89 50 4E 47 0D 0A 1A 0A", and this "signature differentiates a PNG datastream from other types of data". A JPEG renamed to .png fails at the signature, not the extension. Integrity works the same way: each chunk carries the "CRC (Cyclic Redundancy Check) employed in PNG chunks", so a truncated transfer is caught, not rendered.
A CSV file is text with quoting rules, not a table
RFC 4180 keeps it short: "Fields containing line breaks (CRLF), double quotes, and commas should be enclosed in double-quotes." The second rule is the one that breaks a join: "Spaces are considered part of a field and should not be ignored." A header written as "name ,email" has a column called "name ", and a value containing a line break splits a line-based reader into two records.
An upload is multipart, and each part declares its field name
An uploaded file is one part of a multipart body. RFC 7578 requires that "Each part MUST contain a Content-Disposition header field" whose disposition type is "form-data". A rejected upload is usually a rejected part name or declared type, not bad bytes - which is why a size check that passes in the browser can still fail at the edge.
| Task | Tool here | The rule that applies | Source |
|---|---|---|---|
| Combine pages into one document | Images to PDF | PDF/A-1 is a constrained form of PDF 1.4, built for long-term preservation | Library of Congress |
| Convert an image format | Image Format Converter | an eight-byte signature identifies a PNG; chunk CRCs detect corruption | W3C PNG 3 |
| Inspect or edit a CSV | CSV/Excel Viewer | fields with line breaks, quotes or commas must be quoted; spaces count | RFC 4180 |
| Diagnose an upload rejection | any upload | every part carries a Content-Disposition header named form-data | RFC 7578 |
| Keep the file on the device | every tool in this hub | a Blob is immutable raw binary data, read in the browser | W3C File API |
Start with the Image Format Converter, combine pages in Images to PDF, shrink the result in Compress PDF, remove annotations in Flatten PDF, and clear identifying fields in Edit PDF Metadata. The CSV/Excel Viewer follows the RFC 4180 rules above.
Sources: Library of Congress, PDF/A-1 format description; W3C PNG (Third Edition); RFC 4180, CSV Files; RFC 7578, multipart/form-data; W3C File API.