Configuring a module

Last updated:

When creating a module, there are a number of options available that impact where a module is visible, how it's identified, and how it can be edited.

When developing locally, modules are stored as folders with a .module suffix. These folders contain the files that make up the module's settings and the code used to render it. A module's configuration is kept in the meta.json file, while fields are configured separately in a fields.json file.

Most configuration can also be modified using the module editor in the Design Manager

Module folder structure displayed locally

At a high level, you configure module options locally within the meta.json file, which can include the following properties:

ParameterTypeDescription Default

URL to an image to use as the icon for a module.


Label used when modules are shown in the content editors


Unique id for the module that is independent from the path.


The value for the toggle in the top right corner of the module editor in HubSpot. Determines if the module can be used in content.


Indicates whether the module is global or not


An array of content types that the module can be used within. One or more of:

  • ANY: any of the types listed below.
  • LANDING_PAGE: landing pages.
  • SITE_PAGE: website pages and templates.
  • BLOG_POST: blog posts and templates.
  • BLOG_LISTING: blog listing templates.
  • EMAIL: emails and email templates.
  • KNOWLEDGE_BASE: knowledge base pages and templates.
  • QUOTE_TEMPLATE: quote templates.
  • CUSTOMER_PORTAL: customer portal templates.
  • WEB_INTERACTIVE: web interactives.
  • SUBSCRIPTION: subscription templates.
  • MEMBERSHIP: membership templates.

If a module is not to be used in any area within HubSpot, you would set the value to an empty array [] instead of ["NONE"].

Note that this field was previously named host_template_types. Modules using the previous field name will continue to function, but it's recommended to use content_types moving forward.


An array of CSS files that the module depends on. Supports relative paths.

e.g. "css_assets": [{ "path": "../path/to/file.css" }]


Set whether the module CSS renders asynchronously with async: true, false 

{"async": false}

An array of JavaScript files that the module depends on. Supports relative paths.

e.g. "js_assets": [{ "path": "../path/to/file.js" }]


Modifies the module JavaScript tag added to the rendered page. Options include:

  • position: head , footer
  • async: true, false
  • defer: true, false
  • type: string

Help text that will be shown at the top of the module in a blue info box (limit 300 characters).

Provides information necessary to use the module. If you have field-specific help text information to convey, refer to the help text field documentation.


With translations enabled, the language code of the language the module's fields were originally written in.

e.g. en


Sets placeholder content for the module. Includes the following properties:

  • show_module_icon: whether the module icon displays. true, false.
  • title: the title that appears on the module in the editor. String.
  • description: the description that appears on the module in the editor. String.

An array containing up to three module categories.

For example: 


An array of module tag objects containing the tag name and source of "USER".

For example: 

"content_tags": [{
 "name" : "BUTTONS",
 "source" : "USER"

Below, learn more about individual module configuration options.

Adding an Icon

Modules can include an icon that appears in the Design Manager and the page and email editors to provide visual context for content creators. It's recommended to have different icons for the different types of modules in your theme. Icons are required for marketplace providers.

There are two ways to add an icon, through the design manager or the CMS CLI.

Module icons must be an .svg file and no larger in size than 10kb. For best results your icon should be simple and use only one color. Icons that use more than one color will be automatically converted for you. The default module icon that displays is a wrench and paint brush icon.

To add an icon using the design manager:

  1. In your HubSpot account, navigate to Marketing > Files and Templates > Design Tools

  2. Use the left sidebar to locate the module you want to edit, then click the module name.
  3. In the right sidebar of the module editor, click the icon next to the module title. 
  4. Upload/select your icon. After publishing your changes, the icon will appear within the page editors and design manager.

To add an icon when developing locally, open the module's meta.json file and add or edit the icon parameter's value to be an SVG from the file manager.

// meta.json { "global": false, "content_types": ["PAGE"], "icon": "", "label": "Code block", "smart_type": "NOT_SMART", "is_available_for_new_content": true, "inline_help_text": "This module is for code snippets." }

Changing the label

The label used when modules are displayed in the editor can be adjusted separately from the name for the module. This is useful when developing locally as you can have a name that makes sense to you while having a different one content creators see.

Locally you change the label parameter to set the label. In the design manager there's a field in the module editor below the module name.


Making a module global

For normal modules, the content of each instance of a module in a page, email or template is independent. For some use cases, it is useful to be able to have all instances of a module share the same content. When developing locally, you can make a module global by setting global to true.  

You can also convert modules in a drag-and-drop template to global using the design manager.

Controlling where a module is available for use

When developing locally, you can control which types of content a module can be used in through the hostTemplateTypes property. Learn more about the available template types. Modules also can be hidden so that they can't be added directly to pages through setting is_available_for_new_content to false. For example, this can be helpful for modules built for navigation menus and search.

You can update this in the design manager by clicking the Template type option in the right sidebar.


Adding CSS and JavaScript dependencies

In addition to using module.css and module.js to add CSS and JavaScript that will be added to all pages that include a module instance, dependencies that are shared between modules can be attached using css_assets and js_assets. Paths can be absolute or relative to the meta.json file.

// meta.json { "css_assets": [{ "path": "../path/to/file.css" }], "js_assets": [{ "path": "../path/to/file.js" }] }

Warning: When using relative paths to reference dependencies, running hs fetch --overwrite to update the module for local development will overwrite the relative paths with absolute paths.

Using the design manager, you can link CSS and JavaScript files to a module using the Linked files section in the right sidebar of the module editor.


Adding categories and tags

You can assign categories and tags to modules to organize them within HubSpot tools:

  • Categories: assign categories to a modules to organize them into groups within the content editor UI. This enables content creators to find modules more easily while building content in HubSpot. Note the following about categories:
    • A module can have up to three categories, which are pre-defined and cannot be customized.
    • Currently, categories are not surfaced in the content editor UI. However, you can assign categories for when categorization is available in editors.
    • Uncategorized modules will be available under an All category.
  • Tags: assign tags to organize modules within the design manager. This enables you to find modules more easily while building templates.

In the design manager, you can assign categories and tags using the Filter tags section of the right sidebar in the module editor. Learn more about the available categories and tags below.


Locally, you can add categories and tags to a module's meta.json file as follows:

// meta.json { "label": "Custom module", "categories": ["image_and_video", "commerce"], "content_tags" : [ { "name" : "BUTTONS", "source" : "USER" }, { "name" : "CTA", "source" : "USER" } ], "is_available_for_new_content": true }


A module's categories array can contain up to three of the following categories (case-insensitive):

Category Description
blog Blog-specific modules, such as a recent post listing.
body_content Modules that are formatted to graphically showcase content, such as an image gallery.
commerce Commerce-specific  modules, such as pricing cards.
design Modules that affect content structure and layout, such as accordions.
functionality Modules that include dynamic responses or behavior on the page, such as menus.
forms_and_buttons Modules that allow site visitors to input and submit data.
media Modules that contain elements such as images, icons, video, and banners.
social Social media-specific modules, such as social sharing.
text Modules that contain only text.


A module's content_tags array can contain any of the following module tag objects (case sensitive):

Content types:

  • CODE
  • CTA
  • FEED
  • FORM
  • ICON
  • LOGO
  • MENU
  • TEXT


  • BLOG
  • MAP

Was this article helpful?
This form is used for documentation feedback only. Learn how to get help with HubSpot.