Privacy Policy

This page describes what actually happens to a file when you use this site. It is written to be checkable against the behaviour of the tool rather than to be legally comprehensive, and it states the one thing most converters leave vague: which conversions involve an upload.

Conversions that stay on your device

When your browser can decode the input format and encode the output format, the entire conversion happens locally using the canvas element. No part of the image is transmitted to this server or to anyone else. This covers:

• Input: PNG, JPG, GIF, BMP, ICO and SVG on current browsers, plus WebP, AVIF and HEIC where the platform ships a decoder.
• Output: PNG, JPG, WebP and AVIF.

Files converted this way are labelled on device in the result list. That label is the evidence, not this paragraph.

Conversions that are uploaded

When your browser cannot decode the input format, the file is sent to the server, converted, and returned in the same HTTP response. This applies to HEIC on browsers without a decoder, AVIF on older browsers, TIFF, and some BMP variants. Files converted this way are labelled server.

An uploaded file is read into memory for the duration of the request. It is not written to the server's disk, not entered into a database, not added to a queue, and not retained after the response is sent. The response is marked no-store so that neither your browser nor any intermediary caches the converted result.

What is logged

The web server writes ordinary access logs: the requesting address, the time, the path, the HTTP status and the user agent. This is standard for any web server and is used for capacity planning and abuse prevention. The contents of your image are never logged, and the file name is not written to the application log. Error logs record the technical cause of a failure, such as which codec rejected the file, without image data.

Rate limiting

To stop one client from occupying every worker, requests that reach the server are limited to a modest number per minute from the same address. The counter is a file on the server keyed by a hash of the address, and it stores only a count and a time window. It is deleted as it expires and is not used for anything else.

Cookies and tracking

The converter sets no cookies and stores nothing in your browser's local storage. There is no account system, so there is no session to track.

This deployment currently runs no advertising code at all. The page templates contain reserved advertising positions, but nothing is loaded into them.

Children

The service is a general-purpose utility and is not directed at children. It collects no personal information beyond what any web server records in its access logs.

Your choices

If you would rather not upload a file, check the label after conversion. If it says server and you would prefer not to upload, that conversion cannot be done locally by your browser, and the alternatives are software on your own machine or a different browser that can decode the format.

Changes to this policy

If the behaviour described here changes, this page changes with it. The effective date below records the last revision.

Last updated: 1 November 2024.