It's easy to export send-ready HTML code that's ready to load into your sending platform.
Get your final code back, ready to load into your email platform. If you have made multiple versions, you can export an HTML file for each version. To make it easier for some platforms, exports also include one file with all the versions in.
If you need to print your design, or send over a comp to other stakeholders, you can export desktop and mobile screenshots.
If your email platform will import HTML from a hosted URL, you can temporarily host your email code.
When exporting to a connector, you can optionally include your folder path in the export name to maintain your folder-based organisation in external systems.
A new "Include folder hierarchy in name" checkbox on the connector export page prepends the mailing's folder path to the export name using an underscore separator. For example, a mailing called "Welcome Email" inside the folders Europe > UK would be exported as Europe_UK_Welcome Email.
This toggle only appears when the mailing belongs to a folder and the Folder Hierarchies feature is enabled for your organisation. The default is off, so existing export behaviour is preserved unless you opt in.
Set a per-version image-size budget for your organisation and Taxi will stop oversized mailings before they reach your sending platform — protecting your CDN egress, your inbox-rendering experience, and your deliverability.
When the limit is set and a version exceeds it, the existing expectations banner surfaces the violation with the version's current total alongside the configured ceiling. The check covers both uploaded images and externally hosted ones referenced from src.
Exports are then hard-blocked from every export entry point (Download HTML, ESP connector exports, URL exports, and scrape exports). The user is redirected back to the export options page with a flash message describing the breach so they can find and shrink the offending image.
The limit is org-wide and configured per organisation. Contact support or your account manager if you'd like a ceiling set for your organisation.
See your email's HTML size as you build, and stop oversized versions before they clip in Gmail (around 102 KB). A live size chip in the editor toolbar shows your version's current HTML weight, and admins can set an org-wide ceiling enforced at export — the HTML counterpart to the Total Image Size Limit on Exports.
A size chip pinned to the editor's top action bar, next to the actions menu, shows your version's current HTML weight and refreshes as you save, with ok, warning, and over colour states keyed to how close you are to the limit.
Admins choose how the limit is enforced: off simply surfaces the size, warn flags it at export, and block hard-blocks oversized versions from every export entry point (Download HTML, ESP connector exports, URL exports, and scrape exports), redirecting back to the export options page with a message describing the breach.
The limit and enforcement mode are set once under Organisation Settings, and every version in your organisation inherits the same guardrail.
Ship the same mailing to multiple destinations — each with its own subject line, preheader, and merge-tag overrides — without forking the version. The Custom HTML connector gives admins per-export overrides without changing the source content.
Org admins can create as many named Custom HTML connector instances as they need. Each instance adds its own column to the Personalisation editor, so per-token overrides are clearly attributed to the destination they belong to. The instance then appears as its own card in the mailing's Export menu.
At export time, the connector's values are substituted into subject, preheader, and any <esp-personalization> tags in the body, falling back to each token's default value when blank. The result is a standard HTML zip — ready to upload anywhere.
Note: Connectors are enabled per organisation — contact support or your account manager to add the Custom HTML connector to your account.
Need to integrate Taxi into your existing systems? The Taxi API lets you programmatically push and pull content, render emails, manage modules, and automate your email workflow. Learn more about the API or explore the full API documentation.
Connect Taxi directly to your sending platform, for one-click exporting and in-depth segmentation.
We're constantly developing new ESP connectors, that enable direct connections to your sending platform.
Until these are live, it's easy to export send-ready code from Taxi and upload into your sending platform.
Using an ESP not on this list? let us know!
