How Do Zendesk Help Center Themes Work? Copenhagen, Custom Themes and Plans (2026)

A Zendesk Help Center theme is the bundle of Curlybars page templates, CSS, JavaScript and settings that renders your customer-facing knowledge base, and every help center starts on Copenhagen, the standard theme Zendesk maintains and updates for you. You can rebrand Copenhagen's colors, logo and fonts on any plan without code; editing the code turns it into a custom theme, which needs Suite Growth or higher and stops receiving automatic updates. One date matters this year: Zendesk began retiring Templating API v1, v2 and v3 on September 14, 2026, and any theme still on them will be force-upgraded to v4 by July 31, 2027. For the wider picture, see our Zendesk Guide knowledge base guide and the Zendesk Help Center explainer; the facts below are checked against Zendesk's own documentation.

Multiple article, section and category templates layer on top of the custom-theme path and go live only on Enterprise.

What is a Zendesk Help Center theme made of?

A theme in Zendesk Guide is a bundle of files that together render your customer-facing help center. It contains:

• Page templates: the HTML structure for each type of page, such as the home page, category page, section page, article page, search results and the request (new ticket) form. Each page type has its own template.
• A stylesheet (style.css) that controls colors, typography, spacing and layout.
• JavaScript (script.js) for interactive behavior.
• A manifest and settings that expose certain values (brand color, fonts, logo) as editable options so you don't have to dig into code for simple changes.

The page templates aren't plain HTML. They're written in Curlybars, Zendesk's templating language, which lets the markup pull in live help-center data such as article titles, breadcrumbs, category lists and the search box. More on that below.

What is the Copenhagen theme, and when does it stop updating?

Every Zendesk Help Center ships with Copenhagen, the standard theme. It is a strong starting point: built around accessibility and support best practices, fully responsive on mobile, and maintained by Zendesk. Because it's the standard theme, Zendesk supports it and automatically updates it when new theme features ship, so you inherit improvements without doing anything.

The line that matters is between configuring Copenhagen and editing it:

• As long as you only change Copenhagen through the Settings panel (branding and advanced settings), it stays the "standard" theme, supported and auto-updated.
• The moment you edit its page templates, CSS or JavaScript, it's no longer standard. Your copy becomes a custom theme. In Zendesk's words, custom themes "are not supported by Zendesk and are not automatically updated when new theme features are released", so you add new theming features by hand.

That trade-off, automatic updates against full control, is the biggest decision in any theming project. Most teams should stay on Copenhagen-via-settings for as long as it meets their needs.

Can you brand a Zendesk Help Center without code?

Yes, and for most branding work you never touch code. In Guide admin (the Knowledge admin sidebar), open Customize design. From there you can adjust a theme's Settings panel, which typically exposes:

• Brand color(s): the primary accent used across buttons, links and highlights.
• Logo: your help center logo, plus a favicon and brand imagery.
• Fonts: heading and body typefaces.
• Background, text and link colors and other "advanced settings" the theme author chose to surface.

Change a value, see it in the preview, and publish. That covers what most companies need: make the help center match the brand, swap the logo, set the corporate color, pick a font. No HTML, no CSS, no deployment.

The theme editor and the Customize design screens live inside Guide admin. On our own developer instance that area sits behind a bot-verification wall, so we describe the flow rather than screenshot it. The public help center above is a real example of the branded result theming produces.

How do you customize a Zendesk theme with code?

When the Settings panel can't get you there (a different layout, an extra page element, custom navigation, or hiding a component), you move into the code. In Customize design, click Customize on the theme, then Edit code. The theme's files are grouped into Templates, Styles (CSS), JavaScript, Settings and Assets.

Curlybars and page templates

The HTML templates use Curlybars, a Handlebars-style templating language Zendesk built for the help center. Unlike Handlebars, Curlybars renders server-side. Its double-brace expressions let the template pull in real data and render it: looping over a category's sections, printing an article body, dropping in the search bar, or showing breadcrumbs. You can also use Curlybars conditionally, for example to hide a specific article, section or category by targeting its ID.

There's a template per page type (home page, category, section, article, search results, new request form and others), so you can tailor each surface independently. On Enterprise you can go further and create additional article, section or category templates when one layout isn't enough for all your content.

