In Make, connect an email trigger to HTML/CSS to Image → Create an Image with HTML/CSS, then map the email’s HTML body into the action’s HTML input. The action can produce PNG, JPG, or WebP. Connect a separate HTML/CSS to Image account with its user ID and API key, and test the actual email template: Make documents the conversion capability, not pixel-identical rendering across email clients.
Build the Make scenario
- Add an email trigger. Choose the connector and trigger that match where the message arrives. Make’s generic Email integration includes Watch Emails; Gmail is also available as an email integration. Set criteria to select the messages you want to process.
- Add the image-rendering action. Select HTML/CSS to Image → Create an Image with HTML/CSS. This action takes markup as input. Do not choose Create a Screenshot of a URL unless you want to capture a live webpage rather than render the email’s HTML.
- Connect the rendering service. In the action’s connection dialog, enter the user ID and API key from your HTML/CSS to Image account. Make’s app documentation says this separate account is required.
- Map the HTML body. Run the trigger once, inspect its output bundle, and map the field containing the email’s HTML markup to the action’s HTML input. Connector output labels vary, so select the actual HTML body rather than assuming a field name. Do not map the plain-text body or a link to the message.
- Set the output format. Choose PNG, JPG, or WebP from the formats supported by the action. Use the CSS input and, if needed, the Google Fonts field documented for the app.
- Decide what should happen to the result. Add a downstream module to store, attach, or send the image. If you need to retrieve an image created earlier, Make lists a Get an Image action; its app documentation describes image data in the output bundle’s body. Check what file or data input your destination module expects.
- Run a representative test. Confirm the trigger supplied a non-empty HTML string, inspect the generated image and its dimensions, check remote assets, and verify that the next module received usable image data.
Choose the action that matches your input
| Action | Use it for | Input |
|---|---|---|
| Create an Image with HTML/CSS | Rendering an email whose markup is available in the trigger output | HTML and CSS |
| Create a Screenshot of a URL | Capturing a live webpage | A webpage URL |
| Get an Image | Retrieving an image created earlier | A previously created image reference; output includes image data in the body |
These actions are not interchangeable: an email’s HTML body is markup, not necessarily a public webpage URL. Make lists all three actions in its Email and HTML/CSS to Image integration.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Modern HTML Email (Second Edition) | $13.55 | Buy on Amazon |
| 2 |
|
Create Stunning HTML Email That Just Works | $39.55 | Buy on Amazon |
| 3 |
|
Crafting HTML Email | $6.99 | Buy on Amazon |
| 4 |
|
HTML Examples: Html Workbook | $13.99 | Buy on Amazon |
| 5 |
|
HTML5 HTML Logo, Web Designer Frontend Software Engineer T-Shirt | $18.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Check rendering before relying on the output
Email markup is designed to be displayed by email clients, and the documented Make integration does not promise that this conversion will reproduce how the message looks in any particular client. The cited app pages do not establish support for every CSS feature or remote image, nor do they specify behavior for very long emails. Treat the generated image as an output to validate, not as proof of inbox fidelity.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches- Test the real template, including its longest expected content and any conditional sections.
- Check whether images and fonts referenced remotely appear in the output; the documentation does not guarantee their availability.
- Review the image’s width, height, and readability at its intended display size.
- Compare the output against the email as rendered in the client that matters to your workflow.
Troubleshooting
The HTML input is empty or produces an unexpected result
Inspect a sample trigger bundle and confirm that you mapped its HTML-body field, not the plain-text body or a message URL. Field names and schemas depend on the email connector.
#1 Best Overall
The scenario cannot connect to HTML/CSS to Image
Confirm that you have an HTML/CSS to Image account and that the user ID and API key entered in Make come from that service’s dashboard. The connection is separate from your email account.
Images, fonts, or styling differ from the email client
Check the markup’s CSS and asset references, then test the same template again. Make documents HTML and CSS inputs and a Google Fonts field, but the available documentation does not provide a compatibility matrix or guarantee parity with email clients.
The next module receives no usable image
Check the renderer’s output bundle and the destination module’s expected input type. If you need to retrieve a previously created image, use Get an Image and map the returned image data to a compatible destination field.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The result is not the page you intended to capture
For raw email markup, use Create an Image with HTML/CSS. Use Create a Screenshot of a URL only when you intend to capture a live webpage.
Rank #3
Or skip the browser setup
If your actual goal is to capture a live webpage rather than render raw email markup, ScreenshotNeo can return a screenshot or PDF from one GET request. For example, this saves a WebP screenshot of a page:
Quick Recap
Best Value
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for parameters. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed; and its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo free.
Sources
- Make: Email and HTML/CSS to Image integration
- Make: HTML/CSS to Image integration
- Make: HTML/CSS to Image app documentation
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
