Upgrade toQuasar v2and use Vue.js 3
App Internationalization (I18n)

Internationalization is a design process that ensures a product (a website or application) can be adapted to various languages and regions without requiring engineering changes to the source code. Think of internationalization as readiness for localization.


The recommended package for handling website/app is vue-i18n. This package should be added through a Boot File. On the Boot File documentation page you can see a specific example for plugging in vue-i18n.

Setup manually

If you missed enabling i18n during yarn create quasar/npm init quasar wizard, here is how you can set it up manually.

  1. Install the vue-i18n dependency into your app.
$ yarn add vue-i18n
// or:
$ npm install vue-i18n
  1. Create a file src/boot/i18n.js with following content:
import Vue from 'vue'
import VueI18n from 'vue-i18n'

import messages from 'src/i18n'


const i18n = new VueI18n({
  locale: 'en-us',
  fallbackLocale: 'en-us',

export default ({ app }) => {
  // Set i18n instance on app
  app.i18n = i18n

// if you need to import it from
// other files, then:
export { i18n }
  1. Create a folder (/src/i18n/) in your app which will hold the definitions for each language that you’ll support. Example: src/i18n. Notice the “import messages from ‘src/i18n’” from step 2. This is step where you write the content that gets imported.

  2. Now reference this file in quasar.config.js in the boot section:

// quasar.conf.js
return {
  boot: [
    // ...

  // ...

Now you are ready to use it in your pages.

Setting up Translation Blocks in your SFCs

To use embedded <i18n> template components in your vue files with vue-i18n-loader you must ensure that the @intlify/vue-i18n-loader and yaml-loader dependencies are added to your project using your package manager of choice. Then in your quasar.conf.js file change the webpack build options. In this case the translations are stored in yaml format in the block.

// quasar.conf.js
build: {
  // OR use the equivalent chainWebpack()
  // with its own chain statements (CLI v0.16.2+)
  extendWebpack (cfg) {
      resourceQuery: /blockType=i18n/,
      type: 'javascript/auto',
      use: [
        { loader: '@kazupon/vue-i18n-loader' },
        { loader: 'yaml-loader' }

How to use

There are 3 main cases:

    <q-btn :label="$t('mykey2')">
    {{ $t('mykey1') }}
    <span v-html="content"></span>

export default {
  data() {
    return {
      content: this.$t('mykey3')
  1. mykey1 in HTML body
  2. mykey2 in attribute
  3. mykey3 programmatically

Add new language

Let’s say you want to add new German language.

  1. Create the new file src/i18n/de/index.js and copy there the content of the file src/i18n/en-us/index.js then make changes to the language strings.
  2. Now change src/i18n/index.js and add the new de language there.
import enUS from './en-us'
import de from './de'

export default {
  'en-us': enUS,
  de: de

Create language switcher

<!-- some .vue file -->

  <!-- ...... -->
    label="Quasar Language"
    style="min-width: 150px"
  <!-- ...... -->

export default {
  data() {
    return {
      lang: this.$i18n.locale,
      langOptions: [
        { value: 'en-us', label: 'English' },
        { value: 'de', label: 'German' }
  watch: {
    lang(lang) {
      this.$i18n.locale = lang


Many languages, such as Greek, German and Dutch have non-intuitive rules for uppercase display, and there is an edge case that you should be aware of:

QBtn component will use the CSS text-transform: uppercase rule to automatically turn its label into all-caps. According to the MDN webdocs, “The language is defined by the lang HTML attribute or the xml:lang XML attribute.” Unfortunately, this has spotty implementation across browsers, and the 2017 ISO standard for the uppercase German eszett ß has not really entered the canon. At the moment you have two options:

  1. use the prop no-caps in your label and write the string as it should appear
  2. use the prop no-caps in your label and rewrite the string with toLocaleUpperCase by using the locale as detected by this.$q.lang.getLocale()

Detecting Locale

There’s also a method to determine user locale which is supplied by Quasar out of the box:

// outside of a Vue file

// for when you don't specify quasar.conf > framework: 'all'
import { Quasar } from 'quasar'
import Quasar from 'quasar'

Quasar.lang.getLocale() // returns a string

// inside of a Vue file
this.$q.lang.getLocale() // returns a string


If you use Quasar’s set method (this.$q.lang.set()), this will not be reflected by Quasar’s getLocale above. The reason for this is that getLocale() will always return the users locale (based on browser settings). The set() method refers to Quasars internal locale setting which is used to determine which language file to use. If you would like to see which language has been set using set() you can use this.$q.lang.isoName.