Do originals leave my device?
Processing happens in the browser. We don’t receive or store your original image content.
FAQ
ImageAwe is a local image toolbox in the browser: pick a tool, export, download. Below you’ll find privacy, pricing, formats, batch, cutout, devices, troubleshooting, and copyright. Or search by keyword to jump straight to an answer.
Processing happens in the browser. We don’t receive or store your original image content.
No. All fifteen tools are free to use now — no login wall, no usage meter.
Yes. Eight tools including cutout, compress, and convert support batch; download one-by-one or as a zip.
Yes in the browser. Fine drag work is easier on a tablet or computer.
Plain answer first: does the file stay on your side, or get sent elsewhere?
No. Reading, processing, and export run in the current browser session (Canvas, WebAssembly, and similar local APIs). There is no backend endpoint that receives or stores your images, so there is no path for a “silent server copy.”
Segmentation and compositing also run on-device. Your original is not sent as content to a server. The first use may download a model/component into the browser cache — that file is a general model, not your photo.
Pixels in flight live mainly in page memory; closing or refreshing clears them. We don’t write cookies or long-lived local stores just to keep your original around.
No. If the original never reaches our servers, it can’t be reused, trained on, or sold.
You need a network the first time you open a page and when models/static assets are fetched. After caching, computation itself is local. We don’t ship a full installable offline pack yet — stay online for reliable first loads and updates.
How the workspace and tool pages work today: barriers, limits, mid-flow charges.
Yes. All fifteen tools are free to use, and pages don’t require a paid membership before export.
No. Open a tool page or the workspace and start. Export doesn’t depend on an account.
There’s no per-account quota wall. Practical limits come from device memory and the browser. Keep singles around 20MB or under, and don’t dump huge batches of large files at once.
Not today. If a more advanced paid capability appears later, it will be labeled on that tool page up front — not sprung at the moment you export.
Unreadable HEIC, PNG vs JPG, and whether compression will look soft — pick by export goal.
Which format to export
| Format | When it fits |
|---|---|
| JPG | Everyday photos, form uploads, max compatibility — usually smaller files |
| PNG | Transparency, icons, screenshots, cutout results |
| WebP | Web delivery — often smaller than JPG/PNG at similar look |
| HEIC | Common from iPhone cameras; many non-Apple apps/sites can’t open it — convert first |
| AVIF | Newer efficient compression; avoid if the recipient’s software is old |
| BMP | Large files; rarely ideal for web or chat |
| GIF | Simple motion or stickers; usually not for still photos |
Open Convert Format and export JPG or PNG. After that, most galleries, desktops, and upload forms will accept it.
It depends on your settings. A harsh quality slider shows more damage; Target size / target KB mode aims to hit a size cap while protecting look. Set the upload limit first, then compress — usually better than slamming quality to minimum.
Need transparency or hard-edged graphics → PNG. Everyday photos without alpha → JPG is often smaller. Want web-friendly size with decent look → consider WebP.
No. Those steps change encoding and file size, not canvas dimensions. Use Resize or Crop to change side length.
Recent mainstream browsers and many phone galleries can. If the other side runs older software, JPG / PNG is the safe bet.
Which tools accept multi-select, and how to avoid freezes when downloading.
Tools with batch mode
Background removal, format convert, compress, image to PDF, resize, rotate/flip, watermark, and EXIF view/clear — eight tools support batch. The rest are geared to one-image refinement.
There’s no single hard site-wide number; pages give tool-specific hints. What matters more is not exhausting memory. Keep files roughly under 20MB and split huge jobs.
Download per file, or grab a zip of the whole set and unpack it.
No. Each image runs on its own. A bad or unsupported file usually only blocks itself; the rest can still export.
Heavy work prefers Web Workers so the UI stays responsive, but memory still comes from your device. If it stutters, cut the count or compress to a target size first.
First-run slowness, frayed edges, and what backgrounds you can swap to.
Segmentation and compositing finish in the browser. The original stays with you — no round-trip to a cloud mask service.
Expected. The first run fetches a model/component; once cached, later runs in the same browser are much faster. Slow networks stretch that first wait.
Start from a source with clearer color/brightness separation; even lighting helps. You can also switch to a higher-quality model on the tool page. Extremely fine hair may still need a little manual cleanup afterward.
Common people and product subjects separate well — ID-photo color swaps and ecommerce white backgrounds are typical. After cutout: transparent, solid color, or your own backdrop image.
Pixel count and device power both matter. A decent laptop is often a few seconds; older phones or low-end PCs take longer — that’s expected.
Installs, which browsers to use, and how phone vs tablet differs.
No. ImageAwe is web-based — open the page in a browser and go.
Chrome, Edge, Safari, or Firefox updated within about the last two years usually have full support. Very old engines may lack WebAssembly or other APIs some tools need.
Core capability matches; layout adapts (settings may live in a bottom bar). Precise crop or brush work is easier after zooming, or on a tablet/computer.
Light tools like compress, crop, and convert are easy on older hardware. Cutout is heavier — slower, not usually “impossible.”
Usable. Layout sits between phone and desktop; crop handles and mosaic brushes have touch-friendly hit areas.
No response on pick, endless spinner, or a download that won’t open — try these first.
Confirm the format is supported for that tool and the file isn’t far above ~20MB. Compress first if needed, then retry; refresh or switch to a mainstream browser if it still fails.
Cutout’s first model download can sit for a while on a weak network. If nothing moves for a long time, refresh and retry; also check file size and batch count.
Make sure the download finished. Batch zips need unzipping first. Still broken? Export again, or try another folder/browser.
Most tools let you tweak settings or re-pick an image without a hard refresh. The original file on disk isn’t rewritten, so you can always import again.
Hard-refresh to clear cache, or open in another mainstream browser. If it keeps happening, contact us with device and browser version via the footer.
Tools are neutral; rights live in the content — commercial use, watermarks, and other people’s work.
The tools only process. Whether you may use, alter, or share that image is on you. Confirm you have the rights and respect the creator.
No. A watermark is a visible mark for deterrence or credit — it doesn’t transfer copyright.
ImageAwe doesn’t endorse commercial rights for a given image. That depends on the original’s license and local law — verify before business use.
No. Results don’t automatically add an ImageAwe logo, watermark, or forced credit.
No matching entry — try another keyword.
Still not your case?
How to Use covers paths; Use Cases groups tools by job. For a specific error, tell us the browser and tool name on the contact page.
No sign-up. Download when done — or open the workspace to switch tools on one page.