Which Templating API version should your theme use?

Curlybars and the theme structure make up Zendesk's Templating API, which is versioned. Your theme declares its version in the api_version field of its manifest.json. There have been four versions: v1 (November 2014), v2 (February 2020), v3 (June 2023) and v4 (July 2, 2024), the current version. The version decides which helpers your theme can use. Newer versions bring performance and accessibility improvements and also remove older helpers: v4 dropped the {{request_form}} and {{follow_up}} helpers from the new-request template, replacing them with a new_request_form object that Copenhagen renders with React and Garden components.

Copenhagen tracks the latest version automatically. A custom theme stays on whatever version its manifest declares until you upgrade it: download the theme, bump api_version, preview locally to catch deprecation warnings, and replace anything unsupported.

When do Templating API v1, v2 and v3 stop working?

Zendesk has announced the end of life for v1, v2 and v3, in four steps:

• September 14, 2026: new accounts can no longer import v1, v2 or v3 themes.
• November 25, 2026: Zendesk launches an upgrade tool in the Zendesk Command Line Interface (ZCLI) for custom-coded themes.
• March 1, 2027: importing v1, v2 or v3 themes is blocked for all accounts.
• July 31, 2027: any remaining legacy theme is force-upgraded to v4, and the old versions are removed.

If your live theme is custom and still declares v3 or earlier, upgrade it on your own schedule before July 31, 2027, rather than letting a forced conversion break a form or a helper your layout depends on. It's one more reason custom themes are a maintenance commitment: compatibility doesn't update on its own.

Editing, downloading and importing themes

The code editor lets you make changes in place, but you can also work outside Zendesk:

• Download a theme as a ZIP to version-control it, edit it locally, or back it up before a big change.
• Import a theme ZIP back into Guide. This is how you bring in a third-party theme or deploy a locally developed one.
• Use the CSS and JavaScript files for site-wide appearance and behavior, and Curlybars in the templates for structural content changes.

A sensible workflow for anything non-trivial: download the current theme as a backup, build or import a copy, preview it, and only then set it live.

Can you use a marketplace or third-party theme?

Yes. The Zendesk Marketplace offers Guide themes, free and paid, built by Zendesk partners. You browse, import one into your help center, then customize it like any other custom theme. It's a fast way to get a more distinctive design than Copenhagen without commissioning one. A marketplace theme behaves like any custom theme: you own its maintenance, it won't receive Copenhagen's automatic updates, and you should check which Templating API version it declares before you import it, since v1 to v3 imports are being blocked.

How do you manage multiple themes and set the live one?

Your help center can hold more than one theme, but only one is live, the one customers see. That is what makes safe iteration possible: leave the live theme untouched, work on a draft copy, and swap when ready.

To switch, open the theme's options menu and choose Set as live theme. The newly live theme moves to the top and applies to your help center immediately. Because the old theme is still there, rolling back is just setting it live again, which is why you keep the previous version around rather than editing the live theme in place.

How does theming work with multiple brands?

If you run multiple brands in Zendesk, each brand gets its own help center, and therefore its own theme and live-theme selection. A parent company can give each brand a different logo, colors and even layout while managing everything from one Zendesk account. Multibrand and the number of brands you can run depend on your plan, so confirm what your subscription includes before planning a multi-brand rollout.

Which Zendesk plan do you need for custom themes?

Theming is tiered, and the line that catches teams out is code access:

• Standard Copenhagen and Settings-panel branding is available broadly. You can change colors, fonts and logo without a premium tier.
• Editing theme code or using custom themes is available from Suite Growth upward (Growth, Professional, Enterprise and Enterprise Plus, plus Support with Knowledge Professional or Enterprise). Per Zendesk, custom themes are not available on Suite Team: on the entry tier you configure the standard theme and cannot edit its code or import custom or marketplace themes. The common misconception is that you need Professional; Suite Growth is the lowest qualifying tier.
• Multiple page templates go live only on Enterprise or Enterprise Plus (or Support with Knowledge Enterprise), where you can add up to 100 extra templates each for articles, sections and categories. On Suite Growth and Professional you can build them only in a non-live theme, to test the feature.
• Multibrand (several help centers, each themed) is gated to higher tiers.

