Mautic 7 Logos & Favicon: From Inline SVG to File-Based Assets — What Changed?

Product Support Mautic 7 Install / Upgrade Support
1

Hello,

While working with Mautic 6, I noticed that the application’s logos and favicon were embedded directly in the code as inline SVG elements. These appeared in multiple locations across the UI and templates.

During the development cycle of Mautic 7, I remember seeing a pull request that proposed moving these inline SVG assets to external files, allowing the application to load them directly from the file system instead of embedding them in the code.

The proposed change seemed beneficial for several reasons:

  • Cleaner templates and UI code

  • Easier asset management

  • Simpler customization and theming

  • Potentially improved cacheability of static assets

Now that Mautic 7 has been officially released, I tried to locate the original pull request and any related documentation describing this change. However, I haven’t been able to find clear references to it in:

  • Release notes

  • Documentation updates

  • Developer change logs

Questions for the Community and Core Developers

I’d love to clarify a few things with the Mautic developer community:

  1. Was the change to move logos and favicons from inline SVG to file system assets implemented in Mautic 7?

  2. If so, which files are now responsible for loading these assets?

  3. What are the file system paths used for these logos and favicon assets?

  4. Are there recommended ways to override or customize them?

Understanding this would be helpful for developers and maintainers who customize Mautic interfaces or build custom themes.

Investigating the Code

Of course, the quickest way to confirm the current behavior is simply to inspect the Mautic 7 codebase and see how assets are being loaded now.

However, documenting this change would benefit the wider community. Many developers rely on release notes and documentation to track architectural or UI-related changes like this.

Why This Matters

Small infrastructure changes—like moving assets out of inline markup—can make a big difference for:

  • Theme developers

  • Branding customizations

  • UI maintainability

  • Frontend performance optimization

If this refactor did land in Mautic 7, it would be great to have clear documentation outlining:

  • Asset locations

  • Loading mechanisms

  • Recommended override methods

Final Thoughts

If anyone from the core team or community has insight into this change, it would be great to hear more about it.

Otherwise, I’ll dive into the Mautic 7 source code and trace how these assets are currently implemented.

Either way, documenting the findings should help make future customization and development a bit easier for everyone working with Mautic.

Thanks.

2

Hello,

I wanted to share some feedback after reviewing the recent code changes. I’ve identified that in M7.0.1, the Mautic logos and favicon are now being loaded as file-based assets rather than inline SVG code. This is a positive step forward, and I’d like to thank the developers for their work and effort in making this improvement.

That said, I wasn’t able to find a specific PR documenting these changes, which is a bit unfortunate. I assume they were included under general refactoring, but having clearer traceability would be helpful for those reviewing updates.

I’d also like to suggest that the developers revisit the formatting of the <div> elements surrounding these assets. At present, the styling appears tailored specifically to a circular Mautic icon. It would be beneficial to make this more flexible so that any loaded icon is properly centered, regardless of its shape.

I’m happy to share further details if others are interested or encountering similar issues, particularly if additional developer guidance isn’t available.

Thanks again!