Some converters upload; others run in the browser
A website can decode and encode an image with browser APIs, or send the file to a remote conversion service. There are also hybrid tools that process some formats or operations locally and others remotely. The interface alone is not enough to identify the path.
Read the product’s documentation for the named tool. If you need stronger confirmation, use browser developer tools on a non-sensitive test file and inspect network requests when you select and process it. Avoid treating a single network observation as proof of every feature’s behavior.
Signals worth checking
Check whether the tool explains local processing, asks you to upload before conversion, or links to a retention policy. Look for requests containing file data in the browser’s network panel, while remembering that network tools require careful interpretation and can be affected by previews, telemetry, and other requests.
A privacy statement should identify what happens to inputs and outputs, how long they are retained, and whether outside processors are involved. If it omits an answer, treat that detail as unverified. Do not assume that a short processing time means local work or that a “secure” label specifies a retention period.
Pixuna’s Image Converter
Pixuna’s converter reads the selected image in the browser, draws it to a canvas, and requests an encoded output from the browser. Output formats depend on browser encoder support; the frontend reports an error if the requested output type is not produced.
The converter exposes JPEG, PNG, WebP, AVIF, BMP, HEIC, GIF, TIFF, and ICO choices, but the presence of a choice does not guarantee that every browser can encode it. Confirm the downloaded file in your target application, especially when transparency or an exact output format matters.