CONTENT CREATION

Auto-localize any screenshot dropped into R2

Watches an R2 bucket for new raw product screenshots, detects the source language, and generates localized variants for a fixed set of markets into a published folder.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew screenshot uploaded to R2 incoming prefixCloudflareCloudflare R2
  • LogicSkip if already localized
  • ActionGenerate localized variant per marketImage generation
  • ActionWrite variants to published prefixCloudflareCloudflare R2
  • OutputSave manifest JSON of all outputsCloudflareCloudflare R2

What it does

Monitors an incoming R2 bucket where designers drop raw product screenshots and automatically produces a localized variant for each of your standard target markets, writing them to a published prefix.

When to use it

When screenshot localization should be hands-off — anyone on the team drops a PNG and the localized set appears minutes later, with no ticket and no design request.

How it works

  1. 1An R2 object-created event on the `incoming/` prefix triggers the flow with the new screenshot key.
  2. 2The flow reads the image and any sidecar copy file describing the on-image text.
  3. 3A logic step skips files already tagged as localized to avoid reprocessing loops.
  4. 4For each market in the configured list, it regenerates the screenshot with translated overlay text baked in.
  5. 5The localized variants are written to the `published/<market>/` prefix in R2, and a manifest JSON listing every output is saved alongside them.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Cloudflare R2Object storage, S3-compatible.
  2. 2
    Connect Image generationManaged Nano Banana image renders, metered per image.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.