Order of CSS files. Load module's CSS before theme's CSS

Order of CSS files. Load module's CSS before theme's CSS

August 8, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Order of CSS files. Load module's CSS before theme's CSS

Changing the Order of CSS Files: Loading Module CSS Before Theme CSS

When working with Magento, you might find that the order of CSS files gets loaded on your frontend pages incorrectly. By default, Magento loads theme CSS before any module (extension) CSS, which can lead to style conflicts or overridden styles. In this post, we’ll explore how to change this order and ensure that your module’s CSS is loaded before your theme’s CSS.

Understanding the Default Behavior

Before we dive into solving the issue, let’s first understand how Magento loads CSS files by default:

  1. Theme CSS: This is typically loaded on all pages via the default.xml layout file in your theme folder.
  2. Extension CSS: Each extension can have its own CSS file that gets loaded based on the specific page type it’s registered for.

The order of loading is as follows (by default):

/default/mytheme/css/styles.css
/default/mytheme/css/theme.css
/default/myextension/css/extension.css

As you can see, the theme CSS (theme.css) is loaded before any extension CSS. This might cause issues if your extension has styles that should take precedence over the theme’s styles.

The Desired Order of Loading

What we want to achieve is a reversed order:

/default/mytheme/css/styles.css
/default/mytheme/css/extension.css
/default/mytheme/css/theme.css

In this desired scenario, our module’s CSS (extension.css) would be loaded before the theme CSS.

How to Force This Order

To override the default loading order, you need to carefully manage how your extensions and themes register their CSS files:

Theme CSS Registration

Ensure that your theme registers its CSS file in the default.xml layout file. The code snippet looks like this:

<reference name="head">
    <action method="addItem">
        <type>skin_css</type>
        <name>css/theme.css</name>
    </action>
</reference>

Extension CSS Registration

In your module’s XML layout file, register the CSS file. For example, if you want to load the CSS on category pages:

<catalog_category_layered>
    <reference name="head">
        <action method="addItem">
            <type>skin_css</type>
            <name>css/extension.css</name>
        </action>
    </reference>
</catalog_category_layered>

The Trick: Prioritize Your Module

The key to ensuring your module’s CSS loads before the theme CSS lies in how you structure and deploy your modules. Here are some best practices:

  1. Keep your extensions simple: Smaller, focused modules are easier to manage and prioritize.
  2. Use dependency injection: If possible, use Magento’s DI system for loading your assets instead of relying on layout files. This gives you more control over the order of loading.

Remember, Magento loads CSS in a specific order based on the module structure and dependencies. You can’t directly force an order through XML alone—you need to structure your code appropriately.

Conclusion

Changing the order of CSS files loading in Magento requires careful management of how your themes and extensions register their assets. While there isn’t a direct “force” method, understanding the process and structuring your code appropriately is key.

By keeping your modules simple, using DI where possible, and following best practices for asset registration, you can ensure that your module’s CSS loads before your theme’s CSS without having to resort to complex hacks or workarounds.

Extensions Themes Orders Errors

Our network