How to import an HTML email template into Mailchimp

Mailchimp’s import documentation, checked for this guide on October 26, 2026, lists custom HTML templates as available on Standard plans and above. Check your account first if the import option is missing.

You also need an email-ready HTML file or the source code for the completed email. A screenshot, PDF, or ordinary website page is not the same thing. If you are still preparing the design, use the website-to-email guide to create a version intended for inboxes.

Keep an untouched copy of the export before editing it in another tool. Name it by campaign and version, such as “spring-service-announcement-approved.html.” That gives you a known reference if later changes alter the layout or the links.

The following route follows Mailchimp’s documented custom-template workflow. Account navigation can change; the linked help page is the reference if your labels differ.

1. Open Campaigns → Email templates.
2. Choose Code your own, then the HTML import option.
3. Select your HTML file. If you have source code instead, use the paste-code option.
4. Review the preview and save the template with a recognizable name.
5. Create the campaign from the saved template and complete its audience and message settings.

For a self-contained design that refers to public image URLs, a single HTML file is often the simplest handoff. If your template package includes local assets, use the platform’s documented ZIP process and check its current packaging rules before uploading.

Do not confuse a successful upload with a finished campaign. Importing proves the platform accepted the file. It does not prove that the right audience is selected, that the offer is current, or that a recipient’s name will display correctly.

After saving, give the draft a specific campaign name. Keep the campaign, audience, subject, and offer version recognizable so a second reviewer can verify the same thing you tested.

Imported HTML does not automatically become the same kind of block-based template as a design built inside Mailchimp. Decide where you intend to make changes before the first campaign is reviewed.

For a Cmora-created email, a straightforward workflow is to keep copy and layout changes in Cmora and import the updated export. That keeps one editing source. Otherwise, your team can end up with a Mailchimp version and a Cmora version that look similar but contain different offers or links.

Mailchimp also has a template language for explicitly editable areas. Its editable-area documentation notes that the described options are for the legacy builder. If your team needs that workflow, have a developer prepare and test it deliberately rather than assuming any HTML import will provide it.

For a one-off send, editing the original and exporting again is often easier to manage. For a team maintaining a coded template library, document which areas can change and which must remain intact. Either route benefits from a clear owner for the approved version.

Each sending platform uses its own merge syntax. A first-name field or unsubscribe placeholder copied from another tool may remain visible as raw text or fail to resolve. Cmora’s Mailchimp export adapts the standard greeting and unsubscribe field; any custom fields still need values and matching setup in your sending platform.

Inspect the rendered result rather than merely finding the tag in the code. A record without a first name should get a readable fallback. A custom field such as an appointment date should not appear as an empty label.

Mailchimp’s testing guide says ordinary test emails do not resolve contact-specific merge tags and dynamic content. Use live merge-data preview or a controlled live send to a small test segment you own. An unresolved name in a generic test therefore needs a better test before you conclude that the export is broken.

Send the final draft through Mailchimp and inspect it in the inboxes your customers use. Check the top of the message first: the sender identity, subject, preview, opening explanation, and first action should all agree.

On a phone, confirm that the text remains comfortably readable, the main button is easy to select, and the layout does not require sideways scrolling. Review dark mode and images blocked where possible. A logo that disappears against a transformed background needs attention even if the desktop editor looked correct.

Mailchimp’s HTML limitations guide explains why browser features such as scripts and embedded forms are unsuitable for most inboxes. Use the email to explain and link to the task, with the form, video, or interactive experience on a web page.

Finally, check the actual buying or booking path. For a promotion, confirm the offer still works. For a newsletter, open the article. For a welcome, complete the promised first step. Keep the final test aligned with the version you intend to send.

Make one correction at a time and retest the affected path. Replacing the whole design because one personalized field failed can introduce new problems while leaving the original data issue unresolved.

Once the imported template, audience data, and destination are verified, save the approved version. Use the newsletter design checklist when reusing it for a future campaign; the template may stay the same while content, links, and offers change.