Table & Return exports an individual email draft as HTML or plain text. Export does not send an email or connect a subscriber list. This tutorial explains the website’s export workflow and the checks needed in your own sending platform. No third-party platform import or inbox rendering test is claimed here; available import features depend on the provider and plan.
1. Choose and review the email
Open a free template or review your current AI draft in the generator. Confirm the subject, preview text, headline, paragraphs, and main button. Read the final wording against your actual dish, service, event, and offer terms. A template download uses fictional restaurant details until you replace them. Generator edits are kept in the active page; save an export before refreshing or leaving. A useful starting test is a no-discount menu announcement with one menu link, rather than a complex campaign with several competing destinations.
2. Select Copy text, HTML, or Text file
The action controls offer Copy text for your clipboard, HTML for a downloadable .html file, and Text file for a .txt download. Template filenames follow restaurant-[occasion].html or .txt; the worked example downloads as restaurant-worked-menu-example.html or .txt. These are email content files, not a contact list, campaign schedule, or automatic integration. Copy text includes labels such as Subject and Preview so you can transfer those fields deliberately. If the browser blocks clipboard access, download the text file instead. Check the downloaded file before moving to your provider.
3. Know what the HTML contains
The HTML export includes the subject as the document title, hidden preheader text, the restaurant name, headline, paragraphs, one main action, optional terms, and a footer. It uses presentation tables and inline styling with a content width capped at 600 pixels. The file does not embed the decorative food or dining-room photograph shown on template pages. It does not contain JavaScript or your subscriber list. The subject and preview text may still need to be entered in separate fields in your sending platform; an HTML document title does not set an email subject automatically.
4. Resolve every link and footer placeholder
The generator accepts your main menu or booking URL, postal address, and unsubscribe URL. Free examples deliberately leave placeholders when those details are absent. Without a valid main link, the HTML export shows a reminder rather than a working CTA link. Replace the address and unsubscribe reminders with your actual sender information and your platform’s supported unsubscribe mechanism. Search the exported wording for bracketed reminders and example details. Do not use a generic homepage as a substitute for an unsubscribe mechanism. If the provider uses special merge tags, follow that provider’s current instructions and test a real message.
5. Choose a supported import route
In your sending platform, first check whether your plan supports importing or pasting custom HTML. If it does, use its documented HTML workflow and inspect the result after import. If it only provides a visual editor, copy the wording into its own content blocks, recreate the button with your destination, and set the subject and preview fields separately. Neither route is guaranteed to preserve the Table & Return preview exactly. This guide intentionally avoids naming untested menu buttons or claiming a direct integration. Check the provider’s current instructions for your account, and keep a copy of the source export.
6. Test before scheduling
Send a test through the platform that will actually deliver the campaign. Open it on a phone and desktop, check the subject and preview, read the text with images blocked where possible, and click the menu or booking destination. Confirm that any personalization resolves and that the unsubscribe footer is handled as the provider expects. A local HTML preview checks a file, not inbox compatibility or deliverability. If the imported layout is unsuitable, use the text in the provider’s native editor instead of scheduling an unreviewed file. Keep track of which platform and account plan you tested.
7. Troubleshoot without sending a duplicate campaign
If the HTML opens as source code, confirm whether you are using a code editor or a rendered preview; changing the filename does not add import support to a provider. If the file is missing, check your browser’s downloads and any blocked-download prompt. If the button is absent, review the main destination field: an empty or invalid URL exports a reminder. If the footer contains brackets, complete it in the supported platform workflow. If an import fails, retain the draft and use plain text as a fallback. Generating another AI version is unnecessary for an import problem and would use another credit.
What has and has not been verified
The website’s export functions are exercised by automated checks for text content, HTML escaping, link handling, and footer placeholders. This is narrower than a browser download, a provider import, or delivery into an inbox. No supported-provider list or inbox compatibility guarantee is implied. The worked menu example gives you a public sample to inspect and download without buying credits. Use it as a starting point for your own controlled test, replacing fictional details before any send. Record the test date, provider, and result before describing a platform as compatible.
Continue with a practical next step.
Read the HTML and text export tutorial, inspect the complete worked menu example, or choose a new-menu email template. For live AI writing, follow the generator walkthrough.
For commercial email requirements, start with the FTC's guidance for US businesses and the official rules relevant to your own audience. Our guides are general information, not legal advice or a promise of results.