Key Takeaways
HubSpot built its CMS with one principle: marketers should own their web pages. That means no ticketing a developer every time you need to swap a homepage slider image, update a CTA, or push a time-sensitive offer live.
The mechanism behind this autonomy? Modules. HubSpot breaks every webpage into modular components that marketers can add, remove, and edit independently. But not all modules are created equal. Understanding the three types—standard, custom, and global—determines how fast you can move and how much control you actually have over your site.
Why Modules Matter for Marketers
Think about the assets you manage daily:
1Email Templates
Campaigns with rotating offers, seasonal designs, and A/B test variants.
2Landing Pages
Event registrations, product launches, gated content offers—all time-sensitive.
3Website Pages & Blog Posts
Homepages, product pages, content hubs that need fresh infographics, updated stats, and new CTAs.
4Sliders & Promotional Banners
The homepage carousel that needs updating every sprint cycle to reflect new campaigns.
Every one of these assets lives inside a module. If you can't edit the module, you can't update the page. And if you can't update the page without filing a developer ticket, your campaign timeline just got 3-5 business days longer.
The Bottom Line: Module-based web development is HubSpot's way of making marketers self-sufficient. The question isn't whether you should learn how modules work—it's how much time you're wasting by not understanding them.
The Three Module Types in HubSpot CMS
Every module in HubSpot falls into one of three categories. The one you choose depends on the kind of content you need to create, store, and display.
Standard
Pre-built, drag-and-drop. No code required.
Custom
Developer-built. Content editable by marketers.
Global
One edit updates everywhere. Site-wide consistency.
Standard Modules: Your Drag-and-Drop Toolkit
HubSpot identified the most common webpage elements and pre-built them as standard modules. These are in-built components that work with zero coding knowledge. You drag them onto a page, fill in the content, and publish.
Where You Use Standard Modules
Standard modules are accessible from two interfaces inside HubSpot: the Design Manager (for template-level layout) and the Page Editor (for page-level content). Marketers typically work in the Page Editor.
The main concern for any marketer is addition, exclusion, and editing of components. Standard modules make all three operations trivially simple—click, edit, publish. Need to update a homepage banner at 4:57 PM on a Friday before a product launch? Standard modules handle that in under 2 minutes.
If your team needs a custom HubSpot CMS setup that maximizes marketer self-service, we build template architectures specifically optimized for non-technical content editing.
Custom Modules: Developer-Built, Marketer-Editable
When standard modules can't deliver the functionality you need, custom modules fill the gap. These require a developer who knows HTML, CSS, JavaScript, and HubL (HubSpot's templating language) to build. But here's the critical distinction: once built, marketers can edit the content inside them freely.
Common Custom Modules in HubSpot Themes
HubTheme and similar frameworks ship with reusable custom modules that cover the most requested design patterns:
Custom modules maintain their style across individual templates. A slider built as a custom module on your homepage will look and behave identically if you add it to a landing page—no re-styling required.
The Five Field Types Marketers Can Edit
When a developer hands you a custom module, you're not locked out of it. HubSpot exposes five editable field types that let you modify content without touching the code:
Editable Field Types
Why This Matters: Primary fields control content (text, images, formatted copy). Control fields control behavior (toggles and selections). Together, they let marketers customize both what appears and how it appears—without writing a single line of code.
Two Ways to Edit Custom Modules
HubSpot provides two editing interfaces for custom modules. As a marketer, you'll almost always use the first one:
Via Modules Box (Recommended):
Via Code Editor (Advanced):
If your marketing team works inside HubSpot CMS regularly, having a dedicated development team build out a library of custom modules tailored to your campaign workflow saves an average of 14.5 hours per sprint on content production.
Global Modules: One Edit, Every Page Updated
Global modules are the consistency layer. When you create a global module on HubSpot COS/CMS, you intend to use it throughout the entire website. Change it once, and it updates on every page where it appears.
Best Use Cases for Global Modules
Global modules solve the "update 47 pages" problem. A single edit cascades site-wide automatically.
A global module can be a single content module or a group of multiple modules bundled together. Either way, editing is identical to standard modules—click, modify, save. The only difference is scope: global = everywhere, standard/custom = per page.
Standard vs. Custom vs. Global: When to Use Each
Module Selection Guide
The Marketer's Module Workflow: 5 Steps
Here's the practical workflow for marketers who want to get the most out of HubSpot's module system:
Audit Your Current Templates
Open your HubSpot Design Manager and identify which modules are standard, custom, and global. Knowing what you already have prevents duplicate work and reveals editing capabilities you may not have known existed.
Request Custom Modules for Repetitive Tasks
If you're filing developer tickets for the same type of change every sprint (slider updates, testimonial swaps, pricing changes), ask your developer to build a custom module with editable fields. One $1,300 investment eliminates recurring developer costs permanently.
Convert Repeated Elements to Global Modules
Any element that appears on more than 5 pages should be a global module. Headers, footers, announcement bars, and brand blocks all qualify. This ensures one update propagates instantly across your entire site.
Use Boolean Fields for Campaign Toggles
Ask your developer to add boolean (on/off) fields to custom modules that control visibility. This lets you hide a seasonal promotion, enable a flash sale banner, or toggle a new feature announcement—all with a single checkbox click.
Document Your Module Library
Maintain a shared document listing every custom and global module, its purpose, and which fields are editable. New team members onboard 3x faster when they have a module playbook instead of guessing what each component does.
Need a team to build and maintain your HubSpot module library? Our software outsourcing services include dedicated HubSpot CMS development with marketer-friendly deliverables.
Frequently Asked Questions
What is a HubSpot module?
A HubSpot module is a reusable content component that can be added, edited, and rearranged on web pages within the HubSpot CMS. Modules handle everything from text blocks and images to complex interactive elements like sliders, pricing tables, and FAQ accordions. They come in three types: standard (pre-built, drag-and-drop), custom (developer-built with editable fields for marketers), and global (site-wide elements that update everywhere when edited once).
<div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question" class="bg-white rounded-xl p-5 shadow-sm border border-gray-200">
<h3 itemprop="name" class="font-bold text-gray-900 mb-2">Can marketers edit custom modules without coding?</h3>
<div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
<p itemprop="text" class="text-gray-600">Yes. Custom modules require a developer to build initially (using HTML, CSS, JavaScript, and HubL), but once created, marketers can edit all exposed content fields—text, images, rich text, toggles, and dropdown selections—through HubSpot's visual editor without writing any code. The editing experience is nearly identical to working with standard modules.</p>
</div>
</div>
<div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question" class="bg-white rounded-xl p-5 shadow-sm border border-gray-200">
<h3 itemprop="name" class="font-bold text-gray-900 mb-2">What is the difference between a custom module and a global module in HubSpot?</h3>
<div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
<p itemprop="text" class="text-gray-600">A custom module is a developer-built component with specific functionality (sliders, pricing tables, etc.) that can be used on individual pages. A global module is any module—standard or custom—that has been designated to appear site-wide. Editing a global module updates it on every page where it exists. Custom modules are about functionality; global modules are about scope and consistency.</p>
</div>
</div>
<div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question" class="bg-white rounded-xl p-5 shadow-sm border border-gray-200">
<h3 itemprop="name" class="font-bold text-gray-900 mb-2">How many standard modules does HubSpot offer?</h3>
<div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
<p itemprop="text" class="text-gray-600">HubSpot includes over 25 standard modules covering the most common webpage elements: rich text, images, forms, CTAs, video embeds, social sharing, menus, headers, footers, and more. These can be used directly in the Design Manager or Page Editor without any development work. Additional elements are available through HubSpot's marketplace.</p>
</div>
</div>
<div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question" class="bg-white rounded-xl p-5 shadow-sm border border-gray-200">
<h3 itemprop="name" class="font-bold text-gray-900 mb-2">What is HubL and do marketers need to learn it?</h3>
<div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
<p itemprop="text" class="text-gray-600">HubL is HubSpot's proprietary templating language used by developers to build custom modules and templates. Marketers do not need to learn HubL. The entire point of HubSpot's module architecture is to separate developer concerns (code, structure, logic) from marketer concerns (content, images, CTAs). Developers write HubL; marketers edit the content fields those modules expose.</p>
</div>
</div>
<div itemscope itemprop="mainEntity" itemtype="https://schema.org/Question" class="bg-white rounded-xl p-5 shadow-sm border border-gray-200">
<h3 itemprop="name" class="font-bold text-gray-900 mb-2">Should I use the Design Manager or the Page Editor to edit modules?</h3>
<div itemscope itemprop="acceptedAnswer" itemtype="https://schema.org/Answer">
<p itemprop="text" class="text-gray-600">Marketers should use the Page Editor for content changes—it provides a visual, WYSIWYG interface for editing module content on specific pages. The Design Manager is primarily for developers and template architects who need to modify template-level layouts, create new templates, or build custom modules from scratch.</p>
</div>
</div>
The Bottom Line
HubSpot's module-based architecture was designed to put marketers in the driver's seat. Standard modules handle the basics. Custom modules extend functionality while keeping content editable. Global modules enforce brand consistency at scale. Understanding all three eliminates the developer bottleneck and lets your marketing team move at the speed of your market.
Need HubSpot CMS Development That Empowers Your Marketing Team?
We build custom HubSpot module libraries that give marketers full content control—sliders, pricing tables, testimonials, and campaign toggles—without developer tickets.
Get a Free HubSpot Audit