Freshdesk Portal Themes & Templates Explained

Where portal themes live

Everything starts in one place. Per Freshworks' Customizing your customer portal documentation, you manage themes under Admin → Portals, where you click edit next to a portal and switch to the Appearance tab.

When you first sign up, your portal ships with the Marina theme applied by default. The Appearance tab shows your current live theme, an Available themes gallery of other theme cards you can switch to, and an Import theme button for bringing in a theme from outside Freshdesk. Alongside the gallery is a live preview so you can see roughly what you're about to ship before you commit to it.

The gallery is the "templates" people usually mean when they search for Freshdesk portal templates: a set of pre-built starting points you can adopt as-is, or clone and modify. You don't have to design from a blank page.

Basic vs advanced customization

Freshdesk splits portal theming into two tiers, and knowing which one you need saves a lot of time.

Basic customization is the no-code path. Inside a theme you can adjust the colors — primary color, body elements, header and footer — and the fonts through a visual palette, with no HTML or CSS involved. For most teams that just want the portal to match their brand palette and logo, this is the whole job.

Advanced customization is the code path. Freshdesk exposes an in-built code editor where you work directly with HTML, CSS, and Liquid to restructure the layout of individual pages and sections. This is how you'd move a search bar, restyle article cards, inject a custom header, or add tracking markup. Per Freshworks' advanced portal customization guide, this deeper editing is gated to the Pro and Enterprise plans — Free and Growth accounts get the basic color-and-font controls but not the code editor.

Working with themes: clone, edit, import, publish

Themes in Freshdesk behave a bit like branches in version control — you don't edit the live one directly, you work on a copy. Here's the typical flow:

1. Open Admin → Portals, click edit on your portal, and go to the Appearance tab.
2. To modify the theme that's currently live, click Clone & Edit theme — this makes a working copy so your live portal stays untouched while you experiment. For a theme in the gallery that isn't live, you'll see Edit theme instead.
3. Make your changes — colors and fonts in the basic editor, or HTML/CSS/Liquid in the code editor.
4. Click Preview in a new tab to check the result, and use the device toggles at the top to see it on desktop, tablet, and mobile.
5. When it looks right, Save and then Publish to push it live. If you need to walk back, Reset returns you to the last saved state.

Beyond that, a three-dot menu on each theme card gives you View on portal, Download, Rename, Clone, and Delete theme. Downloading exports the theme (Freshdesk emails it as a .zip), which is how you back up a theme, hand it to a developer, or move it between environments. Import theme accepts that same .zip — so you can build or buy a theme externally, import it, and apply it to your portal.

The Liquid templating layer

If you go into advanced customization, you're really working with two things: styling (CSS) and structure (Liquid templates). Liquid is the templating language Freshdesk uses to render dynamic content — it's the same lineage as the Liquid used across other Freshworks and Shopify-style products, so if you've touched it before, it'll feel familiar.

The most important concept is the Layout, which Freshworks calls the most important part of a theme. Your layout wraps every page and must include three placeholders:

• {{ header }} — replaced by your header code.
• {{ footer }} — replaced by your footer code.
• {{ content_for_layout }} — replaced by the specific content of whichever page is rendering. Do not remove this placeholder — without it, page content has nowhere to render.

Freshdesk also gives you drop-in snippets for the interactive bits you don't want to hand-build, like {% snippet login_form %}, {% snippet signup_form %}, {% snippet new_topic_form %}, and {% snippet new_ticket_form %}. You place the snippet tag and Freshdesk renders the working form.

The code editor exposes 17 editable pages grouped into four sections, so you can restyle each surface independently:

That granularity is the real power of the advanced editor: you can leave most of a theme alone and surgically rework just the Solutions article view, or just the new-ticket form, without touching everything else.

Multi-product portals

If you support more than one product or brand, you don't need multiple Freshdesk accounts. Per Freshworks' multiple-portals documentation, you can spin up a separate branded portal per product, each with its own URL, its own theme, and its own knowledge base — and you can restrict solution and forum categories so each portal only shows the content relevant to that product.

The plan gating matters here. Multiple products are available from the Estate plan onward in the older Freshdesk plan structure; on the current Pro plan you can create up to 5 products, and on Enterprise you get unlimited products. So a company with three product lines can give each one a distinct portal experience — different logo, different palette, different help center — all administered from a single Freshdesk instance. Just note that each portal is themed independently, so a consistent brand system across five portals is real, repeatable work.

The honest limits — and where an AI layer picks up

Freshdesk's theming is genuinely capable. The gallery gives you a running start, basic customization covers most branding needs without a developer, and the Liquid code editor gives front-end teams real control over 17 pages. Credit where it's due: for shaping how the portal looks, this is a solid, well-documented system.

But be clear about what a theme is and isn't. A theme controls presentation, not answers. A beautifully branded help center still depends on the underlying solution articles being complete and findable — if the content is thin, no amount of CSS fixes the deflection rate. Advanced customization is also Pro-and-Enterprise-gated, so smaller teams are capped at colors and fonts. And Liquid editing is a maintenance commitment: custom themes can drift or break when Freshdesk updates the platform, and every one of your multi-product portals has to be maintained separately.

Most importantly, the portal's job is to reduce tickets, but it does nothing for the ones that still come through. That's the seam where an AI agent layer fits — and it's worth weighing the build-versus-buy tradeoff honestly before you reach for one. The broader category of AI agents for customer service exists to do the reasoning a static help center can't: understanding a messy question, pulling the right answer, and replying.

Macha is one such layer, and it's explicit about staying in its lane: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk, your portal, or your themes. You connect Macha to Freshdesk with your subdomain and API key, and it reads the same knowledge base your portal publishes to draft or post grounded replies on the tickets that get submitted anyway. It can look up an order or account status through a custom tool that turns a REST API into something the agent can call, and it triages incoming tickets by intent — the kind of work covered in how to automate Freshdesk with AI. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: use Freshdesk themes to make the portal look like your brand and organize self-service well, and layer an agent on top for the part a theme can't do — actually answering the tickets your beautiful portal still funnels through. If you're also tuning when those tickets get worked, business hours and SLA timing are the next lever, which we cover in Freshdesk business hours explained.

FAQ

Where do I customize my Freshdesk portal theme? Go to Admin → Portals, click edit next to a portal, and open the Appearance tab. There you'll find your current live theme (Marina by default), an Available themes gallery, an Import theme option, and a live preview.

What's the difference between basic and advanced portal customization? Basic customization is no-code: you change colors and fonts through a visual palette. Advanced customization opens an in-built code editor for HTML, CSS, and Liquid so you can restructure page layouts. Advanced customization is available on the Pro and Enterprise plans, not Free or Growth.

What is Liquid in Freshdesk themes? Liquid is the templating language Freshdesk uses to render dynamic portal content. In advanced customization your Layout must include the {{ header }}, {{ footer }}, and {{ content_for_layout }} placeholders, and you can drop in ready-made snippets like {% snippet login_form %} and {% snippet new_ticket_form %}.

Can I have a different portal theme for each product? Yes. Freshdesk supports multiple branded portals — a separate portal, URL, theme, and knowledge base per product. Multiple products are available from the Estate plan onward; the current Pro plan allows up to 5 products and Enterprise allows unlimited. Each portal is themed independently.

Can I add AI to my Freshdesk portal without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing portal and themes — it doesn't replace them. It reads your published knowledge base to draft grounded replies to the tickets your portal collects, while Freshdesk stays the system of record for your help center and its theming.

Ready to back a branded portal with fast, grounded answers? Start a free trial of Macha and connect it to your Freshdesk in minutes.