Related pages
File handling
How Convurter handles files.
Browser-local when possible. Temporary jobs when needed. Metadata stays bounded.
RuntimeBrowser-local tools
Image, PDF page operation, ZIP, checksum, file inspection, document review, PDF inspectors, image inspectors, and text/data tools use browser APIs and local JavaScript runners when marked as no-upload tools.
RuntimeTemporary server jobs
PDF, Office, OCR, HEIC, and HTML-to-PDF workflows can use temporary upload-backed jobs with size limits, expiry, delete controls, and quality notes.
RuntimePublic lookups
DNS, SSL, redirects, and HTTP headers use public records or public responses. These checks are not private-network scans or security certifications.
Browser-local toolsMost current public tools process selected files directly in your browser. For those tools, Convurter does not upload your files to a server to complete the task.
Most current public tools process selected files directly in your browser. For those tools, Convurter does not upload your files to a server to complete the task.
Readiness tools such as PDF-to-Word readiness, OCR readiness, scanned PDF detection, PDF text-layer checks, HEIC support checks, Office conversion checklists, and HTML-to-PDF render readiness are also browser-local. They inspect signals and explain risks; they do not convert, OCR, redact, or upload the file.
Temporary PDF jobsPDF rendering, PDF text extraction, embedded image extraction, and PDF compression use temporary upload-backed jobs.
PDF rendering, PDF text extraction, embedded image extraction, and PDF compression use temporary upload-backed jobs.
Convurter creates a short-lived upload URL, queues the job, stores temporary input and output artifacts, and returns an expiring download link. The workbench can expose a delete action that removes the temporary input and output object prefixes and marks the job expired or deleted.
Temporary Office jobsDOCX to PDF, PDF to Word, XLSX to PDF, and PPTX to PDF use the same temporary server job contract as PDF jobs. Conversion runs in the worker path and returns one expiring download. Outputs must be reviewed for sheets, charts, slides, fonts, page breaks, and layout shifts.
DOCX to PDF, PDF to Word, XLSX to PDF, and PPTX to PDF use the same temporary server job contract as PDF jobs. Conversion runs in the worker path and returns one expiring download. Outputs must be reviewed for sheets, charts, slides, fonts, page breaks, and layout shifts.
Temporary OCR jobsImage to Text and PDF OCR use temporary upload-backed OCR jobs. Image OCR accepts JPG, PNG, and WebP inputs and returns plain text. PDF OCR accepts unlocked PDFs, renders pages for recognition, and returns plain text with page separators.
Image to Text and PDF OCR use temporary upload-backed OCR jobs. Image OCR accepts JPG, PNG, and WebP inputs and returns plain text. PDF OCR accepts unlocked PDFs, renders pages for recognition, and returns plain text with page separators.
Temporary image and HTML jobsHEIC to JPG, HEIC to PNG, and HTML to PDF use temporary upload-backed jobs. HTML to PDF accepts uploaded or pasted HTML only; arbitrary URL capture, private-network fetching, scripts, frames, plugin objects, and external network resources are blocked.
HEIC to JPG, HEIC to PNG, and HTML to PDF use temporary upload-backed jobs. HTML to PDF accepts uploaded or pasted HTML only; arbitrary URL capture, private-network fetching, scripts, frames, plugin objects, and external network resources are blocked.
Tools that need extra reviewSome workflows need stronger processors and output review before Convurter offers them as production tools. For those cases, Convurter may provide readiness checks and guides until the actual conversion path is reliable.
Some workflows need stronger processors and output review before Convurter offers them as production tools. For those cases, Convurter may provide readiness checks and guides until the actual conversion path is reliable.
LimitsFile limits are intentional. They keep the page responsive, protect your browser from oversized work, and keep free tools inexpensive to operate.
File limits are intentional. They keep the page responsive, protect your browser from oversized work, and keep free tools inexpensive to operate.
AnalyticsTool analytics use safe metadata such as tool id, family, runner, file count, size bucket, format, success, failure, copy, and download events. Raw file contents, pasted text, filenames, URLs, passwords, tokens, and generated outputs are not logged.
Tool analytics use safe metadata such as tool id, family, runner, file count, size bucket, format, success, failure, copy, and download events. Raw file contents, pasted text, filenames, URLs, passwords, tokens, and generated outputs are not logged.
DownloadsFinished browser-local files are created in your browser and downloaded by your browser. Temporary server job outputs are stored only as expiring artifacts for the download window.
Finished browser-local files are created in your browser and downloaded by your browser. Temporary server job outputs are stored only as expiring artifacts for the download window.
Sensitive filesAvoid using free web tools for secrets, regulated records, legal documents, medical records, financial files, or private credentials unless you understand the risk.
Avoid using free web tools for secrets, regulated records, legal documents, medical records, financial files, or private credentials unless you understand the risk.