Contentful content type limits

Contentful content type limits by plan

As of April 2026, Contentful’s plan-based content type limits are:

The change most New Zealand businesses on Contentful don’t know about: Effective 30 April 2025, Contentful reduced the Free plan content type limit to 25. Previously, the Free plan allowed an unrestricted number of content types. Teams on legacy Free plans who built their content model before this change may now find themselves over the new limit, or approaching it without realising the ceiling was lowered.

According to Contentful’s technical limits documentation, the hard technical ceiling is 1,000 content types per environment. This applies to Premium and Enterprise plans. For Free plan teams, the plan entitlement of 25 is the binding constraint, not the technical ceiling.

What happens when you hit the limit: Contentful will prevent you from creating new content types. Existing content types and their entries are unaffected. You can’t publish new structural models until you either delete existing types, archive unused ones, or upgrade your plan.

Two secondary limits worth knowing:

• 50 fields per content type (structuring a type with more than 50 fields is a signal the type needs splitting)

• 1,000 total entry links across all fields in a content type — entry links are references from one entry to another, used for related content, authors, or category tags (this limit affects highly relational content models)

For a full breakdown, see Contentful’s pricing page and the Contentful data model documentation.

Five warning signs your content model needs an audit

Before assuming you need a plan upgrade, check whether your content model itself is the issue. These are the patterns we see most often in NZ and AU enterprise implementations.

1. You have a content type for every page template, not every content pattern. “Homepage”, “About Page”, “Services Page”, “Contact Page” — each as a separate content type. This is the most common mistake. Page templates belong in your design system. Content types should reflect the structure of your content, not the layout of a specific page. One well-designed flexible Page type with modular references can replace 15 template-specific types.

2. You find yourself duplicating fields across multiple types. If your “Event”, “Webinar”, and “Workshop” content types all have the same title, description, date, and registration URL fields, you probably have one content type masquerading as three. Duplication is the clearest signal that consolidation is possible.

3. Your editors can’t decide which content type to use. Emma, a digital content manager at a Wellington-based professional services firm, described it this way: “We have ‘News Article’, ‘Insights Post’, ‘Case Study Update’, and ‘Industry Commentary’. Every time I write something new, I spend five minutes deciding which one it goes in, and I still get it wrong sometimes.” When editors are confused, the model is wrong. One well-structured Editorial type with a category field replaces four.

4. Your developers have to check which type to query before building a component. If your frontend team frequently asks “what content type does this pull from?”, your model has become unpredictable. A coherent model means types map clearly to components, and developers know what to query without investigation.

5. You have content types nobody will touch. “EOFY Campaign Banner 2024”, “Easter Promo Section”, “Legacy Partner Block” — campaign-specific content types created for a single initiative and never cleaned up. This is content debt: it accumulates silently, one content type at a time, until you’re at 40 types and can’t account for half of them.

If two or more of these apply to your implementation, an audit will almost certainly recover enough headroom to keep you within your current plan.

If you’re not sure where to start, talk to our team about a content type audit. It’s a standalone engagement, you don’t need to be mid-project for it to be useful.

How to reduce your Contentful content type count without breaking your site

A Contentful content type audit follows a consistent process. Here’s how we approach it. It’s methodical, and it produces results before you touch a single content type.

Step 1: Audit what you actually have

Export a list of all content types in your space. For each one, record: how many entries exist, when the most recent entry was created, which pages or components use it, and whether any external system — your CRM, marketing automation platform, or API consumers — depends on it. Contentful’s Content Management API makes this straightforward to pull.

What you’ll typically find: 20–40% of content types have no recent entries. Many haven’t been touched in over 12 months. In implementations where Contentful content type limits are becoming a problem, unused types are almost always part of the story.

Step 2: Identify redundancy

“News Article”, “Blog Post”, “Insight”, “Industry Update” — do they have the same fields? The same editorial workflow? If yes, they’re the same content type with different names.

List your consolidation candidates. Don’t merge yet — document first.

Step 3: Separate structure from content

The most powerful audit insight is usually this: teams have built content types that represent page layouts rather than content structures. Separate the two.

Your page layouts belong in your component library. Your Contentful content types should represent content objects — things that have meaning independent of where they appear. A “Hero Banner” content type that only ever appears on the homepage isn’t a content object. It’s a page section masquerading as one.

Step 4: Introduce modular references

Rather than a separate content type for every variation, use a single flexible type that references modular component types. One “Page” type with a References field pointing to an ordered list of components (“Hero”, “Feature Block”, “Testimonial”, “CTA Strip”) replaces every page-specific type you currently have. This is the architectural pattern that keeps type counts low on even complex sites.

Step 5: Archive, don’t delete

Contentful allows you to archive content types that have no entries. Archiving removes them from your active count and hides them from editors, but preserves the schema for reference. Only delete content types when you’re certain neither the entries nor the schema will ever be needed. Archive first; delete later.

A structured audit of this kind typically takes one to two days for a mid-sized NZ enterprise implementation. The result is a leaner model, better editor experience, and enough headroom to keep building without hitting the limit again. This is what good Contentful content model optimisation looks like in practice — not a full rebuild, but a focused rationalisation.

