ImgKit

Image tool privacy

Privacy-first image tools with clear processing boundaries

Learn how ImgKit browser image tools handle photos, which edits can run locally, and when a feature requires server processing.

Overview

“Privacy-first” is useful only when it describes an actual processing boundary. ImgKit does not apply one universal claim to every tool. Instead, each workflow should make clear whether the browser can complete the task locally or whether the feature sends data to a service for processing, payment, or delivery.

Local processing can reduce upload time and unnecessary exposure for routine edits. It also means a page refresh can clear in-memory work, and the browser must have enough memory for the selected file. Server processing can support more demanding models or durable delivery, but it requires a different privacy explanation.

Stable facts

Key facts at a glance

Usually local
JPG, PNG, and WebP conversion, compression, resizing, cropping, and image-to-PDF creation where supported.
May require a server
Model-based background removal, payment confirmation, protected delivery, and recovery workflows.
Accounts
Basic browser tools do not require an account.
Storage
Local tool inputs are handled in the active browser workflow rather than stored as a personal media library.
Transparency
The relevant tool page is the source of truth for that feature’s current processing method.
Supported devices
Current desktop and mobile browsers, subject to available device memory and format support.

What local browser processing means

The selected file is decoded and transformed by code running in the browser. The result is generated for download without the normal need to upload the source image to ImgKit. Network requests may still load the application code itself, fonts, analytics, or a format decoder; that does not mean the selected image file was uploaded.

Why some tools use server processing

Some tasks depend on models or infrastructure that are not practical inside every browser. A server may also be required to confirm a payment or provide a durable recovery link. When that boundary exists, the page should say so and avoid presenting the feature as fully local.

How to choose the right workflow

For routine format changes, resizing, cropping, compression, or PDF assembly, start with a browser tool. For model-based editing, read the tool’s privacy note before selecting a file. For sensitive images, remove unnecessary metadata, use only the feature you need, and download or clear results when the task is complete.

  • Check the tool page for its processing note
  • Use the smallest workflow that solves the task
  • Avoid uploading unrelated sensitive images
  • Save the result, then close or reset the active session

Continue exploring

Image converterConvert JPG, PNG, and WebP formats in a focused browser workflow.Image compressorReduce image file size with quality controls.Image to PDFCombine supported images into a PDF in the browser.ImgKit privacy policyRead the site-wide policy and contact details.

FAQ

Common questions

Do ImgKit image tools upload my photos?

Many standard tools process supported files locally, but not every feature is local. Check the specific tool page for its current processing method.

Which tasks commonly run in the browser?

Supported conversion, compression, resizing, cropping, and image-to-PDF tasks commonly run in the browser.

Why would a tool need a server?

A model-based edit, payment, protected delivery, or recovery flow may require server infrastructure.

Do basic tools require an account?

No. Basic browser image tools do not require an ImgKit account.

Does local processing guarantee a file is never exposed anywhere?

It means the tool does not need to upload the selected file for that edit. Users should still consider device security, browser extensions, and any separate services they use.