How it works
From scattered generations to one production memory.
Keep generating in the tools you already use. BTW gives every asset a searchable home and keeps its prompt, model, references, versions and decisions attached, so the team can find, reproduce and hand off the work later.
No credit card. Setting up the first project takes about two minutes.
The loop
Capture, iterate, set the final, hand it off.
You keep generating where you already generate. BTW wraps four steps around that work, and this page walks each one in full. Follow an asset from the moment the extension captures it, through every version on the shot, to the final that carries its whole record when you hand it off.
Step 01
Your work enters BTW straight from the tool.
The browser extension sits next to whatever generator you are working in, so the moment a result is worth keeping you send it into a BTW project without leaving the tab. It reads the prompt that ran, the tool and the exact model version, the seed and aspect, and the reference images you fed in, and it attaches all of it to the file as the file arrives. Nothing is copied by hand and nothing is reconstructed from memory later, because the account of how the asset was made is written down at the one moment it is still fully known. That single moment is the one the Article 50 transparency and documentation duties, which begin on 2 August 2026, expect you to have on record.
- Send from the generator's own tab through the browser extension, with no window switch
- Prompt, tool, exact model version, seed, aspect and reference images attach to the file as it lands
- The record is written at generation time, while the details are still known, not pieced together afterwards
Extension · CaptureStep 02
Every version stays linked to the shot.
Every new variation you capture lands on the same shot on the workflow canvas, next to the versions that came before it. The canvas lays the attempts out in the order they were made and keeps each one tied to the prompt, model and references it came from, so a version is never just a loose file with a cryptic name. You can see where a look started, which change moved it forward and who made each pass, because the author and the time ride along with every version. When a shot needs another round weeks later, the whole line of attempts is already in front of you instead of scattered across drives and chat threads.
- New variations attach to the shot on the workflow canvas, laid out in the order they were made
- Each version keeps its own prompt, model, references, author and time
- The full line of attempts stays on one shot rather than spread across folders and chats
Workflow · VersionsStep 03
You mark the version that ships.
When one version is the one that ships, you set it as final in a single move, and the versions around it are marked held for later or killed outright. Each of those calls is written onto the shot with the person who made it and the time it was made, so the decision lives in the record rather than in someone's memory. Exactly one version wears the final status, and the reasons the others were set aside sit right beside it. When a client reopens the shot weeks later or a new editor picks it up, the shipped version and the story behind the choice are already clear.
- Set the shipping version as final in one move, and hold or kill the rest
- Every hold, kill and final decision is stamped with its author and time on the shot
- One unambiguous final, with the reasons the others were set aside kept beside it
Workflow · FinalStep 04
Hand off the final with its full record.
You share the final in one click, as a link or a handoff, and its whole record goes with it rather than as a separate document you have to assemble. The person on the other end opens the asset and finds the prompt that ran, the tool and model version, the seed and references, the hold, kill and final decisions, and the author and time behind each one, all in one place. It is a declared, reproducible account of what was attached at each step, not a cryptographic proof, and that is usually exactly what a client, a rights office or an Article 50 disclosure asks for. Because the record was built as you worked, answering how something was made is a matter of opening the asset, not of digging back through drives and chats.
- Share or hand off the final as a link in one click, with no separate document to assemble
- Prompt, model, seed, references, decisions, author and time all open with the asset
- A declared, reproducible record of what was attached, ready for a client or an Article 50 disclosure
Handoff · Share
The extension
Integrate the workflow directly into your AI workspace.
Capture stays where you already work. The moment a generation is done, you send it into BTW from the tool you made it in, without switching windows and without breaking your flow. The prompt, the model and the references come with it.
The record
What one asset carries with it.
Every one of these is recorded on the asset itself, so all of it travels with the asset when you share it or hand it over.
- Prompt
- The text that ran, kept verbatim and searchable.
- Tool and model
- Which generator produced it, and which model version.
- Seed and aspect
- The settings that let you run it again.
- References
- The images attached to the shot, with their rights status.
- Versions
- The iterations before it, in the order they were made.
- Decision
- Whether it was held, killed or marked final.
- Author and time
- Who created the version, and when.
- Comments
- The feedback that was left on it, in place.
FAQ
Frequently asked
- What is Behind The Workflow?
- Behind The Workflow (BTW) is production memory for AI teams. It sits above the AI tools you already use and keeps the record behind every shot, from every prompt, model, reference and version to who made it, when and why, in one searchable place, so nothing has to be reverse-engineered weeks later.
- Do I have to change the AI tools I use?
- No. BTW is neutral by design. You keep generating in Midjourney, Runway, ComfyUI, Freepik or whatever you already use, while BTW sits above all of them and captures the trail behind each shot. Your creative workflow doesn't change.
- Who is BTW for?
- Solo AI artists, directors and producers, and production companies. It scales from one person's workflow up to a full studio with shared projects and clear roles, without anyone switching tools.
- How does BTW help with the EU AI Act?
- From 2 August 2026 the EU AI Act's transparency and documentation duties for AI-generated content take effect, and broadcasters already ask for a record of how AI work was made before they air it. BTW produces that documentation by default as a structured, shareable record of every prompt, model and reference behind each shot.
- Can I share and export my work?
- Yes. Share any image or video straight from BTW with its model, prompt, aspect ratio, author and timestamp attached, in one tap via WhatsApp or email. You can download in full resolution anytime and hand a client the full documentation in a click.
- When can I start?
- BTW is live, so you can start today. Setting up your first project takes about two minutes, and the free plan works without a credit card.
Start
Keep every shot findable, reproducible and ready to hand off.
Keep working in the AI tools you already use. BTW holds the production together for you, your team and the next client question.