Your project, together
Multiple JSON/RESX files, existing target imports, conflict previews and source revisions. Preserve keys and non-string data.
Software localization on Windows
Localize JSON and RESX with their context.
Localize JSON and RESX projects on your Windows PC. Keep the source, context, terminology, corrections and release checks together.
Studio · available in 1.0.21
View public 1.0.21 downloads →Iria Localization Studio
From resource files to a reviewed release.
Localize JSON and RESX projects on your Windows PC. Keep the source, context, terminology, corrections and release checks together.
Studio · available in 1.0.21
/welcome
Source resources
Welcome, {name}!Context from source file
Greeting on the welcome screen; keep {name}.
English → Spanish
¡Bienvenido, {name}!Draft · review required
Translate & prepare review
Translate & export automatically
Context that follows the source
RESX comments become context for new resources. Changed inherited context makes old drafts outdated; differing custom contexts stay yours.
Corrections you can reuse
Exact project memory matches source file, languages, source, context, glossary and access-key format. TMX import and export help move existing work.
Checks before a release
Supported placeholders, markup, ICU/plurals, quantities, glossary terms, length limits and access keys. Proposed keys need your review.
A clearer review workspace
Search and filter resources, compare the previous source, preview ICU branches and numbers, and open a release blocker directly.
A repeatable workflow
Save completed drafts, cancel and resume a batch, watch tracked source files and run project checks through the Windows CLI.
Translate & prepare review
Default: generate drafts and review them before exporting. Your approved corrections become scoped project memory.
Translate & export automatically
Optional: disable the human-review policy to accept current drafts that pass supported checks and export. Imported drafts, ICU obligations and access-key proposals still require explicit review.
Structural checks protect supported resource syntax. They do not certify meaning; review important translations in your application.
A project you can revise
Import resources and existing targets
Keep multiple JSON/RESX files together. Compare conflicts before replacing a translation and retain non-string data.
Add context and terminology
New RESX resources inherit their comment as context. Customize it when needed and set glossary terms, length limits and access-key format.
Translate and review
Human review is the default. Compare the previous source, check ICU branches and approve corrections. Automatic export is an explicit choice.
Check and export the release
Open release blockers and generate a new folder with its report. Compatible projects can use .NET resource filenames.
Synchronize the next revision
Retain current approvals and flag outdated results. The CLI brings checks into your build workflow under the configured Iria license/model setup.
Before you use Studio
Does Studio upload my resource text to a translation provider?
Resource inference runs locally with the installed model. License validation, model downloads and update checks use the network. This is not a claim that the whole application is network-free.
Can I export without approving every translation?
New projects require human approval by default. You can explicitly disable that policy for Translate & export automatically. Supported structural checks remain active; imported drafts, ICU review obligations and access-key proposals can still block export. Automatic acceptance is recorded separately and does not create human correction memory.
What happens when a source string or comment changes?
Source changes make previous drafts outdated. Inherited RESX context follows a changed effective comment; a differing custom context is preserved. A context change revokes approval and excludes old-context automatic memory reuse. Long comments retain their complete source text while translation context is capped at 1,000 UTF-16 units.
Which formats can I use?
Studio works with JSON string resources and RESX string resources, including multiple files. It supports bounded TMX memory interchange. It is not a full-document layout translator, and there is no XLIFF project import claim.
Can I reuse a TMX memory with a JSON or RESX project?
Studio supports limited TMX 1.1, 1.4 and 1.4b import for human translation memory, and plain-text TMX 1.4 export. This is bounded interchange, not full TMX Level 2 support. Supported structural checks do not certify linguistic meaning.
Can the CLI certify translation quality in CI?
The CLI can create, inspect, synchronize, translate, check and export a saved project under the existing license/model setup. A failed check or required review blocks release. These are supported integrity and review gates, not a linguistic quality certificate.
Is Iria proven more accurate or faster than other translators?
No global accuracy or speed claim is made. Translation depends on the language pair, source and local model. Human comparative quality, correction effort and task time remain to be evaluated.