The processing path
GetResizer reads a file you select, decodes it in the browser, changes pixels locally, and creates a downloadable output. Image processing does not use an image-upload endpoint or remote file store. PDF, HEIC and ZIP workflows load optional local-site libraries when needed; their network requests download code rather than upload your document.
Local processing and website data are separate
Opening a website creates normal requests to its host. The public site can also use consent-controlled analytics and advertising. These are distinct from sending an image for processing. Read the privacy policy and cookie information rather than treating 'local' as a claim of zero network activity.
Selected filenames and image data are not sent by GetResizer's processing or upload-checker features. A website's access to a file depends on what you select and the code running in the page, so examine the actual implementation and requests rather than trusting a slogan.
A useful Network-panel check
- Load the tool and open browser developer tools before selecting a non-sensitive test image.
- Clear the Network log, select the file and run one export.
- Distinguish asset, library and analytics requests from requests with a file payload. Inspect request type and body instead of expecting a completely quiet log.
- For ordinary JPG, PNG and WebP processing, test after the required page scripts are loaded with network access disabled.
- For PDF, HEIC or ZIP, load the optional dependency first. An offline failure before that download does not prove that the image needs an upload.
Device limits still apply
A decoded 6000 × 4000 RGBA image needs about 96 MB for one pixel buffer. Decoding, previews and output can require more than one buffer. Input limits are 40 megapixels per image, 80 megapixels across the retained queue and 100 files or PDF pages; outputs have their own 80 megapixel limit. A phone can run out of memory below those limits.
Cancellation may wait for a browser decoding or encoding step already in progress. Split large batches and save ready downloads before changing the queue or settings.
Local does not remove visible private information
An output can still contain a face, address or document number. Camera metadata is another concern, but re-encoding is not a complete anonymization tool. Follow your own organization's requirements for sensitive materials and inspect the actual image before sharing it.
Frequently asked questions
Why do I see network requests during a local export?
The site can load assets, optional libraries, analytics or advertising separately. Inspect payloads to distinguish these from file uploads.
Will every feature work offline immediately?
The required scripts and any optional PDF, HEIC or ZIP dependency must already be loaded.
Does local processing guarantee anonymity?
No. Normal site requests and visible information in an image are separate privacy considerations.
Tools for this guide
Sources and verification
File-size and geometry examples are explained separately from measured exports. Platform rules apply only to the linked service and can change. Report a correction through the publisher's contact page.