Free editor for .xcstrings, plus repo-based Android support
Clean up localization files before release week gets messy.
Review and edit .xcstrings in one place, then search, filter, and manage languages without spreadsheet cleanup. If you connect source control, the same editor also works with Android strings.xml and keeps changes reviewable in your repo.
Try one added language free on your first project • no credit card required
free trial
1 added language
formats
.xcstrings · repo strings.xml
workflow
Search + edit
> What The Editor Helps You Do
Teams reach for the editor when they want fewer translation handoffs, faster string review, and a cleaner path from localization work back into release prep.
inspect_native_files()
See the strings table your team actually ships.
Open .xcstrings directly, and use the same editor for Android strings.xml when the project is connected to source control.
review_rows_fast()
Search, filter, and fix copy faster.
Work through keys, localized values, comments, states, and quality signals without bouncing between exports.
add_languages()
Add a language without rebuilding the workflow.
Start with one added language free, then manage new locales from the same project instead of setting up side scripts.
> How Teams Use It
The workflow stays simple on purpose: start from the right project type, review what matters, and send cleaner localization back into the release process.
step_01
Start with .xcstrings or connect your repo
Manual upload projects accept .xcstrings, while source control projects also detect Android strings.xml files.
step_02
Review the rows that actually need attention
Use search, state filters, comments, and optional quality signals to focus on the strings that changed or still need work.
step_03
Send changes back through the right path
Manual projects let you download updated files, and repository projects can write normalized output and open pull requests.
> Key Capabilities
These are the practical reasons teams keep using the editor once they run it on real files instead of sample data.
format_support()
XCStrings first, Android in repo projects
Start with .xcstrings uploads today and use the same editor for Android strings.xml when source control is connected.
search_filters()
Search and filter by what changed
Find keys, values, states, and quality buckets faster when you are narrowing in on a localization problem.
edit_strings()
Edit translations, notes, and state inline
Update localized copy, comments, and workflow state from the editor instead of round-tripping through another file view.
manage_languages()
Manage languages from the same project
Add or remove locales without rebuilding project setup or inventing a separate onboarding flow.
repo_ready()
Reviewable output for repo projects
Repository projects write normalized files and can open pull requests instead of leaving localization changes stranded in a side tool.
quality_signals()
Quality signals when enabled
On plans that include quality checks, filter by pending, needs review, and ready rows so review time goes where it matters.
> Start With One Free Language
Try the editor on a real .xcstrings file, or connect source control when you want the same workflow for Android strings.xml and reviewable repo output.