Every HubSpot theme is a set of constraints. That is the product. You are paying someone to have already decided how a hero works, how a pricing table behaves, how a page breaks on a phone.
Good constraints are invisible. You never notice the decisions a theme made for you, because you did not want to make them.
The trap starts somewhere else: the first time you need something the theme does not do, and someone says "we'll just build a custom module for that."
That sentence is always reasonable. It is also the beginning of the only kind of lock-in that actually hurts on HubSpot, and almost nobody explains the mechanic behind it. So let us do that first, and then give you a test you can run in twenty minutes.
A HubSpot site has three layers, and they have completely different portability.
The content layer. Blog posts, forms, contacts, files, CRM data. This never locks. It lives in HubSpot, not in the theme. If you switch themes tomorrow, it does not move.
The style layer. Colors, typography, spacing, set in theme settings. Mostly portable in the sense that the decisions transfer, even if you re-enter them.
The layout layer. Your pages, built out of the theme's modules. This is the layer that locks. A page assembled from Theme A's modules does not survive a move to Theme B. Not because HubSpot forbids it, but because the modules the page is made of stop existing.
So when someone asks "how locked in am I?", the honest answer is a page count. How many pages would have to be rebuilt by hand. Nothing else.
Here is the part that changes how you shop.
A theme you buy from the HubSpot marketplace is not editable. You cannot open a module and change it. To customize anything, you create a child theme, which is HubSpot's supported way of overriding a parent without forking it.
And here is the clause that matters: creating a child theme does not copy the templates, modules, stylesheets or scripts. It starts empty. You clone into it only the specific assets you want to change. A file in the child theme overwrites the equivalent file in the parent.
Read that again with a maintenance hat on.
The moment you clone a module into your child theme to change one thing, that module stops being the vendor's problem. The vendor keeps shipping updates. Your cloned copy does not receive them. Fixes, accessibility improvements, new options, compatibility with whatever HubSpot changes next: all of it lands in the parent module you are no longer using.
That is module debt, and it is not a metaphor. It is a specific file that is now yours forever.
One cloned module is nothing. Twelve is a part-time job nobody was hired for. And the twelve arrive one reasonable decision at a time.
HubSpot caps a marketplace theme at 50 page templates, 50 modules and 50 sections. System templates, the 404 and 500 pages, password prompts and subscription preferences, are required but counted separately. Every serious premium theme is pressed against that ceiling.
This has a consequence buyers consistently miss: module count is not the number to compare. All the good themes are at 46 to 50. What differs is how those 50 were spent.
A theme can spend its 50 on fifty narrow modules, each doing one specific layout. Impressive in a demo. It traps you faster, because the day you need the fifty-first layout, there is no room and no option, and you are cloning.
Or a theme can spend 40 modules that each expose deep options, so one module produces fifteen genuinely different sections. Less impressive in a list. Far harder to outgrow.
When you evaluate a demo, do not count modules. Open one module and count the decisions it lets you make. That number predicts whether your next request ends in a settings panel or in a developer ticket.
Five questions. Answer them before you buy, not after.
1. How many custom modules would you need in week one?
Take your current site, or the wireframe of the one you want. Walk it against the theme's demo. Count the sections that have no equivalent. If the number is above three or four, you have picked the wrong theme, not found a customization project.
2. What can a marketer change without help?
This is the editable surface, and it is not a yes or no. Can they change copy? Yes, every theme. Can they change the layout of a section, swap a two-column for a three-column, reorder blocks, adjust the mobile version separately? That is the real question, and the answer varies enormously.
3. What breaks if the theme disappears?
Count the pages built with theme modules. That number is your exit cost, in rebuild hours. Everything else survives.
4. Who owns the code you added?
If a freelancer built your four custom modules and left, are they documented, and does anyone else understand them? Module debt is bad. Undocumented module debt owned by someone who no longer answers email is worse.
5. What updates are you giving up?
For each cloned module, you are opting out of the vendor's maintenance on that file. Make that trade explicitly. Write it down. It should buy you something you can name.
Twenty minutes, and it tells you more than any demo.
Three or more out of ten and your website is a developer dependency, not a marketing asset. That is the number a new theme has to move. If a theme you are evaluating would not have changed those rows, it is not solving your problem, whatever it costs.
Most teams have never run this. It is uncomfortable, and it is the only measurement in this article that comes from your own site rather than a listing page.
Nobody decides to build a site only one person can touch. It happens the way all of these things happen.
The homepage needs a slightly different hero, so we clone the hero. The campaign needs a countdown with a custom style, so we clone the countdown. The product page needs a comparison table with one more column, so we clone the table. Each request takes a day. Each one is defensible on its own.
Eighteen months later the site has fourteen cloned modules, none of them receiving updates, and exactly one person who knows which is which. Nothing went wrong. Every decision was right. The sum is the problem.
The discipline is not "never customize." It is: an exception has to buy a business outcome you can name out loud. More leads, a faster launch, a compliance requirement. "The designer preferred it" is not one. If you cannot name the outcome, use the module the theme gave you and spend the day on the offer instead.
This is what a good theme buys you: not fewer options, but fewer decisions worth making.
Send this list. The answers, and how fast they come, tell you as much as the answers themselves.
It means your page layouts are built from one theme's modules and do not transfer to another theme. Your content, forms, blog posts and CRM data are never locked. Lock-in on HubSpot is measured in pages that would need rebuilding, not in data you could lose.
No. Marketplace themes are not editable. To customize one, you create a child theme and clone into it only the assets you want to change. A file in the child theme overrides the equivalent file in the parent.
Only for what you cloned. The parent theme keeps updating, but any module or template you copied into your child theme no longer receives those updates. That is the real cost of a customization, and it is permanent.
There is no hard number, but a useful rule is that if you need more than three or four in your first month, the theme does not fit your site. That is a selection problem, not a development project.
HubSpot caps marketplace themes at 50 page templates, 50 modules and 50 sections, with system templates counted separately. Every premium theme is close to that ceiling, which is why module count is a poor way to compare them. How deeply each module can be configured matters more.
List the last ten changes your team made to the website and note who shipped each one. If a developer had to touch three or more, your site is a developer dependency. A theme worth buying moves that number.
Ocean Pro was built by an agency that maintains client sites, which is a different design brief than building a theme to sell. The modules carry deep options precisely so the answer to "can we change that?" lands in a settings panel instead of a ticket. See the module settings, not just the demo.
Deciding between themes rather than deciding how to live with one? Read Best HubSpot Themes for B2B Websites in 2026.