November 5, 2026 · 7 min read

Customizing the Shopify Horizon Header and Menus Without Editing Core Theme Files

Learn how to customize the Shopify Horizon theme header and navigation menus using CSS variables, app embeds, and custom sections without touching core

Customizing the Shopify Horizon Header and Menus Without Editing Core Theme Files

You can reshape Horizon's header and menus without touching a single vendor-owned file, by working through four layers: Theme Settings, the Custom CSS fields in the editor, app embed blocks targeting the header section group, and a parallel custom section that replaces the header only in your JSON templates. Done correctly, every change survives a Shopify-pushed theme update. Done incorrectly, you are manually re-applying patches every few weeks.

Key takeaways

  • Horizon's header exposes CSS custom properties like --header-background and --menu-top-level-font-size-desktop that you can override without editing any file.
  • The header section's built-in "Custom CSS" field in the theme editor is scoped to that section and survives updates.
  • App embed blocks can target the sectionGroup:header surface, letting you inject announcement bars or nav widgets with zero file edits.
  • When you need structural HTML changes (extra menu, tabs, mega-menu), create a custom.header.liquid section and swap it into JSON templates rather than modifying the vendor header.liquid.
  • Since 1 October 2026, apps can no longer create or update storefront script tags; every nav widget that used script injection must now use theme app extensions.

Why Horizon makes this harder and also easier than Dawn

Horizon launched as a family of ten free themes at Shopify Editions Summer '25. It runs on Web Components rather than plain Liquid rendered server-side, and it ships a blocks/ directory full of reusable theme blocks that nest up to eight levels deep. That architecture is genuinely more powerful for merchants, but it creates a specific problem for developers: a lot of the header behavior lives inside custom elements (<header-component>, <header-drawer>) whose internal DOM is partially isolated. The old pattern of querying a <select> for a variant and listening for change does not work the same way, and the same logic applies to event-based menu scripts.

The good news is that Horizon's authors leaned heavily on CSS custom properties for all visual tokens. That is your first tool, and it costs zero file edits.

Layer 1: CSS custom properties via Theme Settings > Custom CSS

Open the theme editor, click the cog icon (Theme Settings), scroll to Custom CSS, and drop rules there. This field writes into an inline <style> block injected by Shopify; it is not part of any vendor file, so it does not get overwritten on update.

Useful properties for the header:

/* Make top-level nav items larger and always white */
overflow-list {
  --menu-top-level-font-size-desktop: 1.25rem; /* default ships at 1.125rem */
  --menu-top-level-font-size: 1rem;
}

/* Force a solid background, remove the scroll-transparency effect */
header-component#header-component {
  --header-background: #ffffff;
}

/* Kill the submenu hover fade */
header-component#header-component
  .header__underlay.header__underlay-closed {
  background: transparent !important;
}

Font-family tokens live in snippets/theme-styles-variables.liquid in the vendor files. You can override them without opening that file:

body {
  --font-heading-family: 'YourFont', sans-serif;
}
.header__menu-item,
.menu-drawer__menu-item {
  font-family: var(--font-heading-family);
}

If you need the override scoped to only one section, use the section-level "Custom CSS" field inside the Header section panel instead of Theme Settings. That scope is narrower and less likely to bleed into other components.

Layer 2: App embed blocks targeting the header surface

This is the correct path for adding third-party nav widgets, announcement bars, or trust badges near the header. As of 1 October 2026, storefront script tags are deprecated; Shopify stops running them on 1 March 2027. Anything that previously injected itself via a script tag pointing at the header DOM must now be a theme app extension.

In your extension's block schema, you can target the header section group directly:

"target": "sectionGroup:header"

This tells Shopify to offer the block inside the Header section in the editor, without the merchant needing to place it manually on every template. The merchant activates it once under Theme Editor > App Embeds, and it appears globally. No theme.liquid edits required.

For a mega-menu app, the DOM insertion approach works at the CSS selector level: the Horizon header's outermost wrapper carries the class .header-section, which you can target with an Insert After rule, dropping your menu below the header on desktop without binding to any internal Liquid structure.

Layer 3: Structural changes via a parallel custom section

This is where most teams get it wrong. They open sections/header.liquid, add a second link_list setting and a secondary menu block, save, and move on. That works until Shopify ships a Horizon update. Because Horizon is a free, Shopify-maintained theme, updates arrive frequently, and your edits live in the same file the update wants to overwrite.

The upgrade-safe pattern:

  1. Leave sections/header.liquid completely untouched.
  2. Create sections/custom.header.liquid. Copy the parts of the vendor header you need, then add your structural changes there.
  3. In each JSON template (index.json, collection.json, product.json, etc.), swap the header section reference to custom.header.

A minimal example for adding a secondary explore menu to the drawer:

{%- comment -%} sections/custom.header.liquid {%- endcomment -%}
{%- assign shop_handle    = section.settings.menu -%}
{%- assign explore_handle = section.settings.explore_menu -%}

