One portal
The licence is issued to a single HubSpot portal. A staging portal and a live portal are two portals. Building for a client means a licence in the client portal, which is where it should end up anyway.
Before you buy
The questions people ask before installing it.
What the theme is, what the licence covers, what you need in place before it installs, and what happens after the purchase. The question list is at the bottom of the page.
The licence
What one licence covers.
A licence is tied to a HubSpot portal and does not move between them. These three lines are the whole of it.
all_inclusive
It does not expire
The version you bought stays yours, with updates and fixes to it. Nothing stops working if you stop paying attention to us, and nothing in the theme phones home to check.
code
You can change any file
Edit the HubL, the CSS, the module fields. What you may not do is resell the source, share it across portals, or ship it inside a product of your own.
A HubSpot account with CMS access: Starter, Professional or Enterprise. A free CRM account cannot install a custom theme, and no workaround changes that.
What installing looks like
From the marketplace it is one click and the theme lands in Design Tools. Bought directly, it arrives as a folder you upload with the HubSpot CLI. Neither route touches the pages you already have; a theme sits alongside them until a page is switched to one of its templates.
Nothing has to be migrated for the theme to work. Pages you already publish keep running on whatever template they use now, and you move them one at a time.
What is worth having ready
- The logo as SVG or a large PNG, because the navigation scales it rather than cropping it
- Your two typefaces, or the decision to use the ones the presets ship with
- The real text for the first page you intend to rebuild, including the longest heading you really use
Blog posts, forms and CRM data are untouched by a theme change. The blog listing and post templates read the same posts you have now.
Whoever edits pages after launch does it in the HubSpot page editor. Every section on every template is a drag-and-drop module with its own fields, so adding a row of cards or reordering sections is not a developer task.
Where the line sits
Colour, type and spacing come from theme settings, not from each module, so a page editor changes layout and copy without reaching the palette. If you would rather a colleague could not change something, remove that field from the module and the control disappears from the editor.
1
It arrives in the portal
A marketplace purchase installs itself into Design Tools. A direct purchase is a download link and a CLI upload. Ends with the theme listed alongside whatever you already have.
2
Pick a preset
Light, Dark, Midnight Blue, Warm Neutral and Forest Green each set colour, type and radius together. Custom starts you from an empty set of tokens. Ends with the whole site in your palette.
3
Build one page
Create a page from a template, then edit it in the page editor. Sections move, fields drive the layout, and no step of it opens a code file. Ends with a page you can publish.
4
Hand it over
The documentation is written for the person who inherits the site rather than for the person who installed it, so handover is a link. Ends with someone else shipping a change.
Limits
What it does not do.
Written before the purchase rather than discovered after it. If one of these is a blocker, it is better found on this page.
block
It is not a HubSpot subscription
The theme runs on HubSpot CMS and does not replace it. If your account has no CMS access, the theme cannot be installed and buying it will not change that.
edit_off
It does not write your content
The demo text on these pages is placeholder. Layouts hold real sentences well and hide bad ones badly, which is deliberate.
swap_horiz
It does not migrate a site for you
Existing pages keep their current templates until someone moves them. Moving a page means recreating its sections in the new template, which is page-editor work rather than code.
photo_camera
It does not include photography
The images in the demo are placeholders and are not licensed for you to publish. Bring your own, or use a layout that does not ask for one.
lan
It does not move between portals
One licence, one portal. Staging and live are two. An agency buying for a client buys in the client portal.
engineering
It is not custom development
A module that does something no field covers is work, not a setting. Ask and we will tell you whether it is a small change or a different product.
If the answer needs longer
The long version is a course.
A course that starts with an empty portal and ends with a published page. Every part is written against this theme rather than against HubSpot in general.
Questions
Everything else, in one place
Filter by topic or search. Both narrow at the same time.
search
All questions
Every topic in one list. Pick a topic to narrow it, or search across all of them.
Buying
Where it is sold, how it is paid for, and the refund window.
Licence
What one licence covers, what happens with more than one portal, and what client work needs.
Installing
What the theme needs from your HubSpot account, and what happens to the pages you already have.
Building
Theme settings, presets, modules and the parts a marketer can change without a developer.
After launch
Updates, edited files, and what happens to a site that has been running for a year.
From the HubSpot Marketplace, where the install is automatic, or directly from us, where you get a download link and upload it with the HubSpot CLI. Payment goes through HubSpot on the first route and Stripe on the second. We do not see or store card details either way.
This site is the theme, running unmodified. Every page in the navigation is a template in the download, so clicking through them is the trial. Switch presets on the demo pages to see what a colour change does to a whole site.
Yes. Ask within fourteen days of purchase, provided the theme is not already live on a public site. Because it is source you keep a copy of, the window closes once it is published. Marketplace purchases go through the refund process HubSpot runs. The full terms are on the licence page.
Not to us. You need a HubSpot account with CMS access, which is a HubSpot cost, and a domain. The theme has no add-ons, no per-seat charge and no service that has to stay switched on for it to keep working.
One HubSpot portal, for as long as you want it. You can use it for your own site or a client site, modify any file, and keep the version you bought along with its updates and fixes.
That is two portals and two licences. We would rather say it here than have it surface during an audit of an account.
Yes, one portal per licence. Most agencies buy the licence in the client portal and bill it through, so at handover the licence is already where it belongs and nothing has to move.
Resell or redistribute the source, run one licence across several portals, or build a product for sale out of the files. Modules you write yourself against the theme tokens are a different thing and they are yours.
CMS access on Starter, Professional or Enterprise. A free CRM account cannot install a custom theme.
No. A theme sits alongside your existing templates, and a page only changes when someone switches it. Blog posts, forms and CRM data are untouched.
For a marketplace install, no. For a direct purchase, someone has to run one CLI upload once. Everything after that is the page editor.
Colour, typeface, type scale, spacing, border radius, shadows, button and form styling, card styling, navigation and footer are all theme settings. Page layout and copy are module fields. What is left for code is behaviour no field covers.
Light, Dark, Midnight Blue, Warm Neutral and Forest Green, plus Custom. Each one sets colour, type and radius as a group, so switching preset moves the entire site rather than one page. Custom starts you from an empty set of tokens and hands you every one of them.
Every icon renders through one shared partial and the library is a theme setting: Material Symbols, Font Awesome, Phosphor, Lucide, Heroicons, Bootstrap, Remix, Tabler, HugeIcons or the HubSpot icons. Change it once and every module follows.
Yes. Every module is a drag-and-drop module in your portal, so it can be dropped into any page with a drag-and-drop area, including pages built on another theme.
Blog listing and blog post templates are in the download, along with 404, 500, password prompt, search results, subscription preferences and unsubscribe. They read the same theme settings, so they do not look like a different site.
Updates and fixes to the version you bought are included. Content lives on the page rather than in the template, so an update does not touch what a marketer wrote. It does replace theme files you edited, which is why the edited ones are worth listing somewhere.
Then take updates deliberately rather than wholesale, and read the diff first. A module you wrote from scratch is never touched by an update, so heavy customisation is safer as a new module than as an edit to one of ours.
Email support for installing and configuring the theme, from the people who built it. Custom development is a separate conversation and we will say so rather than quietly doing it.
The site keeps running. There is no licence server, no phone-home check and no part of the theme that only we can change. Everything is source in your portal.
No questions match
Try a different word, or clear the filters to see everything.
Ask us
Ask the one this page did not answer.
Say which portal you are on and what you are trying to build. That is usually enough for the first reply to be useful.
A reply from the people who wrote it not a support queue
- help Pre-sale questions get an answer before you pay, not after
- gavel Licence questions get the clause, not a paraphrase
- block We will tell you when the answer is that it does not do that
Anything asked twice ends up on this page, with your name nowhere near it.