OptimizePixels Frequently Asked Questions

Answers about local image processing, browser storage, supported outputs, quality settings, resizing, batches and troubleshooting.

These answers cover the OptimizePixels application itself: where processing happens, how projects are stored, what the controls mean and how to diagnose a disappointing result. For broader image-delivery advice, use the linked guides.

Privacy and storage

Do my images leave this device for processing?

No. The application processes selected images locally in your browser. Source files and processed results are not sent to an OptimizePixels image-processing server for conversion, resizing, previewing or result preparation.

Where is my working project stored?

The project can be stored in this browser’s IndexedDB site-data store on the same device so it can be restored. This is not cloud storage or a permanent backup. See the local processing guide for the full explanation.

Will clearing my browser cache delete the project?

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

Can I use the tool on a shared computer?

You can, but clear the project and browser site data afterward if the images should not remain available to another user of that browser profile.

Does local processing mean the site collects no information?

No. Local processing specifically describes the image workflow. Normal website requests and any enabled, consented analytics or advertising services are explained separately in the Privacy Statement and Cookie Policy.

Formats and quality

Which output formats can I choose?

The optimizer provides WebP, AVIF, JPEG and PNG output. The best choice depends on the image, required transparency, delivery environment and tested visual result.

Which format should I try first?

WebP is a practical first test for many web images. Compare AVIF for large photographs, use JPEG where traditional compatibility matters, and test PNG for screenshots, transparency or exact raster detail.

Does quality 80 retain exactly 80 percent of the image?

No. The value controls an encoder and is not an objective percentage of quality retained. Values are not directly comparable across formats or different encoders.

When should I use lossless output?

Use it when preserving decoded pixel data is important, such as some screenshots, sharp graphics and transparent assets. For photographs, carefully reviewed lossy compression can produce much smaller delivery files.

Should I keep the original image?

Yes. Treat optimized website files as delivery copies and retain the best available source separately for future editing, cropping or export.

Resizing and batches

Should I resize before adjusting quality?

Yes. Establish realistic delivery dimensions first, then tune format and quality for the pixels that will actually be served.

How do I avoid stretching an image?

Keep the aspect ratio locked so changing one dimension updates the other proportionally. Crop deliberately when the design requires a different shape.

Can I process several images at once?

Yes. Add multiple files, apply shared settings and save successful results together. Inspect representative and unusual images because one setting can affect them differently.

Why does a large batch take time?

Processing uses your device. High-resolution sources, AVIF encoding, large batches and limited browser memory can increase processing time. Try fewer images or smaller target dimensions.

Results and troubleshooting

Why is the optimized file sometimes larger?

The selected output may be inefficient for that image, dimensions may be unchanged, or the quality setting may be unnecessarily high. Compare another format, resize first or adjust quality.

Why does the output look blurry?

The target dimensions may be too small, the quality may be too aggressive, or a small source may have been enlarged. Review dimensions and increase quality or return to a better source.

What should I inspect before saving?

Check faces, text, fine edges, gradients, shadows, repeated texture and transparency. Review at the intended display size and use the closer comparison view to diagnose damage.

Can I recover a previous result after changing settings?

The working project may restore locally, but you should save approved outputs and keep originals separately rather than relying on browser storage as an archive.

Still learning what works for your image?

Start with a conservative setting, compare the output and adjust one decision at a time.