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.

Plural support

Tolgee supports pluralization in all the known languages. Plurals are visualized in the UI, so you won't get lost while editing them.

Native SDK

Develop localized apps fast, delegate localization to non-developers and provide context to (machine) translators to get reliable results.

CLI

Automate your workflows with the CLI. Push or pull localization data, tag keys, or extract data from the code.

Placeholders & HTML

No more confused translators with specific placeholder and markup syntax. Placeholders and HTML tags are visualized in the Tolgee Platform.

Open-source & self-hosted

Tolgee is open-source and can be self-hosted. Keep your data safe if your policies require it.

Cross-platform

Reuse the same strings on mobile, web or backend. What's stored in Tolgee can be exported to any supported format.

AI Translator

Get reliable results from the Tolgee AI translator. It uses all the data possible to provide the best results.

Simple & Delightful UI

Tolgee's UI is so simple that you won't get lost in it. We prioritize delightful and clean UI when we design any feature.

REST API

Use REST API to automate your processes. Anything you can do in the UI can be done using the REST API.

Plural support

Tolgee supports pluralization in all the known languages. Plurals are visualized in the UI, so you won't get lost while editing them.

Native SDK

Develop localized apps fast, delegate localization to non-developers and provide context to (machine) translators to get reliable results.

CLI

Automate your workflows with the CLI. Push or pull localization data, tag keys, or extract data from the code.

Do it your way

Tolgee native SDK

Tolgee native SDK provide the best developer and translator experience. Enhance in-context editing, context extraction or one-click screenshot generation.

TOLGEE CLI

Import & Export via UI

REST API & Webhooks

QuickFit app

Workouts that fit your schedule, goals, and lifestyle.

Workouts that fit your schedule, goals, and lifestyle.

Quick translation

Homepage-subtitle

Workouts that fit your schedule, goals...

Entrenamientos que se adaptan a tu…

Tolgee native SDK

Tolgee native SDK provide the best developer and translator experience. Enhance in-context editing, context extraction or one-click screenshot generation.

TOLGEE CLI

Import & Export via UI

REST API & Webhooks

QuickFit app

Workouts that fit your schedule, goals, and lifestyle.

Workouts that fit your schedule, goals, and lifestyle.

Quick translation

Homepage-subtitle

Workouts that fit your schedule, goals...

Entrenamientos que se adaptan a tu…

Tolgee native SDK

Tolgee native SDK provide the best developer and translator experience. Enhance in-context editing, context extraction or one-click screenshot generation.

TOLGEE CLI

Import & Export via UI

REST API & Webhooks

QuickFit app

Workouts that fit your schedule, goals, and lifestyle.

Workouts that fit your schedule, goals, and lifestyle.

Quick translation

Homepage-subtitle

Workouts that fit...

Entrenamientos que...

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.

How can I handle plurals?

We recommend using the ICU message format for pluralization. It enables you to render the correct plural forms in every known language.


E.g.

{dogsCount, plural,
  one {Je tu jeden pes}
  few {Jsou tu # psi}
  other {Je tu # psů}}


The `few` variant in the example above is not required in English. However, in the Czech language, providing this form is necessary to display a grammatically correct string for any number.

ICU message format handles this for you.

Tolgee Platform visualizes plurals so users, like translators, do not have to face the ICU syntax.

Tolgee Platform can export visualized plurals to various file formats supporting pluralization, like .po, Ruby .yaml or i18next.

How can I handle plurals?

We recommend using the ICU message format for pluralization. It enables you to render the correct plural forms in every known language.


E.g.

{dogsCount, plural,
  one {Je tu jeden pes}
  few {Jsou tu # psi}
  other {Je tu # psů}}


The `few` variant in the example above is not required in English. However, in the Czech language, providing this form is necessary to display a grammatically correct string for any number.

ICU message format handles this for you.

Tolgee Platform visualizes plurals so users, like translators, do not have to face the ICU syntax.

Tolgee Platform can export visualized plurals to various file formats supporting pluralization, like .po, Ruby .yaml or i18next.

Which machine translation providers are supported?

Tolgee currently supports

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

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.

Do you offer a completely free cloud plan?

Absolutely! When you sign up for Tolgee, you will automatically receive our Free plan, which is limited by the number of keys, seats and MT credits.

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.