Adobe Campaign Standard (ACS) offers a convenient feature for uploading HTML content as a ZIP package—containing HTML, CSS, and images with relative paths. While efficient for managing branded emails and landing pages, it often runs into a common font issue, where custom fonts referenced in CSS fail to load properly.

Explore more: Uploading HTML content

While this functionality works seamlessly for standard assets like images and stylesheets, a recurring issue arises with custom fonts. Specifically, fonts that are internally referenced via CSS (using relative paths within the ZIP package) often fail to render correctly in emails or landing pages once uploaded to ACS.

In Adobe Campaign Classic, this limitation is resolved by uploading font files to the Public Resources section and referencing them via their unique MD5-based URLs. However, in Adobe Campaign Standard, there’s no built-in way (as of now) to host custom static assets like fonts, JavaScript files, or external images that need to be publicly referenced from within ACS content. This lack of static asset hosting presents a major roadblock for maintaining brand consistency—particularly for organizations with strict typography guidelines.

Simple Two-Step Solution to Fix the Font Issue in ACS

1. Host Fonts on a Public Web Server
   Upload your brand fonts (e.g., .woff, .ttf, .woff2) to a publicly accessible location—ideally, your corporate website or CDN. Then, modify your CSS to reference these fonts using their full public URLs instead of relative paths.
2. Enable CORS for ACS Domains
   To ensure the fonts load properly in ACS-rendered content, you must CORS-enable the ACS domain(s) on your font-hosting server.
   Cross-Origin Resource Sharing (CORS) allows your ACS instance to securely access font files hosted on a different domain. Your infrastructure or web team will need to add ACS’s domain to the Access-Control-Allow-Origin header on the font-hosting server. Without this, browsers may block the font due to cross-origin restrictions—even if the URL is correct. Check out: Cross Domain Fonts

Once you’ve completed the above steps—hosting the font files publicly and enabling CORS—Adobe Campaign Standard (ACS) will automatically render the correct fonts in your delivered emails (EDMs) and landing pages, with no additional intervention required.

But beyond just solving the immediate font rendering issue, this approach brings several strategic advantages for long-term maintainability and brand consistency:

There are few other benefits of using this approach to address font issue:

1. Centralized Brand Asset Management: By hosting fonts, logo images, base CSS files, and similar brand-specific assets in a single, centralized location (such as your official website or a dedicated asset CDN), you ensure consistent styling across all digital touchpoints. This centralization allows for quick and coordinated brand updates across multiple EDMs, landing pages, or even other platforms—without needing to repackage or redeploy HTML content each time a visual element changes.
2. Environment Independence & Easy Migration: Referencing assets via absolute URLs rather than ACS-relative paths decouples your code packages from specific ACS environments (e.g., Staging or Production). As a result, you can seamlessly migrate your email or landing page content between environments without breaking asset references—ensuring correct rendering and faster QA cycles during deployment.
3. Improved Reusability & Reduced Duplication: Once assets like custom fonts are publicly hosted, they become reusable across multiple campaigns, templates, and teams. This eliminates the need to upload redundant copies of the same files for every package, reducing storage clutter and saving time for your creative and technical teams.

###