Does Pixsoma upload my images?

No. Pixsoma decodes, resizes and encodes images locally in the browser. The image data is not sent to Pixsoma for processing.

Can I verify that there are no uploads?

Yes. Open the browser developer tools Network panel, process an image and inspect the requests. No request containing the image file is sent to Pixsoma.

Does Pixsoma use cookies or analytics?

Pixsoma does not use advertising or analytics cookies. A local daily-use counter and optional Pro or profile information are stored in the browser.

pixsoma

Resize images privately - without uploading them

local processing - no account - no watermark - no ads

Pixsoma performs resizing, cropping, compression and format conversion on your device. Client photos, unreleased screenshots, product images and internal documents do not enter an upload queue or image-processing server.

Open the private image resizer

What "private browser processing" means

Your images stay local

The browser reads the selected files and uses its Canvas API to create the output. Pixsoma does not receive the source or result.

No image account required

The free workflow opens immediately. You do not need to create a profile or provide an email address.

No advertising trackers

Pixsoma has no ad network and no analytics tracker. Fonts and processing scripts are served from the Pixsoma site.

Offline after the first load

The service worker caches the tool and core assets. Once loaded, ordinary resizing can continue if the connection drops.

Scope of the privacy claim: Opening any website still creates normal requests for the page itself. Pixsoma's claim is specific: the image files you select are not uploaded for processing.

Verify the claim in your browser

Open Pixsoma and then the browser's developer tools.
Select the Network panel and clear its existing entries.
Add and process an image.
Inspect the network list: page assets may appear, but there is no image-upload request containing your file.

Developer tools - Network - clear - process an image - inspect requests

Data that remains in browser storage

The free daily-use counter and its calendar date.
An activated license state for the current device.
Saved Pro profiles and filename settings when you choose to save them.

These items are small settings, not copies of the selected image files. Clearing site storage removes them and may also deactivate local license state on that browser.

When local processing is especially useful

Client work and product launches that have not been published yet.
App Store and Google Play screenshots from pre-release builds.
Internal documentation or screenshots that contain business information.
Large image folders where upload and re-download time would be wasteful.

Private image resizer FAQ

Does Pixsoma send filenames to a server?

No image-processing request is sent. Filenames are read locally so Pixsoma can create output names and ZIP folders.

Can a browser extension still see my page?

Browser extensions and software installed on your device operate outside Pixsoma's control. Use a trusted browser profile when working with sensitive material.

Why does the page need an internet connection initially?

The browser must first download the Pixsoma page, fonts and scripts. The image data itself is processed locally, and the cached tool can continue working after the connection drops.

Is the checkout also local?

No. Purchasing and license activation use Lemon Squeezy. That is separate from image processing and only happens when you open checkout or activate a license.