Skip to main content
Add fields to modules and themes to allow content creators to control various aspects of a page within the page editor. Below, learn about all of the fields available for modules and themes, along with their available properties. For more information about implementing module and theme fields, including field groups and repeating fields, view the module and theme fields overview.

Properties used by all fields

All fields share a set of common properties. These are general fields, such as the field’s name or the help text that displays for content creators using the field in the module or theme.

Alignment

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
Enables content creators to position an element within a container. To enable text alignment, use the text alignment field instead.
Alignment field

Background image

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
This field provides a background image field which has subfields for background position and background size. Background image fields have a .css property that returns CSS based on the field’s value. Learn more about the generated CSS property.
Background image field

Blog

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
This field provides a way for content editors to select a blog, providing you, the developer the blog’s ID. This is useful for situations like pulling teaser information for featured blogs in modules. You can use the blog ID in blog-related HubL functions to get information like blog authors, recent blog posts, recent blog posts with a specific tag, and more.
Screenshot of Blog field

Boolean

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules and themes as a style field.
This field provides a way for content editors to enable/disable functionality. Booleans can only be true or false. Often it makes sense to make groups or fields conditional based on boolean fields. If you think you might need to provide more than two states in the future, a choice field may be a better option as you can grow into that with less effort should needs change later.
Screenshot of Boolean field
A toggle switch can make sense when the value of the field enables/disables other fields conditionally being shown. Another time a toggle may be useful is when the field represents a major design change for the module.Checkboxes make sense for smaller changes that may not have as drastic of an effect on the module’s display, such as hiding or showing individual small elements.

Border

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
This field provides content creators a user interface for creating a border around an element. Border fields have a .css property that returns CSS based on the field’s value. Learn more about the generated CSS property.
Screenshot of border module field in page editor

Choice

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules and themes as a style field.
Choice fields allow a content creator to select one or more items from a list of options. Using the display property, you can set display the options in a dropdown menu, radio select, or checkboxes, or a range of buttons. Learn more about choice field display options below.
choice-field-dropdown

Choice button presets

To configure a choice field to display buttons instead of a dropdown menu, checkboxes, or radio selects, you can use any of the presets below. Each preset allows for a specific set of option labels, which you’ll need to include in the choices array. These labels cannot be customized.

Color

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules and themes as a style field.
Color fields provide a color picker interface for content creators. They support solid colors as well as transparency. They are a perfect choice for when you want to give content creators full control over colors within a module. By default, the opacity input of a color field is hidden for email modules, as some email clients don’t respect opacity rules. You can reveal the opacity field for email modules by setting show_opacity to true.
Color field

CTA

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Please note: this field is only available for Content Hub Professional and Enterprise.
Call-To-Action (CTA) fields provide a way for users to pick a CTA to display. CTA’s are essentially trackable buttons or links. Content creators create CTAs that can be used throughout a site.
Call To Action Field

CRM object

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Please note: this field is only available for Content Hub Professional and Enterprise.
CRM object fields provide a way for users to pick an individual instance of a CRM object to display. module.fieldname.properties returns the properties fetched from this object instance. This makes it so you don’t need to use the crm_object() function to get the data for the selected object instance. module.fieldname.id returns the object instance ID.
CRM Object Field

CRM object property

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Please note: this field is only available for Content Hub Professional and Enterprise.
Use the CRM object property field to access property metadata, such as the label and property name, from a specified object type. This enables content creators to select from object properties when needing to display property details on a page. For example, you could add this field to a custom table module to populate table headings based on the selected properties.
crm-object-property-dropdown-menu0
In addition, you can use the following snippets to return other property details:
  • {{ module.fieldname.property }}: returns the property’s internal name.
  • {{ module.fieldname.property_definition.label }}: returns the property’s label.
  • {{ module.fieldname.property_definition.type }}: returns the property type (e.g., string).

Date

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Date fields provide a date picker interface to make it easy for content creators to select a date. Returns a timestamp you can use in your code.
Date field with calendar picker open

Date and time

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Date and time fields provide a date picker interface just like the date field, as well as a time picker to make it easy for content creators to select a date and time of day. Returns a timestamp you can use in your code.
Date and time field

Email Address

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Use this field to allow users to select email addresses associated with users in the account, or enter custom email addresses. For example, this could be useful when building out a Contact us section with an email address option. The email field returns an array of selected email addresses you can loop through.
email-field

Embed

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Embed fields allow the user to add a URL from an oEmbed-enabled site or paste in an embed code from another site. To learn more about oEmbed usage on HubSpot, and see use cases, visit our oEmbed document.
Embed field

File

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
File fields allow the user to upload a file to the file manager, or document manager, and make it easy to attach items that are in those locations. This can be useful for linking out to PDF files or files of other formats. For displaying images on a page you should use the image field.
File field

Followup email

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Please note: this field is being deprecated in favor of attaching followup emails within form fields. Consider removing any followup email fields from this module beforehand. Learn more in the Developer Changelog.
Followup email fields allow a content creator to designate an email that will be sent in response to a form submission. This works in tandem with the HubL form tag, through the simple_email_campaign_id parameter.
followup email field

