UI strings & navigation
Menus, labels, tooltips, modals, settings, forms, buttons and empty states across your product.
Translate the interface without breaking the experience. We localize SaaS platforms, software UI, structured strings, onboarding, errors and help content, with terminology, placeholders and release requirements in mind.
Target file · French
{ "button.save": "Enregistrer", "nav.settings": "Paramètres", "error.required": "Ce champ est obligatoire", "plan.active": "Offre actuelle : {plan_name}"}Words such as “Save” or “Plan” only make sense in context. The translation should fit your interface, audience and user journey.
Menus, labels, tooltips, modals, settings, forms, buttons and empty states across your product.
Dashboards, account areas, onboarding flows, permissions, subscriptions and product features.
Warnings, recovery messages, confirmations and validation copy that users need to understand.
In-product help, knowledge bases, setup instructions, release notes and support articles.
Approved feature names, subscription labels and recurring terms kept consistent across screens.
Resource files with translatable values alongside technical keys, tags, variables and identifiers.
Software localization is not plain text translation. The brief identifies what should change, what must stay intact and where your product needs additional context.
Translation work distinguishes software keys and resource identifiers from user-facing values.
Dynamic names, numbers and parameters are identified so their placement remains meaningful.
Screen context and interface constraints inform short labels, buttons and message length.
Glossaries and approved translations can be reused across content batches and versions.
File structures and technical compatibility are reviewed from the source files before a project is confirmed.
Send the export your team actually works with. We review translatable fields, variables, tags, structure and the return format before scoping the project.
For a complex file or custom format, share a representative sample. We’ll confirm what can be supported and whether any file preparation or engineering work is needed.
Check compatibility with our team ↗JSON / XMLStructured localization values, resource keys and tagged content.XLIFFExchange files with segments, IDs and relevant metadata.CSV / XLSXString exports with source text, context and review columns.RESOURCESPlatform-specific string tables and language packs for review.HELP FILESSupport articles, product guidance and release documentation.One batch or an ongoing release cycle: the workflow is agreed around your content, file formats and deadlines.
Share source strings, target languages, screenshots, a glossary and your delivery needs.
We identify translatable text, technical elements, formatting and the expected return structure.
Interface and product copy are localized using the approved brief and relevant terminology.
Agreed linguistic and file checks are completed before files are returned for your own product testing.
The right screens and release requirements help us understand short strings, variables and feature terminology before localization starts.
The existing starting rates are shown below. A final quote depends on language pair, volume, technical complexity, review requirements and deadline.
These are starting per-word rates, not guaranteed project totals. Please send the source files for an accurate quote.
For suitable content batches where an AI-supported workflow with human review fits the source material and brief.
Check suitabilityFor UI strings and SaaS content needing natural wording, product terminology and context-sensitive human localization.
Order software localizationFor terminology-heavy releases or projects requiring additional specialist handling and technical review.
Discuss complexityAdditional engineering, testing or formatting requirements are scoped separately where relevant.
We’ll review your actual file structure, target languages and interface context before confirming the workflow.
Ask a project questionSoftware localization adapts user-facing product content for another language and market. It can cover interface strings, onboarding, errors, help content and resource files, with product context and technical requirements considered.
Yes. Projects can include dashboards, billing screens, account areas, notifications, settings, forms, onboarding and associated help content.
We can review JSON, XML, CSV, XLSX, XLIFF and platform-specific string files. Send a sample so we can confirm technical suitability, translatable values and the required return format.
We review resource-file conventions and identify identifiers, tags and dynamic placeholders separately from text intended for users. Any technical or linguistic QA requirements are defined in the project brief.
Software localization covers broader SaaS, web and desktop product interfaces. For mobile-app screens, mobile onboarding, notifications and app-store content, use our dedicated App Localization service.
Current starting rates on this page are £0.08 per word for suitable AI-supported work with human review, £0.12 per word for human software localization and £0.16 per word for specialist or complex content. We confirm the final quote after reviewing the files and requirements.
Share your source files, target languages, screenshots and deadlines. We'll review the scope, confirm the delivery format and advise on the appropriate localization workflow.