Pixuna

How Pixuna handles media

Privacy and file processing

Pixuna uses different processing paths for images and videos. This page explains the image workflow and why video processing is temporarily unavailable.

Image tools process selected files in your browser

The image compressor, resizer, converter, crop-and-rotate, and format optimizer use browser image APIs to read, transform, and export the selected image. Their processing code does not send those selected image files to a remote media-processing API.

Browser processing uses the device’s memory and compute, and available decoders and encoders can vary by browser. This describes the media-processing path; it is not a certification about every website request, browser extension, device, or hosting component.

PDF tools process selected files in your browser

The PDF tools read the selected files into browser memory, edit or render them with JavaScript libraries running in your tab, and produce the download there. Their processing code does not send your PDFs to a remote API. You can confirm this with your browser’s network panel while a tool runs.

Large PDFs can exhaust browser memory, some encrypted or unusual files may not open, and the Unlock PDF tool only works when you supply the correct password. Password protection uses AES-256 encryption performed in your browser.

Document and spreadsheet tools process text and files in your browser

The document and spreadsheet tools read the text you type or the files you open into browser memory and convert, format, or compare them with JavaScript running in your tab. Their processing code does not send your text, documents, or spreadsheets to a remote API. You can confirm this with your browser’s network panel while a tool runs.

Very large files can exhaust browser memory. Avoid pasting passwords or live secrets into any web page when sample data will do.

Video tools are temporarily unavailable

Pixuna’s video compressor, video converter, and video-to-GIF pages are currently disabled while the processing service is paused. The saved frontend implementation sent selected videos as multipart form data to a configured API, but it does not establish the backend’s storage, access, logs, backups, third-party processors, cleanup, or deletion behavior.

Why the difference matters

Local image processing avoids sending the selected image to a media-processing API. A future server-processed workflow would require a file transfer and should only be restored when the service is available and its handling practices are understood.

Choose a workflow that fits the sensitivity of your files. For confidential media, use only a service whose operational policies and retention controls meet your needs.

Read more