Website, app and software translation

Provide string context

Include screenshots, field descriptions and placeholder instructions. Variables, HTML tags and technical keys must be identifiable. Mark content that must remain untranslated.

Plan delivery and review

Agree the file format, length limits, versions and handling of new strings. Reviewing the implemented translation in your interface or publishing it in a CMS requires a separate agreement.

Typical content and situations

• Websites and online stores
• User interfaces and app strings
• Help content and knowledge bases
• Release notes and product copy

Delivery date and project scope

Turnaround depends on the text length, languages and subject area. Send the complete text and your actual deadline so we can confirm a delivery date after review. For ongoing projects, we can agree staged delivery and version handling.

What to include in your enquiry

• Complete source files and required delivery format
• Source and target language, target country or regional variant
• Subject area, audience, glossary and reference material
• Requested delivery date and additional review requirements

Related information

• How much does a professional translation cost?
• How long does translation take?
• Which file formats should I send?
• Explore all services
• All languages and practical guides