Reference
Features
Every feature Mergua offers, field by field, with a link onward to the page that documents it.
Still deciding whether Mergua fits? /features walks through the same ground as a tour, starting with branches.
Take the tour →Editing & Translation
Translation Editor
A side-by-side editor showing source text and translation. Supports three view modes (panel, inline, table), keyboard navigation, search, and status filters. On a phone it is the inline view — source over translation, full width — with the key tree a drawer. Includes character count tracking and placeholder validation.
Learn more →AI Translation
Translate individual keys or batch-translate all missing translations with AI. Results are saved as drafts for human review.
Learn more →Translation Memory
When editing a translation, Mergua shows similar translations from your project. Click to insert — great for keeping terminology consistent.
Translation History
Full audit trail of every change. See who translated, reviewed, or modified a key — with timestamps and the ability to restore previous values.
Collaboration
Branches
Work on translations in isolation with feature branches. Create branches from main, make changes, review diffs, and merge back — just like Git.
Learn more →Review Workflow
Translations go through Draft → Translated → Reviewed states. Reviewers can approve or reject with comments. Optionally require approval before merging branches.
Learn more →Review Overview
One page across every project: branches waiting for your review, your own values a reviewer sent back, and comments that mentioned you. Longest wait first, and the count beside it in the header. Two things also reach you by email — a branch sent for review, and the mentions you have not read, collected rather than sent one per mention. Switch both off in Settings or from the link in the email itself.
Learn more →Team Management
Invite team members by email. Assign roles — Owner, Translator, or Viewer — to control access levels across your organization.
Learn more →Integration & API
Multiple JSON Files per Language
Keep the split your framework already uses — common.json, errors.json, one per area. A project setting decides whether it holds one file per language or several; imports carry the file names in, the editor filters and groups by file, and downloads come back in the same shape. Files can be renamed, merged and deleted. Called a namespace by the CLI and the API.
Learn more →Import & Export
Upload JSON files (flat or nested) to import keys and translations. Download individual locales or all at once as a ZIP archive.
Learn more →Pipeline Sync
Integrate Mergua into your CI/CD pipeline. Translations are automatically pulled into your project on every build, with branch-aware matching.
Learn more →Webhooks
One outbound URL per project. Mergua POSTs to it when translations change or a branch is merged, filtered to one branch — main unless you change it. Every delivery carries an HMAC-SHA256 signature over the raw body, and a burst of writes coalesces into one delivery per language and file rather than one per key. The payload names what changed, never the text itself. A failed delivery is not sent again.
Learn more →API Keys
Generate project-scoped API keys for programmatic access. Use them in CI/CD pipelines or custom integrations to pull translations via the REST API.
Learn more →Account
Plans & Billing
Start free, upgrade when your team grows. Per-seat pricing with monthly billing via Stripe. Branches, API access, and review workflow available on paid plans.
Learn more →FAQ
Answers to common questions about Mergua — from getting started and branches to Pipeline Sync and billing.
Learn more →