English Qlik Sense Developers 2.0

Working with the meta data

The extension metadata file (QEXT) is in fact a JSON file and is used by Qlik Sense to identify the visualization extension and it contains the meta data used for the Library or Assets panel. When deployed to Qlik Sense, the visualization extension is displayed in the Charts section of the Assets panel or Library panel.

The QEXT file extension must be in lower case letters, like in HelloWorld.qext.
Make sure your file meets the requirements of a valid JSON file when creating your QEXT file.

See: JSON validator: http://jsonlint.com

All visualizations must contain at least one QEXT file and one JavaScript file.

The QEXT file extension must be in lower case letters.
The JavaScript file and the QEXT file must have the same name, including matching case. The name must also be unique in the Qlik Sense system so prefixing of the name should be considered. For example: com-qliktech-helloworld.



The following properties can be defined in the QEXT file.


The name property is mandatory.

This is the name of the visualization extension and is displayed in the library as well as in the preview.

It is recommended to use an unique name of the visualization to avoid interference with other visualizations that may have the same name.


The type property is mandatory.

This defines the type of extension. Should always be visualization for visualization extensions.


This defines the description visible in the preview of the visualization extension.


Default is extension.

This defines the icon displayed in the library. Can be:




"line-chart" %














"treemap" »


If preview is undefined, the icon definition will be used.

This defines which preview image to be used. The preview image is displayed in a pop-up when you select the visualization extension in the library.

You can define a custom preview image file. It must be of PNG format. For an example of how this is defined, see the Hello world code example.


"icon": "<CustomImage>.png"


This defines your individual version handling of the visualization extension. This setting is manually defined. Semantic versioning is recommended.


This defines the author of the visualization extension. This setting is manually defined.


Example: Hello world QEXT file

	"name": "Hello World",
	"description": "Hello world example",
  	"preview": "helloworld.png",
	"type": "visualization",
	"version": 1,
	"author": "Qlik International"