Before You Start
Confirm which platform or email client you will use.
Confirm whether you need a visual export (PDF or PNG) or an HTML export.
If you need a download option added to your instance, contact support.
Where to Find Download Options
Open the asset you want to export.
Open the Actions menu and hover over Download.
Select the download option that matches your platform or output.
Platform-Specific HTML Downloads
Use these options when you will paste or upload HTML into a marketing automation platform. These downloads apply platform-specific formatting rules and merge tag handling.
Platform-Specific HTML
Download Option | Description / Notes |
Marketo | Standard Marketo HTML format. Dynamic content renders default variants only. |
New Marketo Editor | Optimized for Marketo’s newer email editor. |
Pardot, HubSpot, SFMC, Eloqua | Platform-specific HTML formatting for each tool. |
Adobe Campaign, Braze, Responsys, SAP Marketing Cloud, SendGrid, Acoustic | Email platform–specific HTML variants. |
Veeva CRM | Life sciences CRM–specific HTML format. |
Gen Studio | Optimized for Adobe Gen Studio. |
Custom Platforms | HTML tailored to custom platforms configured for your company. |
Tip: If dynamic content does not appear as expected in your platform, confirm how that platform handles variants.
Generic Downloads
Use these options when you want standard HTML output. Use Outlook-specific options when the email will be used in Outlook.
Download Option | Description / Notes |
Download HTML | Standard HTML output. |
Download HTML (with details) | Standard HTML with the email details at the top, such as the subject line and from name. This matches what the standard PDF shows. |
Download HTML for Outlook | Optimized for the Outlook email client. |
Download HTML for Outlook Attachment | Use this with the “attach HTML” feature in Outlook. |
Visual and Document Downloads
Use these options when you need a file you can share or review visually.
PDF and PNG Options
Download Option | Description / Notes |
Download PDF | PDF version of the asset. |
Download PDF (mobile) | Mobile-optimized PDF. |
Download PDF without details | PDF without the email details, such as the subject line and from name. |
Download PDF (Pages) | Splits the asset across Letter-size pages (8.5 x 11 in). The standard PDF is one long page. |
Download Mobile PDF (Pages) | The mobile PDF, split across Letter-size pages (8.5 x 11 in). |
Download PNG | PNG image of the asset. |
Download PNG (mobile) | Mobile-optimized PNG image. |
Download PNG for External Review | A PNG for review outside Knak. Knak’s tags are swapped for tags that external approval tools use. |
Download Mobile PNG for External Review | The mobile version of the external review PNG. |
Tip: Use mobile variants when the asset is designed for small screens.
Special Downloads
Use these options when you need a ZIP package or a specialized output for a specific workflow.
Download Option | Description / Notes |
Veeva CRM Zip | Packaged ZIP file for Veeva CRM. |
Dynamic Content Variations PDFs | A PDF that shows all dynamic content variants. By default, this PDF is built from images, so its links do not work. Contact support to turn on Compose from PDFs if you need working links. |
Download HTML of DC Variants page | The HTML of the page used to build the Dynamic Content Variations PDF. |
Download HTML for Composer | A ZIP file with the email HTML and a separate text file of macros. |
Download Zip Package for Gamma | A ZIP file with an HTML file and a plain-text file for the email. It also includes one of each for every translation. Image alt text can be removed from the plain-text files. Contact support to turn this on. |
XLIFF for Translation | An XML Localization Interchange File Format (XLIFF) file. Use it to send content out for translation. Learn more in Using XLIFF Translations. |
Plain HTML vs. Platform-Specific HTML
The download option you choose affects how Knak prepares your HTML for use outside Knak.
Platform-Specific HTML
Choose a platform-specific download when your destination platform is supported by Knak.
Knak adapts your asset to meet the requirements of the selected platform. Depending on the platform, this can include:
Converting merge tags and personalization to the platform's syntax.
Adjusting dynamic content to work with the platform.
Configuring link tracking for the platform.
Updating image paths as needed.
Adjusting the HTML structure to meet platform requirements.
This reduces the manual changes you need to make after downloading your asset.
Plain HTML
Choose Plain HTML when you need the base Hypertext Markup Language (HTML) from Knak.
Plain HTML is not converted for a specific platform. It includes:
Standard HTML generated by Knak.
Knak's merge tag syntax, such as
{{First Name}}.Default dynamic content formatting.
Generic link and tracking structures.
No platform-specific HTML adjustments.
You may need to manually update the HTML before using it in another platform.
Which Option Should You Choose?
| Platform-Specific HTML | Plain HTML |
Best for | Platforms supported by Knak | Unsupported platforms or custom workflows |
Merge tags | Converted for your platform | Uses Knak syntax |
Dynamic content | Adapted for your platform | Uses the default format |
Link tracking | Configured for your platform | Uses a generic structure |
HTML structure | Adapted for your platform | Uses the base Knak HTML |
Manual changes | Usually minimal | May be required |
Choose a platform-specific download when your destination platform is available in Knak.
Choose Plain HTML when you need to customize the HTML yourself or use it with a platform that Knak does not support.
Troubleshooting
Check for Adobe Target Code (Landing Pages Only)
Adobe Target code in your landing page is a common cause of blank PDFs. Adobe Target is a tool that shows personalized content on your page. Its code can hide your whole page while it loads. This stops visitors from seeing the page change. Adobe calls this “flicker management.”
Knak takes a snapshot of your page to make the PDF. If your page is still hidden when the snapshot happens, the PDF may come out blank. This check only applies to landing pages.
Important: Do not publish or sync your landing page while the Adobe Target code is removed. If you do, your live page will not have Adobe Target.
Adobe Target code can be in either of these fields:
Custom HEAD HTML
Header tracking
Your team may have added it, or your Knak admin may have set it as a default for your brand. Check both fields.
Adobe Target usually adds two pieces of code:
Code | What it does | What to look for |
Adobe Target library | Loads Adobe Target. It can also hide the page by itself. |
|
Pre-hiding snippet | Hides the page until Adobe Target loads. |
|
To test if Adobe Target code is the cause:
Open your landing page.
Click the Info tab in the editor toolbar.
Go to Advanced Settings.
Check the Custom HEAD HTML field and the Header tracking field for Adobe Target code. Use the table above to find it.
Copy any Adobe Target code you find and save it somewhere safe. Note which field it came from. Then delete it from the field.
Click Save.
Open the Actions menu and hover over Download.
Select Download PDF.
Paste the Adobe Target code back into the field it came from. Click Save.
If your PDF downloads correctly in step 8, the Adobe Target code was the cause. Each landing page has its own settings, so check every landing page that uses Adobe Target, including cloned pages.
Tip: If the Custom HEAD HTML field is locked or greyed out, you may not have permission to edit it. Ask your Knak admin for help.
To learn more about how Adobe hides the page, see:
How does at.js Manage Flicker? (for
at.js)
Try General Troubleshooting
Your browser can also cause a blank PDF. Follow the steps in General Troubleshooting. This includes clearing your cache, turning off browser extensions and trying a different browser.
If general troubleshooting and removing the script do not fix the problem, contact Knak Support.
Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com.