Newsletter Issue Composer
Write one issue. Keep the HTML, plain text and links together.
Your writing stays in this tab. No autosave, AI calls or uploads. Download JSON to keep a draft; reload clears it. The host receives ordinary page and asset requests.
Version 1 · 200 KB maximum. A valid import replaces the current draft after confirmation. Invalid imports leave it intact. Incomplete drafts can be saved.
Issue preview
Browser preview only. Email clients and provider styling may differ.
Add an issue title and a card heading and paragraph to preview.
Paste the fragment into an existing email content block. Keep your provider's unsubscribe, address and footer.
Link inventory checks syntax, duplicate destinations and missing labels. It never checks reachability, HTTP status or safety.
Loading local composer…
Use the content fragment
Keep your existing email template. This tool formats the text you supply; it does not generate or fact-check your writing.
- Write a title and 1–12 ordered cards. Review the preview and warnings. Save JSON for the next issue.
- Choose HTML content fragment and copy it. In Kit's existing email editor, add an HTML Block, select Edit, paste the fragment and Save.
- Retain the platform's existing footer, unsubscribe link and address. Review its preview and run your own authorized test send before sending.
- Use the plain-text edition as a fallback and the link inventory to check omissions. Other platforms may restrict custom HTML by plan.
Limits and page QA
Is this a complete email template?
No. The HTML fragment has inline CSS and table-based content structure. It has no document wrapper, inbox preheader, tracking, images or provider footer. The standalone preview download is a local viewing document, not a sending-ready template.
Are Kit or email clients tested?
Kit officially documents HTML blocks and inline CSS. No account insertion or test email has been performed. Browser preview cannot establish dark-mode behavior, Outlook/Gmail rendering, deliverability or universal compatibility. Mailchimp custom-template import requires Standard or higher; this tool does not bypass that requirement.
What is validated?
Required issue/card text, the 1–12 card limit, explicit HTTP(S) URL syntax and the versioned JSON schema. Missing link labels and duplicate destinations are warnings. Entered query strings stay intact. No link is fetched or certified safe. Arbitrary HTML is escaped as text.
Can I keep or replace a draft?
Save JSON explicitly. A valid import, example or reset asks before replacing your draft. Bad imports do not replace it. No account, storage or subscriber list is used. Keep downloaded files private if your issue is private.
Kit: HTML blocks · Mailchimp: custom template import. Official steps checked November 3, 2026.