One Gallery for every screen
The Gallery tab shows each screenshot once, with the number of keys on it. Search by screenshot name, page, key name or text, and filter by Figma or uploaded screenshots.
Localization screenshots that show where every key appears.
Upload or paste a screenshot of your app, draw an area for each translation key, and everyone who opens the key sees the screen it belongs to. The project's Gallery keeps every screen and its keys in one place.
Common challenge
A key name and a source string rarely say where a text sits, how much room it has or what it labels, so translators guess and developers answer the same questions again.
Best fit
Product, design and localization teams whose translators and reviewers work from key names and source text alone.
How ReRune helps
Screenshots live next to the keys in ReRune: each key shows the screens it appears on in its Design tab, and the key list filters by screen.
Visual context
The screen behind every key
Members with the Edit keys permission add screenshots in the dashboard, without Figma. Everyone in the project's organisation can see them.
Mark where each key appears
Draw an area for each key on the screenshot, up to 20 per key for a label that repeats. Opening the key highlights its areas, and the Screens filter lists the keys of one or more screenshots.
Replace the image, keep the marks
Replace image swaps the picture and keeps the screenshot. Every key comes back as a draft at the same place, scaled to the new image, for you to confirm or move.
Screenshots from Figma
The ReRune plugin for Figma, coming soon to Figma Community, will upload a screenshot of each frame it pushes, with every linked layer marked, and ReRune will flag screenshots whose text is out of date.
Workflow
From app copy to release-ready localization.
ReRune connects translation management to the delivery path developers already use: dashboard work, AI assistance, CLI/API sync, and OTA updates where a supported SDK is installed.
Collect product text
Manage keys, languages, values, placeholders, glossaries, metadata, and project context before translation work spreads across files and messages.
Translate with context
Use DeepL or OpenRouter-assisted translation flows with glossary terms and product context close to the text being reviewed.
Sync through developers
Use CLI/API workflows to move approved translations into repositories, CI/CD jobs, scripted release tasks, or custom platform integrations.
Deliver safely
Export platform formats or publish OTA updates for supported SDKs while keeping bundled app resources as the safe fallback.
Setup WizardAI Coding Agent
One command. A wizard sets the stage, your AI agent ships it.
Run the onboarding command from the root of your Git repository. The wizard inspects the app and confirms the plan with you, with no AI involved and nothing changed yet. Then it opens the coding agent you already use with a complete migration workflow.
Run inside your Git repository
curl -fsSL https://rerune.io/onboard.sh | shThe script runs locally. ReRune does not receive your source code or list of installed agents.
Coding agent integrations
11 integrations: 4 available now, 7 planned.
- Claude CodeReady
- CodexReady
OpenCodeReady
PiReady- GitHub Copilot CLIPlanned
- GoosePlanned
- Qwen CodePlanned
- Cursor AgentPlanned
- Kiro CLIPlanned
- Cline CLIPlanned
- Factory DroidPlanned
Coverage
App-first does not mean mobile-only.
Start where localization creates release friction, then keep web, mobile, and cross-platform products in one shared workspace as your surface area grows.
- Web apps and browser-based products
- React web apps with the public OTA SDK
- Angular apps with ngx-translate or Transloco
- React Native apps with the public OTA SDK
- Flutter apps with the public OTA SDK
- Native Android apps with the public OTA SDK
- Native iOS apps with the public OTA SDK
- Compose Multiplatform apps with the public OTA SDK
Developer delivery
Sync through the CLI. Publish through OTA SDKs.
Use the ReRune CLI locally or in CI/CD to manage project translations, then deliver approved runtime updates through the SDK built for your app.
Companion CLI
Install the ReRune CLI
Use the ReRune CLI to sync, validate, and manage translations right from your terminal. Run syncs in CI/CD or locally whenever you need to push a new language.
Homebrew (macOS/Linux):
brew install BasalBit/tap/rerune- Downloadable builds for macOS, Linux, and Windows
- Uses the API keys you generate in the dashboard
- Fits scripted CI/CD workflows through CLI and API access
reruneConnect the project
Create the project config and connect the repository to its ReRune workspace.
rerune pullPull approved updates
Bring current dashboard translations into the app or its build workflow.
rerune pushPush local changes
Send local translation updates back to ReRune for the team to manage and publish.
SDK directory
Use the current public SDK for each product surface.
Public ReRune SDKs for Flutter, Android, iOS, Kotlin Multiplatform, React, React Native, and Angular support runtime variant selection with Main and bundled fallback.
rerune on pub.devReRune Android on Maven CentralReRune iOS on Swift Package IndexReRune Kotlin Multiplatform on Maven Central@rerune/react on npm@rerune/react-native on npm@rerune/angular on npmngx-translate example appTransloco example app
Flutter rerune ^1.9.1
Android rerune-android-compose:1.8.0
rerune-android-views:1.8.0
iOS ReRune 1.7.0
KMP rerune-kmp-compose:1.0.0
React @rerune/react@1.9.0
React Native @rerune/react-native@1.9.0
Angular @rerune/angular@1.9.0Questions
Questions teams ask before choosing a localization platform.
Contact the ReRune team
Share an idea, report a problem, or ask for help with ReRune.
Do I need Figma to add screenshots?
No. Members with the Edit keys permission upload screenshots in the dashboard: choose Upload screenshot in the Gallery, drop or paste an image there, or choose Add screenshot in a key's Design tab. The ReRune plugin for Figma, coming soon to Figma Community, will add screenshots of design frames.
Which images can I upload?
PNG, JPEG and WebP work in every browser, and HEIC where the browser can open it. ReRune removes the image's metadata and makes it smaller when needed, to at most 4096 pixels on the long side and 2 MB. Each screenshot needs a name.
Who can see the screenshots?
Every member of the project's organisation. Screenshots are stored by bunny.net in Germany and shown through signed links that expire. Capture screens with test accounts and sample data rather than real customer details.
What happens to the marks when a screen changes?
Replace image keeps the screenshot and brings every key back as a draft at the same place, scaled to the new image: confirm it, move it, or mark it as not on this screenshot. Deleting a key removes it from every screenshot, and a screenshot without keys stays in the Gallery until someone deletes it.
Explore next
Keep exploring the localization workflow.
Go deeper into the developer, platform, and delivery workflows connected to this page.
A translation management system for copy you control.
A translation management system for app copy you control. Keep source text, translations, and variants with team permissions, and publish as a separate step.
AI translation management that stays accountable to product context.
Use ReRune for AI translation management with project context, glossaries, DeepL and OpenRouter assistance, review controls, and developer sync.
A translation workflow with assignments, approval and a separate publish step.
Assign translation keys to teammates with work packages, set due days, add an optional approver, and keep publishing a separate permission in ReRune.
One workspace
Start with one product workflow and expand from there.
Create projects, manage keys, use AI assistance with context, sync through CLI/API, and publish approved runtime updates when your app uses a supported ReRune SDK.
