Information about TIFF to PNG

What it converts

• Both directions, from one window: TIFF to PNG, and PNG to TIFF. A switch chooses which way the next run goes, and a file that is not of the type the current direction expects is skipped with a count and a reason rather than converted anyway.
• The alpha channel survives. An image that was transparent in the TIFF is transparent in the PNG, which is the conversion's whole answer for digital artists and web editors.
• Every page becomes its own PNG, rather than only the first page being converted.

What a run looks like

• Files are dropped onto the extension's window or chosen with a file picker, and several can go in at once. Each finished file waits on its own card with its own Download button; ticking several of them collects them into a single ZIP download.
• A selection larger than one ZIP can carry is the one case that is refused: the extension says the batch is too big for a single archive and points at the one-at-a-time route, rather than failing quietly at the end of the work.
• A compression-level control decides how much work the encoder does. The position you last chose is remembered for the next run.

What happens to your files

• Decoding and encoding run in Web Workers and WebAssembly modules bundled inside the extension. The file's bytes are read from the file you selected and are not copied anywhere else.
• A converted image is held in the browser's memory until you download it, or take the batch as a ZIP. Nothing survives closing the extension's page or the tab it runs in.
• To save a file, the extension creates a temporary in-browser object URL and clicks a link pointing at it. It does not request the downloads permission, so it cannot read your download history, cannot tell whether a download finished, and cannot choose where the file goes — Chrome saves it wherever you have told Chrome to save downloads.
• The files never leave your computer. That is the claim the whole product rests on, and Section 3 of the privacy policy is its long form.

What it does not do

• It makes no network requests, and cannot. A Content Security Policy sets connect-src 'none' and form-action 'none' on the extension's own pages, so they are incapable of contacting a server by fetch, WebSocket, image beacon or submitted form, even if a later bug or a tampered build tried. That is why the extension works fully offline: disconnect the internet and every feature still works.
• It requests no browser permissions at all — not your browsing history, not the content of the pages you visit, not your clipboard, not your downloads, not your bookmarks, not your file system — and it injects no scripts into any website you visit. Clicking its toolbar icon opens its own page in a new tab, which requires no permission, and that is why it can ship with an empty permission list.
• It collects nothing: no account, no sign-up, no personal data, no analytics, no telemetry, no crash reports, no advertising identifiers — and no history of what you converted, because it keeps no log anyone could retrieve.
• It stores two settings on your device, in the extension page's own local storage: the theme, and the compression level. No cookies, no chrome.storage, no IndexedDB, no cache of your files. Clearing your browser data or removing the extension deletes both.

The website itself

The Site at https://tiff.tools converts nothing. It describes the extension and carries its privacy policy, and the extension's page is a separate browser origin with no network access that shares no storage with it. The website sets no cookies and runs no analytics; like the extension, it keeps one setting in your browser's local storage, which is the theme you chose.

Its hosting provider, Cloudflare, records standard access logs when a page loads: IP address, date and time, page requested, referring page and browser user-agent. Section 7.1 of the privacy policy is where that is set out in full, including how long the logs are kept.

Where to read more

• The landing page shows what the extension does, how a conversion looks, and the install button.
• The FAQ answers six questions, including what happens to a multi-page TIFF and how a batch is collected into one ZIP.
• The privacy policy is the authoritative statement about data — for the extension, and for the website.
• llms.txt is this page's summary in plain text.
• Questions about privacy go to [email protected].