FAQ
Frequently Asked Questions
Everything about privacy, formats, modes, and permissions.
Is my page content uploaded to a server?
No. Web to File processes everything locally in your browser: content extraction, cleanup, and file generation. It has no backend servers, no analytics, and no tracking SDKs. No webpage content, exported files, or browsing data ever leaves your device.
Which file formats can I export?
PDF and Markdown for documents, plus full-length screenshots in PNG, JPEG, or WebP. Your image format choice is remembered for the next export, and more formats are planned.
What is the difference between Full Page, Article, and Custom mode?
Full Page mode captures the page as it is rendered, top to bottom. Article mode extracts the main readable content and removes ads, navigation, and sidebars, which suits news and blog posts. Custom mode lets you pick specific content blocks and reorder and refine them before exporting.
Is Web to File free?
Yes — free to install and use, with no account, no subscription, and no in-app purchases.
Why does the extension need the debugger permission?
Chrome’s built-in rendering pipeline (used for high-quality PDF generation and rendered-page capture) is only accessible through the Debugger API. Web to File attaches it only while an export you started is running, and detaches it right after.
Why does it request access to all websites?
So it can run on whatever page you choose to export. Content scripts are injected on demand when you start an export — not automatically on every page you visit.
Does it work on every page?
It works on any normal web page you can open, including pages behind your own logins. Chrome blocks all extensions on browser-internal pages (chrome://, the Chrome Web Store) — Web to File shows a notice on those.
Where are my exported files saved?
Files are saved to your Downloads folder via Chrome’s standard download mechanism. Exports are also kept in a local history inside the extension, where you can view or re-download them.
How do I delete the data the extension stores?
Clear the export history from the extension’s settings, or uninstall the extension — all locally stored preferences, history, and files are removed with it.
An export failed or looks wrong. What can I do?
Try reloading the page and exporting again — some sites finish loading content late. If a specific site consistently extracts poorly, contact support with the page URL; site-specific extraction is actively improved in each release.
Still have questions?
Reach out through the support page — we read every message.