{%- if linklists[shop_handle] != blank -%}
  {# render primary nav #}
{%- endif -%}

{%- if linklists[explore_handle] != blank -%}
  {# render secondary panel #}
{%- endif -%}

{% schema %}
{
  "name": "Custom Header",
  "settings": [
    { "type": "link_list", "id": "menu",         "label": "Main menu" },
    { "type": "link_list", "id": "explore_menu", "label": "Explore menu" }
  ]
}
{% endschema %}

The drawer JavaScript lives in assets/header-drawer.js, which is a custom element registration. If your tab-switching logic only toggles CSS classes and visibility, you can write a separate assets/custom-header-drawer.js that is included only by your custom section, leaving the vendor JS file clean.

Always duplicate the theme before any code edit. That is not a cliche: Horizon ships as a free Shopify theme, meaning Shopify can push an update to your live theme if you have auto-updates enabled. Check your theme settings and disable auto-updates the moment you have committed code to the theme.

Layer 4: Scoping custom block CSS properly

Horizon uses block IDs to scope styles. Every custom block you build should follow the same pattern to avoid selector collisions across the eight levels of nesting the theme supports:

{%- assign block_id = 'custom-header-' | append: block.id -%}
<div id="{{ block_id }}">
  {# block markup #}
</div>

{% style %}
  #{{ block_id }} {
    /* scoped rules only */
  }
{% endstyle %}

This mirrors what Horizon's own AI block generator produces when Shopify Magic writes a block for you: it assigns a unique ID and prefixes every selector. Following the same convention means your custom blocks behave consistently alongside generated ones.

Comparison: approaches to Horizon header customization

ApproachWhat you editSurvives theme update?Good for
Theme Settings Custom CSSNothing (inline style)YesColor, font size, spacing tokens
Section Custom CSS fieldNothing (inline style)YesScoped header-only style overrides
App embed blockExtension file onlyYesThird-party widgets, announcement bars
Parallel custom sectionYour own section fileYes (vendor file untouched)Extra menus, structural HTML changes
Edit vendor header.liquid directlyVendor fileNo, manual re-patch on each updateAvoid unless no other path exists

Verifying the result

After any change, check three things:

  • Theme editor preview: Open the header section in the editor and confirm your settings panel still loads. If a section's schema is broken, the editor silently drops the section and the merchant loses controls.
  • Mobile drawer: Horizon's <header-drawer> is a separate custom element. Open DevTools, switch to the Elements tab, and confirm your injected markup appears inside the correct shadow boundary (or outside it, if you are targeting the host element with CSS custom properties).
  • Update simulation: Install a fresh copy of the same Horizon sibling theme (Atelier, Pitch, Vessel, etc.) into your development store. Apply the same changes. If your approach works in two minutes on a fresh copy, it is portable and update-safe. If it requires hunting through vendor file line numbers, it is not.

For a detailed look at how theme blocks and content_for 'blocks' work inside Horizon sections, see Shopify Horizon Theme Blocks Explained.

A note on the header section group and app block limits

As of February 2026, a single theme app extension can include up to 30 app blocks, raised from the previous limit of 25. If you are building an in-house app that injects header content across multiple surfaces, that raised ceiling gives you headroom. The sectionGroup:header target means your blocks appear in the editor next to the native header controls, which is where merchants look for them.

If you are maintaining a catalog with many SKUs and many templates, the JSON template approach pays back quickly: you edit custom.header.liquid once and it reflects everywhere, with no risk of a Shopify update quietly reverting your nav changes on the vendor file. That consistency matters more than it sounds when you are managing updates across multiple active themes in a development workflow.

If you need this built rather than doing it in house, Lintel, the studio I run, takes on Shopify theme development projects like this.

Frequently asked questions

Can I customize the Shopify Horizon header without editing any theme files?

Yes. For visual changes like colors, font sizes, and spacing, use CSS custom properties in Theme Settings > Custom CSS or in the header section's own Custom CSS field. Neither of those fields is part of a vendor-owned file, so they survive theme updates. For structural changes like adding a second menu, create a parallel custom section file and reference it in your JSON templates, leaving the vendor header.liquid untouched.

What CSS custom properties does Horizon expose for the header?

Key ones include --header-background for the background color, --menu-top-level-font-size-desktop for desktop nav item size (default 1.125rem), and --menu-top-level-font-size for mobile. These are set on the overflow-list and header-component elements and can be overridden from any Custom CSS field in the theme editor without touching vendor files.

Will my Horizon header customizations break when Shopify pushes a theme update?

Only if you edited vendor files directly. Changes made through Custom CSS fields, app embed blocks, or your own parallel section files are stored separately from vendor code and are not overwritten by updates. If you must edit a vendor file, duplicate the theme first and disable auto-updates in your theme settings to give yourself control over when updates are applied.

Seven years of Shopify, on one page.

Roles, projects, stack and certifications are on the resume.

Resume Download PDF LinkedIn