What “on-device editing” actually means
On-device editing means the app does the work on your phone’s own processor and never sends the photo to a server. It is faster, it works offline, and it is the kind of privacy you can check yourself. Here is how to tell whether an app really does it, and why most of the features you use every day no longer need the cloud.
Updated
- On-device means the photo is processed on your phone and never uploaded for editing.
- Face detection, smoothing, looks and crop all run on the phone today; only generative tools still need a server.
- You can test it: airplane mode, the App Store privacy label, no account, and a visible network log.
- On-device editing does not by itself mean no tracking; check for analytics and ad identifiers too.
How can an editor work, cloud or phone?
A cloud editor uploads your photo, runs its tools on a server, and downloads the result. An on-device editor runs the tools on the phone. The photo is read from your library, processed in memory, and written back; the network is not involved.
The difference is invisible on screen. Both show a slider and a result. The difference is where the photo goes, who can see it, what happens when your signal drops, and who pays for the computation.
Why did most editing move onto the phone?
Ten years ago, finding a face, mapping its landmarks, separating a person from the background and smoothing skin at full resolution were server jobs. Today every iPhone ships with those models built into the operating system. Face and body landmarks come from Apple Vision. Separating a person from the background is a system call. Color and texture work runs on the graphics chip through Core Image and Metal.
That means an editor can do the entire everyday workflow, smoothing, reshaping, whitening, brightening, looks, crop, without shipping a single model of its own and without a server. The things that still need the cloud are generative: inventing pixels that were not there, upscaling, cartoon styles. Those cost real money per image, which is why they are metered.
What does on-device editing get you?
- Privacy you can check. If the photo never leaves, nobody upstream can keep it, train on it or leak it. The claim is testable: watch the network.
- Speed. A slider drag renders on the phone in milliseconds. No upload, no queue.
- Works offline. On a plane, in a basement, on a dead data plan.
- Full resolution by default. There is no bandwidth bill to make an app downscale your export.
- Small apps. An editor that uses the system’s models does not need to bundle its own hundreds of megabytes.
- Cheap to run. Your phone pays for the computation, which is why the app can be free without a catch.
How can you tell whether an app really edits on-device?
- Turn on airplane mode and edit. If smoothing and filters still work, they are on-device. If a tool fails or spins, it is not.
- Read the App Store privacy label. “Data Not Collected” is the cleanest answer. “Data Used to Track You” with photos or identifiers in the list is the opposite.
- Look for an account. An editor that requires sign-in usually has a server with your photos on it.
- Ask for the network log. Very few apps show one. Sfuma does: Settings → Network activity lists every connection its own code makes, with the purpose.
- Check the size. Hundreds of megabytes usually means bundled models or a lot of bundled content, not necessarily cloud, but it is a tell.
Proof: on a fresh install, Sfuma’s network log reads “No network activity — as promised.” The only host that can appear is sfuma.cam, after you send feedback; App Store purchases run inside iOS and are not listed.
Try the airplane-mode test on Sfuma: switch it on, open a photo and use every tab. Then open Settings → Network activity and read what the app’s own code has done.
What does on-device not mean?
It does not automatically mean no tracking. An app can edit on the phone and still run an analytics kit and an advertising identifier. Those are separate choices, and they show up in the privacy label and in the network log. On-device editing plus no analytics plus no ad identifier is the full set.
It also does not mean “no server anywhere”. Purchases go through Apple. If you choose to send feedback with a photo, that photo goes to the developer, and an honest app tells you exactly what goes before you press Send.
Sources
- Apple. Vision documentation. The on-device framework for face detection, landmarks, body pose and person segmentation.
- Apple. Core Image documentation. The on-device framework for image filters and color work.
- Apple. App privacy details on the App Store. What the privacy label categories mean and what developers must declare.
- Apple Support. About App Privacy Report. How to see which domains an app contacts, built into iOS.
Sfuma runs every tool on your iPhone and shows its own network log. How it is built.
Coming to the App Store — first in Turkey.
Free. No account. No watermark.
More to read
Why filters change your skin tone, and how to tell when one does
Beauty filters blur, brighten and tint, shifting skin lighter and pinker, most visibly on medium and deep skin. A five-second check, and a better way.
Free photo editors without a watermark: the catch, and how to avoid it
Free editors pay for themselves with a watermark paywall, a downscaled export or tracking. A two-minute check, and why a clean free editor is possible now.
How to share a look with a recipe code
Make a Sfuma recipe code, paste one, and see what travels inside: face, skin, detail, color and look settings. Never the photo, crop or body edits.
How to read your app’s network log
A network log lists the servers an app contacted and why. How to read Sfuma’s, what to look for in any log, and how to check apps that have none.