Facefork

At a glance

Facefork is worth considering when you want to explore several photo edits without losing how one version led to another. Each edit becomes a branch on a canvas, so glasses, a beard and a change built on the glasses can remain separate choices. The bundled sample makes that idea visible before you supply a photo or key. New edits require your own OpenRouter access and paid model usage; this is not a free local image generator.

Good fit

People experimenting with a portrait or comparing several visual directions. The sample tree includes separate glasses and beard edits, a beard added after the glasses, and a composite with two source images. Opening an edited portrait shows its path from the original. That lineage is the useful difference from a folder of unexplained outputs. The sample is pre-generated, so its appearance demonstrates the interface rather than the quality you will necessarily get from a fresh request.

Consider something else when

You need edits to stay entirely on your device, predictable manual retouching or a generator with included usage. The browser calls OpenRouter with the prompt and reference images for an edit, passing them to the selected model provider. Identity preservation is requested in the prompt, not guaranteed. Higher-resolution re-rendering is a new generation that can cost more and change details; it is not simply downloading the same pixels at a larger size.

Start here

Explore the bundled Sam and Mona Lisa tree first. Use View on the glasses edit to see the enlarged image and its path from the original. The interface also offers Hold to compare with the parent. For a new edit, open Settings, review the selected model and resolution, and add your own OpenRouter key with a spending limit. Each resulting edit is intended to appear as a connected branch. Actual generation was not tried in this assessment.

Cost and requirements

Browsing the bundled sample required no account or payment. The app is 0BSD-licensed and can be self-hosted, but generating edits uses your OpenRouter account and the chosen provider’s pricing. The interface gives rough estimates; do not treat the README’s example price as a fixed tariff. Download saves an existing image, while Re-render makes another model request that can incur a charge. Resolution choices are limited to what the selected model supports. Self-hosting and actual paid generation were not tested.

Limits to know

The published storage code keeps the graph and image data in IndexedDB and settings in localStorage; the interface says the key stays in this browser too. Its documented export saves the tree as a .facefork archive before clearing site data. The API source sends reference images directly to OpenRouter, while the header configuration permits connections to the site itself and OpenRouter. This supports the stated design, not a deployed privacy audit or a guarantee about provider retention. Export/import, deletion, sharing and generation quality remain untested; advertised keyboard parent navigation produced no visible change in this inspection.

Still unclear

• How consistently does the intended model preserve the subject and follow edits on the reader’s own permitted images?
• Do export/import and the intended browser’s storage limits preserve a large tree reliably?