How PicShift Handles Privacy and Local Processing

What happens to your files

• Selected images are read by your browser and processed in local browser memory.
• Converted files are generated locally and returned to you as downloadable files.
• PicShift does not require account sign-in to convert images.

What does not leave your device

• Original image content is not uploaded to PicShift servers for conversion.
• Converted image binaries are not stored on PicShift servers.
• No cloud storage account is required for core conversion workflows.

Local settings and analytics

• UI preferences (such as theme, language, and quality defaults) are stored in browser localStorage.
• When enabled, privacy-friendly analytics collects usage events without needing image uploads.
• If analytics are enabled, they are used for product improvement, not file content processing.

Security and trust model

PicShift follows a minimize-data approach: process locally, avoid unnecessary account requirements, and keep user workflows simple. For legal details and policy language, see the Privacy page.

How to verify this yourself

Use this test to verify local-only processing:

1. Disconnect network (airplane mode or Wi-Fi off).
2. Select an image, then convert and download successfully.

Scope and boundaries

• First page load needs network to fetch static assets and WebAssembly codecs.
• After assets are cached, conversion workflows can continue offline.
• Batch conversion supports up to 200 files per run for stable performance.

Technical evidence references

• Privacy policy for legal terms and commitments. /privacy
• Format compatibility guide for supported input/output formats. /docs/format-compatibility
• Quality guide for practical compression and quality behavior. /docs/image-quality-vs-file-size

FAQ