Identity / Use case

Creative editing.
Clear boundaries.

Understand the difference between a permission-based face edit and a misleading or harmful use of synthetic identity media.

Responsible identity editing begins with permission and a clearly understood context. Face replacement can be part of an authorized creative project; it should not be presented as a way to manufacture authentic evidence of someone’s actions.

Explore Face Swap

Face Swap / Identity studyRecorded Studio result
Synthetic target portrait before Face Swap
Studio Face Swap result with the source identity and original target scene
BeforeAfter
Actual Studio Face Swap using two synthetic portraits. Compare the target and result, then open the recipe to view the separate identity source and detailed controls.View the recorded recipe
01 / Start with
Authorized identity media
02 / Direct
Purpose, context, and disclosure
03 / Review
A responsibly reviewed edit

From input to intention

Give the idea a clear path.

Prepare the input, express the intention, and review what actually changed.

01

Establish permission

Confirm who owns or controls the source material and whether the depicted person has authorized the intended identity use.

02

Consider the final context

Ask how the image or clip will be interpreted. An edit that is obvious in a workshop can become misleading when separated from its caption or original context.

03

Review before sharing

Inspect quality and meaning together. Keep source records and use clear disclosure where needed to prevent the result from being mistaken for an authentic recording.

Start with a useful brief

A direction you can adapt.

Use this as a starting brief, then adjust it to your own source and intention.

Example direction

Prepare an authorized identity-editing demonstration. Show the source and target roles, state that the result is edited, and avoid contexts that imply an unapproved statement, endorsement, or event.

Review checklist, not a generation prompt. Photo Face Swap uses the two source/target portraits and the controls in the recorded recipe. Both example portraits are synthetic Studio creations.

01

A plausible result is not an authentic record

An edited image can look realistic while depicting something that never happened. Visual plausibility should not be used as a substitute for truth or consent.

Do not use identity tools for fraud, harassment, harmful impersonation, or non-consensual intimate content. The existing site guidelines apply to the creative process and the way the result is shared.

02

Permission should match the intended use

Permission to view or repost a photograph is not automatically permission to place a person into a new scene. Consider the purpose, audience, and any meaningful change of context.

Keep authorization connected to the project. If the intended use changes, reassess whether the existing permission still fits rather than assuming it covers every future variation.

03

Transparency belongs in the workflow

A useful demonstration explains the source, target, and transformation. This lets viewers understand what they are seeing rather than inferring an authentic event from the final image alone.

Where identity media involves a sensitive context, use a cautious review process and the existing support route for questions. This page is product guidance, not a replacement for the site’s legal terms.

The useful details

A few good
questions.

Is a realistic face edit evidence of a real event?

No. A synthetic identity edit can depict an event or participation that never occurred.

Can I use a publicly available photo as permission?

No. Access to a photo and authorization for an identity transformation are different things.

Why keep this older URL?

It remains a discovery route for the existing site, while the content explains legitimate use and points to the familiar Face Swap tool.

Does this create a new legal policy?

No. It does not replace or rewrite the existing terms, privacy policy, or usage guidelines.

Connected workflows

A different starting point?

All use cases

One tool. More possibilities.

Keep the workflow simple.

This use case belongs inside the broader tool. Explore related approaches without learning a different navigation system.

Open in Studio