Translate the text content within XML tags into your target language while preserving all XML structure, tags, attributes, and formatting intact.
XML translation means converting the human-readable text content inside XML elements into another language without altering the underlying markup. Tags, attributes, CDATA sections, comments, and entity references all stay exactly as they are — only the translatable string values change. This is essential for localizing Android string XML files, configuration files, XLIFF documents, and any XML-based content.
Paste your XML content into the input field, select your target language and any formatting preferences, and the translator processes each text node individually. It understands XML structure, so it won't break your nesting, won't translate attribute names or tag names, and will keep placeholders like %s, %d, or {0} untouched. The output is valid, well-formed XML ready to drop into your project.
Developers working with Android strings.xml files use this to quickly generate localized versions. Game modders translating XML lore files or dialogue trees can process entire files at once. Technical writers localizing documentation stored in XML or DITA formats benefit from structure-aware translation that respects inline markup. It also works well for translating XML-based API responses, RSS feeds, and configuration files that contain user-facing strings.
<resources> <string name="app_name">My Application</string> <string name="welcome_message">Welcome back, %s!</string> <string name="items_count">You have %d items in your cart</string> <string name="logout">Log out</string> </resources>
<resources> <string name="app_name">Mi Aplicación</string> <string name="welcome_message">¡Bienvenido de nuevo, %s!</string> <string name="items_count">Tienes %d artículos en tu carrito</string> <string name="logout">Cerrar sesión</string> </resources>
<menu> <item id="file">File</item> <item id="edit">Edit</item> <item id="view">View</item> <item id="help">Help</item> </menu>
<menu> <item id="file">Archivo</item> <item id="edit">Editar</item> <item id="view">Ver</item> <item id="help">Ayuda</item> </menu>
<messages> <error code="404">Page not found. Please check the URL and try again.</error> <error code="500">Something went wrong on our end. Please try again later.</error> <success code="200">Your changes have been saved successfully.</success> </messages>
<messages> <error code="404">Página no encontrada. Por favor, verifica la URL e inténtalo de nuevo.</error> <error code="500">Algo salió mal de nuestro lado. Por favor, inténtalo más tarde.</error> <success code="200">Tus cambios se han guardado correctamente.</success> </messages>
<resources> <string name="greeting">Hello, {username}! You have {count} new notifications.</string> <string-array name="days"> <item>Monday</item> <item>Tuesday</item> <item>Wednesday</item> </string-array> </resources>
<resources> <string name="greeting">¡Hola, {username}! Tienes {count} notificaciones nuevas.</string> <string-array name="days"> <item>Lunes</item> <item>Martes</item> <item>Miércoles</item> </string-array> </resources>
No. Only the text content inside elements is translated. All tag names, attribute values (like IDs and keys), nesting structure, comments, and CDATA sections remain exactly as they are in the original.
Placeholders are preserved as-is in the translated output. Format specifiers (%s, %d, %1$s), curly brace variables ({name}, {count}), and other common placeholder patterns pass through untouched so your string interpolation continues to work correctly.
Yes. Select the "Android strings.xml" content type and the translator will correctly handle
XML entities like &, <, >, and ' are preserved correctly. The output remains valid, well-formed XML that you can use directly without additional escaping or cleanup.
The translator processes all text content in the XML you provide. If you only want certain elements translated, paste just those elements rather than the full file. You can then merge the translated portions back into your original file.
Comments