Font

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules and themes as a style field.
Font fields provide content creators basic font styling controls. Content creators can choose the size, color, font family, and the format (bold, italic, and underlined). The listed fonts are all standard web-safe fonts. These fonts are sourced from Google Fonts, but are served by HubSpot directly on the domain that the page loads on.
Font field
Please note:
  • Font family is determined by the combination of the font and font_set properties. You must include both to load the font. When inheriting fields, this means you need to inherit both values.
  • Hiding CSS-related sub fields with visibility will not prevent that CSS from being output in the styling returned in the field object. You’ll still need to manually include the CSS in the styles object.

Form

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Form fields allow a content creator to designate a form in their account. You can then use this to render a form to a page using the HubL form tag.
form field-Aug-21-2020-08-09-55-35-PM

Gradient

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
This field provides a way for content creators to create and configure gradients. At this time linear gradients support up to 5 color stops. Gradient fields have a .css property that returns CSS based on the field’s value. Learn more about the generated CSS property.
Gradient Field

HubDB Row

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Please note: HubDB requires Content Hub Professional or Enterprise.
HubDB Row fields allow a content creator to select an individual row (or rows if using repeater fields) from a defined table. You can then use this field to create user-defined lists, tables, resources, and more.
hubdb-row-field

HubDB Table

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Please note: HubDB requires Content Hub Professional or Enterprise.
HubDB Table fields allow a content creator to designate a HubDB in their account. Returns the table ID, which you can use with the HubDB HubL functions.
HubDB field

Icon

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
Icon fields provide an icon picker UI to make it easier for content creators to add icons to your modules. The Icon field is preloaded with FontAwesome Icons.
icon field

Image

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field. Only use image fields as style fields when the image is purely presentational and does not convey meaning. For background images, use the background image field instead.
Image fields provide an easy interface for content creators to add images to a module or theme. Image fields provide a file picker interface that lists images from the File Manager. Since images can be used and displayed in different ways, developers can limit the sizing options available to the content creator in the UI as well as allow for lazy-loading of images.
Image Field
https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Link fields provide an easy interface for content creators to provide links to URLs and email addresses. This field is similar to the URL field, but includes more options for configuring open nofollow options.
link field
https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Logo fields provide a way for content creators to specify logo images to use in a page, defaulting to the domain’s logo. This is useful for site headers and footers that may contain the company logo. Logo fields also allow for lazy loading.
logo field
https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Menu fields provide an easy interface for content creators to create, edit and select a navigation menu that is re-usable on other pages. This field is great for use in menus that are used across multiple pages like main navigation and footer navigation and other global content. Use this field in tandem with the menu tag or menu() function, to render a menu inside of your module. For menus that don’t make sense to re-use on other pages, like a table of contents menu, use the simple menu field.
menu field

Number

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
Number fields provide an easy interface for content creators to enter in or adjust numerical values and options. This can be used for creating percentage based items or anything where numbers are needed for input.
Number field
Suffix and prefix parameters are for display purposes in the content editor and have no effect on the numerical value of the field.

Page

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Page fields provide an interface for content creators to select site pages and landing pages. The value returned by a page field is the page ID of the selected page. When used in tandem with the content_by_id or content_by_ids functions, you can use data from the selected pages in the current page.
Page field

Rich text

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Rich text fields provide content creators with a WYSIWYG text editor experience. When a rich text field’s value is printed it is printed as HTML. When you do not want content creators to have formatting capabilities use text fields.
Rich Text field

Simple menu

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Simple menu fields provide an easy interface for content creators to create a navigation menu that is not re-usable on other pages. For menus that should be reusable, use the menu field. A time you may want this is for a table of contents menu that links to headings on very long pages, or a list of links to content that only makes sense to have on the current page.
Simple menu field

Spacing

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
This field provides a user interface (UI) for content creators to set padding and margin. Spacing fields have a .css property that returns CSS based on the field’s value. Learn more about the generated CSS property.
screenshot of spacing style field expanded in page editor
When using the spacing field, please note the following:
  • You must include a units list when setting a min or max.
  • The units property supports the following unit types: %, ch, em, ex, in, lh, pc, pt, px, Q, rem, vh, vmax, vmin, and vw.
  • When a content creator edits all padding together, HubSpot will use the highest min value and the lowest max value. In addition, only the units shared by all sides will be available to the content creator.

Tag

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Tag fields provide a blog tag picker for content creators. This tag picker returns a blog tag ID which can then be used in blog tag related functions such as Blog Tag URL and Blog Recent Tag Posts.
tag field

Text

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Text fields provide content creators a simple text editing experience with no rich text functionality. Text fields initially show as a single line, but can actually expand to be text areas, supporting multiple lines. Use these when you do not want content creators to have control over formatting. If you do want to provide formatting controls use rich text fields.
text field

Text Alignment

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/Styles.svg
Can be used in modules as a style field.
This field provides content creators a way to align text content within a container. This should not be used for aligning other assets as there is a field type specifically for that.
Text Alignment field

URL

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
URL fields provide a similar experience to link fields. Providing a UI for content creators to add links. URL fields, however, do not show a UI for open in a new window, nor tell search engines not to follow. Use this field when you as a developer want to dictate the values for that. If you want the user to have control, use link fields instead.
URL field

Video

https://developers.hubspot.com/hubfs/Knowledge_Base_2023-24-25/developer/icons/settings.svg
Can be used in modules.
Video fields provide content editors with a place to add HubSpot Video to their module content without the need of using rich text fields.
Video Field
conversion_asset object parameters:
Last modified on June 4, 2026