Tolgee for Vue
Translate Vue apps with Tolgee the way you want. Tolgee offers powerful native SDKs with in-context editing, screenshot generation, or context extraction for AI translator. If you prefer to manage the strings another way, Tolgee provides a powerful REST API.
Do it your way
FAQ
How do I add new keys?
You can add new keys in the Tolgee Platform using the Native SDKs, CLI, or REST API. For JavaScript frameworks like React, Angular, Vue, etc, we recommend adding keys using in-context editing, which is part of the Native SDKs.
Which machine translation providers are supported?
Tolgee currently supports
DeepL
Google Translate
Amazon Translate
Microsoft Cognitive
How can product managers, designers or other non-developer team members edit the strings?
Team members who care about precise wording can reliably edit the strings directly inside the product using Tolgee Native SDKs and its in-context editing feature.
Users can open the in-context edition dialog by alt+clicing the string in the development mode app.
Even live production applications can be turned to development mode using the Tolgee Chrome plugin.
Such an edit is very simple and reliable because the user knows what string is edited and that they're not editing a different string. Also, they don't have to search for the string in the source code, localization files, or huge localization data sets.
Is my application dependent on Tolgee Servers?
No. In a production environment, you should not use Tolgee as a source for localization data or leak your API key this way.
Instead, you should use data exported as static assets or Content Delivery (CDN).
How can I export the data for production?
You can export the data
using the Tolgee Platform UI
using the CLI
using the REST API
or you can publish the data to the CDN
Is my API key exposed in the production?
When your app is live in production, there is no need to use the API key. Your app does not fetch data from Tolgee REST API; instead, it fetches data from static assets or Content Delivery (CDN).
You should never leak your API key. That's why developers should store the API keys in environment files (.env) in the .gitignore file.
What formats are supported by Tolgee?
Tolgee supports all significant formats storing localization data such as JSON, XLIFF, .strings, .arb, .po and many more. Read about all supported formats here.
What's the difference between development and production mode?
When running your app in development mode with the Tolgee Native SDKs, localization data are fetched from the Tolgee REST API. You can edit the strings using the in-context tools, generate screenshots or review translations.
On the other hand, in production mode, Tolgee uses static assets or data published to Content Delivery (CDN). In production mode, no one can modify the app's strings unless they provide their API key using the Tolgee Chrome plugin.
Can I use strings created for web app for mobile and other apps?
Yes. When conversion to Tolgee ICU placeholders is enabled, you can reuse the exact data for any supported platform.
For example, you can use data created for web applications for your iOS or Android mobile app and vice versa.
How can I automate exporting data from the Tolgee Platform?
You can use your favorite CI/CD tool, such as GitHub Actions or GitLab CI/CD, while embracing Tolgee CLI's pull command or Tolgee REST API's export endpoint to automate data exporting.
Popular apps & integrations
We support all major JS frameworks. Set it up in minutes and keep working just the way you like - no disruptions, just smooth, hassle-free localization.