Modular content model design: the pattern that prevents the problem

The teams that never hit Contentful content type limits aren’t lucky — they designed their model before they built anything. Architectural content modelling is what keeps the limit irrelevant.

Consider two approaches to a corporate website with 12 distinct page types:

Approach A (reactive)

Create a content type for each page: “Homepage”, “About”, “Services Overview”, “Individual Service Page”, “Team”, “Team Member”, “News”, “News Article”, “Events”, “Event Detail”, “Contact”, “Careers”. That’s 12 content types before a single campaign, landing page, or resource hub has been considered.

Approach B (modular)

Create a “Page” content type with a modular References field. Create component types: “Hero”, “Text Block”, “Feature Grid”, “Person Card”, “Event Card”, “CTA Block”. A homepage is a Page entry with a Hero + Feature Grid + CTA Block. A team page is a Page with a collection of Person Card entries. The entire site runs on the Page type plus eight component types. Total: nine content types, instead of twelve. And it scales cleanly as new page templates are added.

The modular approach also makes integration simpler. When your Contentful content model is designed with your CRM in mind from the start, content types can carry the fields your personalisation and lead scoring logic needs. A “Resource” content type with an audienceSegment field, for instance, allows your CRM integration to surface the right content to the right contact, without retrofitting it later. This is the design-first principle we cover in more depth in our Contentful implementation service.

The design system parallel is equally important. Your content types should map to your design system’s component inventory, not to your sitemap. If a designer and a Contentful architect review your model together, they should see the same structure.

Contentful plan limits: when to optimise vs. when to upgrade

The answer depends on why you’re approaching the limit.

If you’re on the Free plan and approaching 25 types

Audit first. Most Free plan implementations that hit 25 types have significant consolidation potential. If after a thorough audit you genuinely need more than 25 distinct content structures, that’s a legitimate signal to upgrade. But in most cases, the audit reveals that five to ten types can be removed or merged without any loss of content functionality.

If you’re on the Lite plan and growing

The Lite plan’s content type entitlement isn’t publicly documented, but it’s significantly higher than 25. If you’re hitting limits on a Lite plan, you almost certainly have a model architecture problem. An upgrade to Premium won’t solve it. It will delay it.

If you’re on Premium and hitting complexity

At the Premium tier, the technical ceiling is 1,000 content types per environment. No well-designed enterprise content model approaches this. If you’re experiencing content model complexity on Premium, the problem is architectural. A model review and restructure will resolve it; upgrading further won’t.

The cost consideration

Moving from Free to Lite is USD $300 per month. If an audit identifies consolidation opportunities that bring you back under 25 types, you avoid that cost entirely while ending up with a better model. It’s worth knowing the option exists before committing to the upgrade.

What a Contentful content type audit actually involves

Content type bloat is one of the most common issues we encounter when auditing existing Contentful implementations. It’s also one of the most preventable. A Contentful content type audit — done before a team hits the hard limit — typically recovers significant headroom and leaves the model in better shape than it started.

Take the experience of an Auckland-based education provider we worked with last year. They’d migrated from WordPress 18 months earlier. The migration created one content type per WordPress post type — including legacy types from a previous site redesign that had never been cleaned up.

By the time they called us, they had 43 content types. About half were actively used. Twelve had no entries at all. Six were near-duplicates of each other.

After a two-day content model audit, they were running on 19 types. The model was cleaner, their editors stopped second-guessing themselves, and they gained enough headroom to build out a new course library without touching their plan tier.

This work, specifically the audit and reduction of unnecessary content types and the implementation of modular, scalable models aligned with design systems, is a named part of our Contentful practice. It can run as a standalone engagement or as part of a broader platform build.

Every new Contentful implementation we deliver starts with a content model design session before any types are created. We map the editorial workflows your team actually follows, align the model to your design system’s component inventory, and design integration touchpoints, what content types need to expose for your CRM, marketing automation, or personalisation layer. The result is a model that launches clean and stays that way.

Our delivery model runs to 4–6 weeks for a connected Contentful implementation, content model designed, component library built, CRM integration configured, team trained. Fixed scope, fixed cost. And because the model is designed architecturally from the start, it doesn’t accumulate content debt.

Key takeaways

• Contentful content type limits are plan-dependent. Free plan teams are capped at 25 (reduced from unlimited in April 2025). The technical ceiling for paid plans is 1,000 per environment. Most teams will never approach that ceiling if their model is designed well.

• The limit is the symptom. Teams that build content models reactively, adding a type per campaign, per page template, per feature request, accumulate content debt and eventually hit the wall. Teams that design architecturally rarely need more than 25–30 types, regardless of site complexity.

• Audit before you upgrade. Most implementations approaching their limit have significant consolidation potential. A structured audit typically takes one to two days and can recover enough headroom to keep you within your current plan.

• Modular design prevents the problem. One flexible Page type with modular component references replaces dozens of template-specific types. If your model maps to your sitemap rather than your design system, it needs rethinking.

• Content type debt is real. Like technical debt, it accumulates silently, one campaign type at a time, and becomes expensive to address the longer it’s left.