Zendesk renames and repackages plans periodically, so confirm the exact tier names and limits in your own account before you commit to a customization plan.

How do you avoid breaking your help center when you change the theme?

A help center is customer-facing and high-traffic, so theming mistakes are visible mistakes. A few rules keep you safe:

• Back up before you change. Download the current theme as a ZIP first. It's your instant rollback.
• Work on a copy, preview, then publish. Never edit the live theme directly. Use a draft theme, preview it, and only Set as live theme once it's right.
• Keep custom code minimal. Every line you add is a line you maintain, and the further you diverge from Copenhagen, the more updates and support you give up. Prefer the Settings panel; drop to code only when you must.
• Check the API version. Know what your manifest declares and plan the v4 upgrade before the July 2027 forced conversion.
• Design mobile-first. Much help-center traffic is mobile. Copenhagen is responsive out of the box; keep it that way when you customize, and test on real screen sizes.
• Protect accessibility. Keep color contrast, resizable text, focus states, semantic headings and meaningful alt text. Copenhagen is built with accessibility in mind; don't undo it with a low-contrast brand palette.
• Stay brand-consistent. Logo, colors and fonts should match your main site so the help center feels like part of the product.

Common mistakes: editing the live theme with no backup; over-customizing Copenhagen and then missing months of Zendesk updates; pasting heavy third-party scripts that slow page loads; assuming code edits are available on an entry plan (they're not); and shipping a good-looking theme whose search returns nothing useful.

What can't a help center theme fix?

A polished theme makes your help center look trustworthy. It doesn't make the right answer appear when a customer types a question. If search returns three loosely related articles and none of them solve the problem, the customer gives up and opens a ticket, however good the branding is.

That gap is where an AI agent comes in, and it's a separate layer from theming. Macha is not a help desk and not a Zendesk replacement. It is an AI agent layer that runs on top of the Zendesk you already run. Pointed at your help center content and past tickets, it answers the customer's question in the words they used and hands off to a human with full context when it can't. The theme controls the experience; the agent decides whether the experience ends in an answer. Macha bills per ticket, one conversation charged once however many replies it takes, starting at $299 a month for 750 tickets with setup and monitoring included. You can start with $50 of free usage and no credit card.

Frequently asked questions

What is the default Zendesk Help Center theme? It's Copenhagen, the standard theme that ships with every help center. It's responsive, built around accessibility, supported by Zendesk, and automatically updated when new theme features are released, as long as you customize it through the Settings panel rather than editing its code.

Can I customize my Zendesk Help Center without coding? Yes. In Guide admin under Customize design, the theme's Settings panel lets you change brand color, logo, fonts and other exposed options with no code. That covers most branding needs. You only need code for structural or layout changes the settings don't expose.

What is Curlybars in Zendesk? Curlybars is Zendesk's Handlebars-style templating language for help center themes, rendered server-side. It's used in the page templates to pull in live help-center data (article content, category and section lists, breadcrumbs, the search bar) and to show or hide components conditionally. Custom themes combine Curlybars templates with CSS and JavaScript.

What Zendesk plan do I need to edit my theme's code? Suite Growth or higher (Growth, Professional, Enterprise, Enterprise Plus, or Support with Knowledge Professional or Enterprise). Custom themes are not available on Suite Team. Using multiple page templates in a live theme needs Enterprise, with up to 100 extra templates each for articles, sections and categories.

Can I use a third-party theme? Yes. You can browse Guide themes in the Zendesk Marketplace (free and paid) and import one, or import a theme ZIP you've built or downloaded. Imported themes are yours to maintain and don't receive Copenhagen's automatic updates.

How do I switch which theme is live? Your help center can store multiple themes, but only one is live. Open the theme's options menu and choose Set as live theme; it applies immediately. Keep your previous theme so you can roll back by setting it live again.

Do I need to upgrade my theme to Templating API v4? Yes, if it's a custom theme on v1, v2 or v3. Zendesk blocked those imports for new accounts on September 14, 2026, blocks them for all accounts on March 1, 2027, and force-upgrades any remaining legacy theme to v4 on July 31, 2027. Copenhagen on the Settings panel is already on the current version.