The QIcon component allows you to easily insert icons within other components or any other area of your pages. Quasar currently supports: Material Icons , Font Awesome, Ionicons, MDI, Eva Icons and Themify Icons.

There are multiple types of icons in Quasar: webfont-based, svg-based (v1.7+) and image-based. You are not bound to using only one type in your website/app.


// quasar.conf.js

return {
  framework: {
    // NOT needed if using auto-import feature:
    components: [



If you are using webfont-based icons, make sure that you installed the icon library that you are using, otherwise it won’t show up!

Webfont icons

<q-icon name="..." />
Quasar IconSet nameName prefixExamplesNotes
material-iconsNonethumb_upNotice the underline character instead of dash or space
material-icons-outlinedo_o_thumb_upNotice the underline character instead of dash or space; Requires Quasar 1.0.5+
material-icons-roundr_r_thumb_upNotice the underline character instead of dash or space; Requires Quasar 1.0.5+
material-icons-sharps_s_thumb_upNotice the underline character instead of dash or space; Requires Quasar 1.0.5+
ionicons-v4ion-, ion-md-, ion-ios-, ion-logo-ion-heart, ion-logo-npm, ion-md-airplaneUse QIcon instead of <ion-icon> component; Logo icons require ‘ion-logo-’ prefix
fontawesome-v5fa[s,r,l,b] fa-“fas fa-ambulance”QIcon “name” property is same as “class” attribute value in Fontawesome docs examples (where they show <i> tags)
mdi-v4mdi-mdi-alert-circle-outlineNotice the use of dash characters; Use only one of mdi-v4 or mdi-v3
mdi-v3mdi-mdi-alert-circle-outlineNotice the use of dash characters; Use only one of mdi-v4 or mdi-v3
eva-iconseva-eva-shield-outline, eva-activity-outlineNotice the use of dash characters
themifyti-ti-hand-point-upNotice the use of dash characters

Svg icons

Quasar v1.7.0+
@quasar/extras v1.4+

There are many advantages of using only svg icons in your website/app:

  • Better app footprint – only used icons will be included in the final build (treeshaking in action)
  • Better quality icons
  • No need for including equivalent webfonts from @quasar/extras or CDN.

The current disadvantage is that it is more tedious to use these icons than their webfont counterpart.

Notice in the example below that we want to avoid Vue observable wrapping, so we inject icons on the instance through created() hook. It will work if declared in data() too, but… overhead.

    <q-icon :name="matMenu" />
    <q-icon :name="fasFont" />
    <q-btn :icon="mdiAbTesting" />

import { matMenu } from '@quasar/extras/material-icons'
import { mdiAbTesting } from '@quasar/extras/mdi-v4'
import { fasFont } from '@quasar/extras/fontawesome-v5'

export default {
  // ...
  created () {
    this.matMenu = matMenu
    this.mdiAbTesting = mdiAbTesting
    this.fasFont = fasFont


If you are only using svg icons (and have configured a Quasar Icon Set) then you don’t need the webfont equivalent in your app at all.

VendorQuasar IconSet nameImport Icons from
Material Icons (Google)svg-material-icons@quasar/extras/material-icons
MDI (Material Design Icons)svg-mdi-v4@quasar/extras/mdi-v4
Font Awesomesvg-fontawesome-v5@quasar/extras/fontawesome-v5
Eva Iconssvg-eva-icons@quasar/extras/eva-icons
Themify Iconssvg-themify@quasar/extras/themify

You can also supply your own svg icons. An svg icon is essentially a String with the following syntax:

Syntax: "<path>|<viewBox>" or "<path>" (with implicit 0 0 24 24 viewBox)
  M9 3L5 6.99h3V14h2V6.99h3L9 3zm7 14.01V10h-2v7.01h-3L15 21l4-3.99h-3z|0 0 104 104
  M9 3L5 6.99h3V14h2V6.99h3L9 3zm7 14.01V10h-2v7.01h-3L15 21l4-3.99h-3z

// equivalent to the original svg:
<svg viewBox="0 0 104 104">
  <path d="M9 3L5 6.99h3V....."/>

Inlined svg


QIcon can contain one <svg> tag (the content of the svg can be anything, not only a path).

Reasoning on why to use an <svg> in a QIcon is that the svg will respect the size and color as any QIcon through its props. Without these features, you’re better off inlining the svg in your templates without QIcon.

<q-icon color="accent" size="5rem">
  <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
    <path d="M0 0h24v24H0z" fill="none"/>
    <path d="M19 3h-4.18C14.4 1.84 13.3 1 12 1c-1.3 0-2.4.84-2.82 2H5c-1.1 0-2 .9-2 2v14c0 1.1.9 2 2 2h14c1.1 0 2-.9 2-2V5c0-1.1-.9-2-2-2zm-7 0c.55 0 1 .45 1 1s-.45 1-1 1-1-.45-1-1 .45-1 1-1zm0 4c1.66 0 3 1.34 3 3s-1.34 3-3 3-3-1.34-3-3 1.34-3 3-3zm6 12H6v-1.4c0-2 4-3.1 6-3.1s6 1.1 6 3.1V19z"/>

Some limitations:

  • do not use “height”/“width” attributes on the <svg> tag (it will brake QIcon’s way of handling the size)
  • all <path>s will have “fill: currentColor” CSS applied by default; if you don’t want that, then add fill="none" to the <path> tag

Image icons

You can also make an icon point to an image URL instead of relying on any webfont, by using the img: prefix.

All icon related props of Quasar components can make use of this.

<q-icon name="img:https://cdn.quasar.dev/logo/svg/quasar-logo.svg" />
<q-btn icon="img:https://cdn.quasar.dev/logo/svg/quasar-logo.svg" ... />
<q-icon name="img:statics/my/path/to/some.svg" />


Remember that you can place images in your /src/statics folder too and point to them. You don’t always need a full URL.

This is not restricted to SVG only. You can use whatever image type you want (png, jpg, …):

<q-icon name="img:statics/bla/bla/my.png" />
<q-btn icon="img:statics/bla/bla/my.jpg" ... />
<q-input clearable clear-icon="img:statics/bla/bla/my.gif" ... />

It is also possible to inline the image (svg, png, jpeg, gif…) and dynamically change its style (svg):

<q-icon name="img:data:image/svg+xml;charset=utf8,<svg xmlns='http://www.w3.org/2000/svg' height='140' width='500'><ellipse cx='200' cy='80' rx='100' ry='50' style='fill:yellow;stroke:purple;stroke-width:2' /></svg>" />
Dynamic SVG

You can also base64 encode an image and supply it. The example below is with a QBtn, but the same principle is involved when dealing with any icon prop or with QIcon:

<q-btn icon="

Size & colors

All icons are webfont icons. This means that you can change size by manipulating font-size CSS property. And also, they inherit the current CSS text color used.


For icon properties on different Quasar components you won’t have the means to specify an icon for each platform, but you can achieve the same effect with:

  :icon="$q.platform.is.ios ? 'settings' : 'ion-ios-gear-outline'"
Standard sizes

Custom mapping


Should you want, you can customize the mapping of icon names. This can be done by overriding $q.iconMapFn. The recommended place to do it is in the created() hook of your /src/App.vue component.

The syntax for $q.iconMapFn is as follows:

/* Syntax */
iconMapFn (String: iconName) => Object / void 0 (undefined)

 The returned Object (if any) must be one of the following forms:

 1. Defines how to interpret icon
   cls: String // class name(s)
   content: String // optional, in case you are using a ligature font
                   // and you need it as content of the QIcon

  2. Acts essentially as a map to another icon
    icon: String // the mapped icon String, which will be handled
                 // by Quasar as if the original QIcon name was this value

Let’s take both cases now.

1. Support for custom icon library

This is especially useful when you are using a custom icon library (that doesn’t come with Quasar and its @quasar/extras package).

created () {
  // Example of adding support for
  // <q-icon name="app:...." />
  // This includes support for all "icon" props
  // of Quasar components

  this.$q.iconMapFn = (iconName) => {
    // iconName is the content of QIcon "name" prop

    // your custom approach, the following
    // is just an example:
    if (iconName.startsWith('app:') === true) {
      // we strip the "app:" part
      const name = iconName.substring(4)

      return {
        cls: 'my-app-icon ' + name

    // when we don't return anything from our
    // iconMapFn, the default Quasar icon mapping
    // takes over

Notice in the examples above that we are returning a my-app-icon class that gets applied to QIcon if our icon starts with app: prefix. We can use it to define how QIcon should react to it, from a CSS point of view.

Let’s assume we have our own webfont called “My App Icon”.

  For this example, we are creating:

.my-app-icon {
  font-family: 'My App Icon';
  font-weight: 400;

@font-face {
  font-family: 'My App Icon';
  font-style: normal; /* whatever is required for your */
  font-weight: 400;   /* webfont.... */
  src: url("./my-app-icon.woff2") format("woff2"), url("./my-app-icon.woff") format("woff");

We should then edit our quasar.conf.js (if using Quasar CLI) to add the newly created CSS file into our app:

css: [
  // ....

And also add “my-app-icon.woff2” and “my-app-icon.woff” files into the same folder as “my-app-icon.css” (or somewhere else, but edit the relative paths (see “src:” above) to the woff/woff2 files).

2. Simply mapping a few icons

const myIcons = {
  'app:icon1': 'img:/path/to/icon1.svg',
  'app:icon2': 'img:/path/to/icon2.svg',
  'app:copy': 'fas fa-copy',

// ...
created () {
  this.$q.iconMapFn = (iconName) => {
    const icon = myIcons[iconName]
    if (icon !== void 0) {
      return { icon: icon }

Now we can use <q-icon name="app:copy" /> or <q-icon name="app:icon1" /> and QIcon will treat “app:copy” and “app:icon1” as if they were written as “fas fa-copy” and “img:/path/to/icon1.svg”.