Local Image Processing and Browser Storage

Learn how OptimizePixels processes images in your browser, stores projects on your device, and what clearing cache or site data can remove.

OptimizePixels processes your images inside the browser on the device you are using. When you choose an image, the browser makes that file available to the workspace. OptimizePixels then decodes, resizes, converts and previews it locally. Your source image and processed result are not sent to an OptimizePixels image-processing server.

The browser can also retain a working project on this device. That convenience is local persistence, not cloud storage or a permanent backup.

The short version

Image processing runs inside your browser on this device.

OptimizePixels does not receive your source images or processed results for the image workflow.

A project may be restored only in the same browser profile on the same device.

Clearing cached page files is different from clearing browser site data.

Clearing OptimizePixels site data can permanently remove locally stored projects.

Save finished images to your device if you want to keep them.

Where the working copy lives

Selected file

The original remains a file on your device and is made available to this browser tab.

Browser workspace

The open tab holds previews and working pixel data while you edit settings.

Optional restoration

IndexedDB may retain the project in this browser profile so it can return later.

Saved output

A finished image or ZIP becomes a separate file only when you save it.

Browser memory and IndexedDB belong to the browser profile on this device. Neither is an OptimizePixels cloud account or recoverable server backup.

What happens on your device

You choose an image

The browser gives the page access only to files you select or drop into the workspace. Choosing a file does not by itself send that file across the Internet.

The browser opens it locally

The application reads the file and creates a preview in browser memory. It can also store the working project in the browser’s IndexedDB site-data store so the workspace can be restored later.

The browser processes the pixels

Resizing and format conversion use browser capabilities and image codecs delivered with the application. Processing time therefore depends on the image, settings, browser and device resources.

You save the result

The browser prepares the processed file or ZIP and lets you save it to your device. OptimizePixels does not keep a server copy that you can retrieve later.

Cache, site data and saved files are different

Browser term. What it contains. What clearing it may do

Cached images and files. Copies of website assets used to load pages faster. Usually removes reusable page resources; it does not necessarily remove an OptimizePixels project

Cookies and site data. Site preferences and browser databases, including IndexedDB. Can remove the locally stored OptimizePixels project and its images

OptimizePixels project. Original and processed working files, file details and settings stored in IndexedDB. Is removed when you use Clear All, remove the site’s stored data, or the browser removes that storage

Files saved to your device. Finished images or ZIP files in a folder you choose. Remain separate from the browser project unless you delete them yourself

Browser storage is not a backup

A restored project is a convenience, not a storage guarantee. It is tied to one browser profile and device. Private or incognito windows normally discard site data when the session ends. Cleanup utilities, storage pressure, browser resets, profile deletion or uninstalling the browser may also remove it. Save every finished image you want to keep and retain important originals separately.

What ‘local processing’ does and does not mean

Local processing describes the image workflow. Your browser still connects to the OptimizePixels website to load the application, pages, fonts and other assets. Those normal requests can include technical connection information such as an IP address, browser identifier, requested URL and timestamps.

The privacy-request form is also separate from the image workspace. It sends the details you enter to the server because we need to receive them to respond. Optional analytics or advertising services, when configured and permitted, are described separately in the Privacy Statement and Cookie Notice .

Using a shared device

Someone using the same unlocked browser profile may be able to reopen a locally stored project. Use Clear All after saving your finished files, then remove OptimizePixels site data through the browser if the images should not remain on that device.

Local processing questions

Can OptimizePixels retrieve my images from its server?

No. The image workflow does not create an OptimizePixels server copy. If the browser project and your saved files are deleted, OptimizePixels cannot recover them for you.

Will clearing my browser cache delete the project?

Clearing only cached images and files may leave the project intact. Clearing cookies and site data, all browsing data, or storage specifically for OptimizePixels can remove it. Browser labels and combined cleanup options vary.

Can I continue the project on another device?

No. Local project restoration is limited to the same browser profile on the same device. There is no account or cloud synchronization.

What happens in private or incognito browsing?

The image workflow still runs locally, but private sessions usually remove their site data when the private session ends. Save results before closing the session.

How do I remove the local project?

Use Clear All in the workspace. On a shared device, also remove OptimizePixels cookies and site data through the browser’s privacy or storage settings.

Use the local image workflow

Choose images from your device, adjust the output and save the results you want to keep.