Evergreen
What Is a Photo After Generative AI Editing?
Distinguish sensor capture, computational rendering, frame selection, composites, object removal, generative extension, and fully generated images.
What Is a Photo After Generative Editing?
After generative editing, a photo is best described by its production history rather than forced into a simple real-or-fake category.
An image can contain sensor capture, computational rendering, selected frames, composited people, removed objects, and generated pixels at the same time.
flowchart LR
A["Sensor capture"] --> B["Computational rendering"]
B --> C["Frame selection"]
C --> D["Composite or relocation"]
D --> E["Generative pixels"]
E --> F["Final image and disclosure"]
Sensor capture
A camera begins with light reaching a sensor through a lens.
Even this is not a neutral copy of the world. Exposure, focus, lens choice, position, timing, and framing determine what is recorded.
A sensor capture can still mislead through omission, staging, caption, or use outside its original context.
Computational rendering
Modern phones process sensor data before a person sees the final image.
Multiple exposures may be combined. Noise can be reduced. Tone, color, sharpness, faces, shadows, and highlights can be adjusted.
This computation can make a photo more legible or aesthetically pleasing without introducing a new object. It still changes the relationship between raw sensor measurements and the displayed image.
Calling every computational photograph AI-generated would be too broad. Record the processing when it matters.
Frame selection
A motion photo or burst captures several nearby moments.
Choosing one frame changes which expression or gesture represents the event. A feature such as Best Take can help select expressions from nearby captures for different people.
The people and expressions may all have been captured, while the final combination never existed in one instant.
"Selected from a capture sequence" or "composited from nearby frames" conveys more than real or fake.
Composite
A composite combines elements from more than one capture.
Google's Add Me example allows the photographer to enter a group image through a second capture. The final file can depict people who were together at the event without recording one moment when everyone faced the same camera.
Compositing has a long history. Automation makes it easier, faster, and less visible.
Disclosure depends on the use and the viewer's reasonable expectation.
Removal and relocation
Object removal deletes recorded content. Relocation changes where recorded content appears.
The edit can be harmless in a personal image and material in a news, insurance, legal, medical, employment, or investigative context.
The technical action is the same. The consequence changes with the claim the image is being used to support.
Generative extension
Generative editing can add pixels that were never captured.
It may extend a sky, rebuild an occluded surface, change a background, or fill the space left by a removed object.
The result may be visually plausible because the system predicts content that fits surrounding patterns. Plausibility is not evidence that the generated content existed.
Current Google Photos editing help documents Auto frame as an AI feature that can fill or expand a picture. It also documents other selection and object-editing tools.
That current product record supports tool behavior, not the truth of any edited image.
Fully generated image
A fully generated image does not begin with a corresponding scene capture.
It may still use reference images, style, text, or other inputs. It can be art, illustration, simulation, or deception depending on its purpose and presentation.
The distinction from a generative edit matters because an edited photo can preserve substantial evidence from a real capture while also containing invented parts.
Production history is not truth
The C2PA explainer describes provenance and Content Credentials as ways to record origin and actions. It also states that the system does not judge whether provenance assertions are true.
Google's current photo information help similarly says AI information may be stored through IPTC metadata while warning that the data can be edited or removed.
These mechanisms can support an account of how a file was made. They cannot determine whether the scene was staged, the caption is false, or the image is being used to imply something it does not show.
Use precise language
Describe what is known.
| Known history | Useful description |
|---|---|
| One recorded frame with ordinary rendering | Camera photograph |
| Several exposures merged by the camera | Computational photograph |
| Expression selected from a capture sequence | Frame-selected photograph |
| People or elements joined from captures | Composite photograph |
| Recorded content removed or moved | Materially edited photograph |
| New pixels added to a captured image | Generatively edited photograph |
| No corresponding scene capture | Generated image |
When history is unknown, say that.
Do not call an image authentic solely because metadata exists. Do not call it synthetic solely because credentials are absent.
Use [[How to Verify the Provenance of an AI Edited Image]] to inspect available history. Use [[How to Review an AI Edited Image for High Stakes Use]] when a consequential decision depends on the image.
This concept explainer was developed with AI assistance from E030, current Google Photos documentation, C2PA material, and the linked taxonomy. Dalton Anderson remains the author. Editorial, provenance, ethics, accessibility, current-source, and founder review are mandatory before publication. Publication is not authorized.
Sources
Follow the evidence.
- iptc.org: photo metadataiptc.org
- store.google.com: phonesstore.google.com
- support.google.com: find out if your photos have been edited with aisupport.google.com
- daltonanderson.ghost.io: googles ai magic a pixel 9 gemini deep divedaltonanderson.ghost.io
- c2pa.org: Explainerc2pa.org
- support.google.com: 6128850support.google.com
- youtu.be: vmMnqx ZGFEyoutu.be
- blog.google: made by google 2024 collectionblog.google
- open.spotify.com: 4wQhhIrcfJ3wgclijI5256open.spotify.com
- support.google.com: pixelphonesupport.google.com
- support.google.com: 15532903support.google.com
- spec.c2pa.org: C2PA Specificationspec.c2pa.org