Auto-Generate Hero Images for Beehiiv (2026)

Beehiiv has a public API that supports post creation with images, and a native AI image generator inside the editor, so automating hero images is more possible here than on most newsletter platforms. The catch is that the image generator and the API don’t talk to each other. Full automation still needs a bridge tool that reads your draft URL, generates a matching image, and hands Beehiiv a link.

Writers on Beehiiv lose more time to featured images than almost any other part of publishing. Emails with images get 42% higher click-through rates than text-only emails, and over 70% of emails are opened on mobile, where a weak thumbnail tanks engagement before readers even see the subject line. That makes the cover image the second hardest-working asset in your newsletter, right after the headline, and we saw similar patterns when we looked at whether blog images actually move the needle for traffic and engagement. Most Beehiiv writers are still creating them by hand, one at a time.

Can you automate Beehiiv hero image generation?

Yes, but with one important caveat. Beehiiv exposes a public REST API, and that API’s Create Post endpoint accepts image blocks with URL references, so you can programmatically attach a hero image to a new draft. Beehiiv’s own native AI image generator, however, is editor-only and can’t be triggered through the API. So “automation” in 2026 means either generating your image in the editor manually, or using an external tool that produces an image URL you can hand to the API.

The fully automated path exists but is narrow: you need the Enterprise plan to access the Create Post endpoint, you need an image generation tool that returns a public URL, and you need a way to stitch them together. Writers on any other plan can still automate the creative work with a URL-in tool like imghero, then do a ten-second manual upload. This is the same semi-automation ceiling covered in our broader guide to automating blog hero images and the Substack version of this workflow, but Beehiiv extends it further if you’re on Enterprise.

Why Beehiiv writers struggle with featured images

The friction is structural. Beehiiv’s editor has a native AI image generator, which sounds like the problem is solved, but it still requires you to write a prompt for every post. Research on prompt engineering from 2025 found that expert prompts succeed on the first try only 40 to 60 percent of the time, and reaching 85 percent satisfaction typically takes three iteration rounds. That matches what Beehiiv writers report: most hero images from the built-in tool need two or three tries before one lands.

The stock photo fallback isn’t much better. Beehiiv integrates Unsplash directly in the editor, which is fast, but it guarantees the duplicate-image problem. After a month, you’ll spot the same Unsplash photo on three other Beehiiv newsletters in your niche, and that’s a real brand problem, not just an aesthetic one. Readers in a crowded niche recognize a publication by its images before reading the title, so sharing visuals with five other newsletters actively works against the brand recognition that drives paid conversions.

Beehiiv itself has scaled fast. The platform sent 28 billion emails in 2025, serves 255 million monthly unique readers, and passed $30M ARR with 90,000+ active publishers. That scale also means the Unsplash pool is getting more saturated, not less. The writers who stand out in the Notes feed and in reader inboxes are the ones whose images look made for the post rather than borrowed from a stock library.

The Getty Images integration Beehiiv rolled out to Max and Enterprise plans in early 2026 helps with licensing and quality, but caps at 3 credits per month on Max and 10 on Enterprise. A weekly publisher burns through that in two weeks, and the credits don’t roll over.

What are Beehiiv’s featured image requirements?

Beehiiv recommends hero images at 1,200 by 630 pixels, a 1.91:1 aspect ratio. This is the same dimension Beehiiv uses for post thumbnails, email header images, and social previews, which simplifies things compared to Substack’s three-different-ratios rule. JPG, PNG, and GIF are supported; WebP is not officially confirmed.

Here’s the full specification, pulled from Beehiiv’s official help docs on adding thumbnails and images:

One practical note: Beehiiv displays thumbnails in its RSS feed by default, so if you syndicate your newsletter anywhere that consumes RSS (Feedly, a personal site, Zapier flows), the thumbnail flows downstream automatically. You can toggle it off in RSS settings if you’d rather not. Don’t embed text in the image, since Beehiiv stacks your post title above it and the email client renders at whatever width the reader’s device allows.

Four ways to generate Beehiiv hero images in 2026

There are four realistic approaches for Beehiiv in 2026. They differ less in raw output quality than in how much of your time they eat and whether they fit into an automated workflow.

Unsplash is the fastest option on day one and the slowest over a year. Readers in your niche will see the same images on competing newsletters, and your visual identity blurs into the pack. For a one-off post that’s fine. For a weekly publication building a brand, it’s a real cost that compounds.

Beehiiv’s native AI generator works well if you enjoy writing prompts and have 15 minutes per post to spare. It supports seven styles (Photorealistic, Digital art, Comic book, Neon punk, Isometric, Line art, 3D model) and generates inside the editor without leaving the page. The catch is that the prompt-writing step scales linearly with your post count, and it can’t be triggered by an API call, so there’s no way to build it into a publishing workflow.

Getty Images gives you real licensed photography inside the editor, which solves the licensing anxiety some writers have about AI-generated imagery. Max plan gets 3 credits per month, Enterprise gets 10. A daily newsletter operator burns through that in two weeks, and credits don’t roll over.

URL-in AI skips the prompt-writing step entirely. You paste the draft URL, the tool scrapes and summarizes the post, writes the image prompt for you, and returns an image. The creative decisions happen automatically, not just the individual clicks. The output URL plugs into Beehiiv’s API for Enterprise users or into a Zapier flow for everyone else.

How Beehiiv’s API handles featured images

Beehiiv’s API expects image URLs, not file uploads. The Create Post endpoint accepts a blocks array where each block can be a paragraph, heading, or image, and image blocks reference a publicly accessible URL. There’s no multipart file upload path. That means any end-to-end automation has to solve image hosting first, then hand the URL to Beehiiv.

Post creation via API is also available to Enterprise customers only, while subscriber management endpoints open up on lower paid tiers. Beehiiv launched API v2 in April 2025 and positions Enterprise tooling as the primary integration path for agencies and multi-publication operators.

For everyone else, the ceiling is semi-automation: generate the image programmatically, then paste it into the editor manually. The upload takes 10 seconds, and the creative work is where time actually goes, so you still get from 15 minutes to under a minute per post.

How to auto-generate a Beehiiv hero image with imghero

The manual workflow takes about a minute once you’ve done it once:

1. Draft your Beehiiv post and copy the URL. Beehiiv generates a preview URL for every draft even before it goes live, which imghero can read. For published posts, use the public post URL.
2. Go to img-hero.com and paste the URL into the input field. Pick a style (more on style selection below).
3. Wait about 30 seconds. imghero scrapes the draft, summarizes the content with an LLM, writes the image prompt for you, and generates the image. No prompt input from you.
4. Download the image. imghero outputs a 1,200 × 675 PNG with full commercial rights and no attribution required. That’s 16:9, which crops about 5% off the top and bottom when Beehiiv displays it at 1.91:1, though for most images the crop lands in empty space and you won’t notice.
5. Upload to Beehiiv. Open your draft, click the settings icon in the editor, and upload the image under Thumbnail. Beehiiv uses the same image for the social preview unless you override it.
6. Optional: override the email header. If you want a distinct image for the email version, upload a second one under the email settings. Most writers use the same image for both.

That’s the ceiling for everyone except Enterprise users. Weekly publishers running this workflow cut featured image time from 15 to 20 minutes per post to under 60 seconds, and get a unique image built around what their post actually says.

Automating end-to-end with the imghero API and Beehiiv API

Beehiiv Enterprise users can automate the full pipeline. The workflow has three steps: generate the image with imghero, poll until it’s ready, then create the Beehiiv post with the image URL in a block.

Step 1: Generate the image. Call imghero’s generate endpoint with your post URL.

curl -X POST https://img-hero.com/api/v1/generate/ \
  -H "Authorization: Token YOUR_IMGHERO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://yourpublication.beehiiv.com/p/your-post-slug",
    "style": "bold"
  }'

The response returns a url_id and an image_url redirect:

{
  "url_id": "url_abc123",
  "image_url": "https://img-hero.com/img/url_abc123/",
  "status": "generating"
}

Step 2: Poll until ready. imghero returns images within about 30 seconds. Poll the URL endpoint every 5 seconds until status is complete, then grab images[0].direct_url for the CDN URL.

curl -s https://img-hero.com/api/v1/urls/url_abc123/ \
  -H "Authorization: Token YOUR_IMGHERO_TOKEN"

Step 3: Create the Beehiiv post. Pass the image URL in a block to Beehiiv’s Create Post endpoint. The image block accepts a public URL, which is exactly what imghero returns.

curl -X POST https://api.beehiiv.com/v2/publications/PUB_ID/posts \
  -H "Authorization: Bearer YOUR_BEEHIIV_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Your Post Title",
    "blocks": [
      {"type": "image", "url": "https://static.img-hero.com/..."},
      {"type": "paragraph", "content": "Your intro paragraph..."}
    ]
  }'

imghero’s API rate limit is 100 requests per minute per token, which is far more than any realistic publication schedule demands. The endpoint costs one image credit per generation, regardless of iterations. Beehiiv’s API uses its own rate limits, documented in their developer portal.

One pattern that works well: a weekly scheduled script reads the URLs of all drafts in your queue, calls imghero for each, waits for completion, and either writes the draft via the Beehiiv API (Enterprise) or saves the image URL to a spreadsheet for manual upload (all other plans). When publishing day arrives, every image is already waiting.

Automating with Zapier (no-code option)

Non-Enterprise users can still build a Zapier flow that removes most of the manual work, even without API access to Create Post. The imghero Zapier integration gives you an image generation step that you can chain into any trigger.

A typical flow:

1. Trigger: new post published in Beehiiv (native Zapier trigger)
2. Action: imghero generate image with the Beehiiv post URL
3. Action: store the resulting image URL in a Google Sheet, Notion, or Airtable for your records
4. Manual step: paste the image into the draft’s thumbnail slot

Zapier doesn’t yet have a native Beehiiv action for updating post thumbnails, so the last step stays manual unless you’re on Enterprise and writing your own API integration. This is the same workflow pattern we cover in detail in our guide to automating blog images with Zapier, just retargeted at Beehiiv’s specific trigger set.

Make.com and n8n both support Beehiiv as well. Make has an official integration launched alongside API v2, and n8n has a community-maintained Beehiiv node. Both follow the same pattern: trigger on a Beehiiv event, call imghero, store or forward the result. The image upload to a draft stays manual for non-Enterprise users regardless of which automation platform you use.

Choosing the right style for a Beehiiv newsletter

Beehiiv’s default visual design leans clean and editorial, which means busy hero images compete with the post title Beehiiv stacks above them. The styles that work best are ones that read clearly at small thumbnail sizes in the web feed, survive mobile cropping in email, and don’t fight the post title for attention.

imghero ships with 18 built-in styles. For Beehiiv newsletters, five are worth knowing:

• bold: high-contrast geometric compositions with strong color blocking. Pops in the feed at small sizes.
• minimal: flat, lots of whitespace. Matches Beehiiv’s default aesthetic for essay and analysis publications.
• illustration: vector-style illustrations. Reads well as a thumbnail and stands out without being busy.
• photo: realistic photography. Best when the post has a concrete subject (a product, a place, a person). Not the right fit for abstract essays.
• neon_geo: neon-accented geometric style. Strong for tech, crypto, and gaming newsletters where you want energy.

Skip anything text-heavy, since Beehiiv already shows the post title above the image. Pick one style and use it consistently across every post. Readers who can identify your publication from the thumbnail alone click more often, and rotating through five styles a month undermines that recognition before it has a chance to build.

One EU-specific note: the EU AI Act’s transparency rules for AI-generated content kick in on August 2, 2026. The obligation sits with the AI tool providers rather than individual Beehiiv publishers, so compliant commercial image services handle the watermarking and metadata upstream. AI-generated imagery also doesn’t carry an SEO penalty, despite the myth that it does.

Frequently Asked Questions

Does Beehiiv have an API for featured images?

Yes, partially. Beehiiv’s API v2 Create Post endpoint accepts image blocks referenced by URL, so you can programmatically attach a hero image to a new draft. Access to Create Post is limited to the Enterprise plan. Other paid tiers get subscriber and publication endpoints but not post creation. Beehiiv’s native AI image generator is editor-only and can’t be triggered via API.

What size should a Beehiiv hero image be?

1,200 × 630 pixels (1.91:1 aspect ratio) is the recommended size for thumbnails, email headers, and social previews. Beehiiv supports JPG, PNG, and GIF. WebP support is not officially documented. The same image works across all three slots, unlike platforms that use different aspect ratios for web and email.

Can I use Zapier to auto-generate Beehiiv featured images?

Zapier can automate the image generation step but cannot yet automatically upload the result to a Beehiiv draft as a thumbnail. The practical flow is: Beehiiv post published trigger, imghero generate image action, store URL in a spreadsheet. The final paste into Beehiiv’s editor stays manual unless you’re on Enterprise and write your own API integration.

Does Beehiiv’s native AI image generator work on all plans?

The native AI image generator is available on every paid plan, but it only works inside the post editor. You can’t call it from the API, from Zapier, or from a scheduled workflow. It supports seven preset styles and generates inline, but it requires a fresh prompt for every post, which is where the time cost actually comes from.

How many hero images can I generate with imghero per month?

imghero’s free tier includes 3 images with full commercial rights and no credit card. Starter (€9/month) includes 20 images, Pro (€35/month) includes 100, Growth (€90/month) includes 300, and Scale (€150/month) includes 600. Unused credits roll over up to 2x the monthly cap. A weekly publisher is covered by Starter for a full year with room to regenerate.

Will AI-generated images hurt my Beehiiv newsletter’s SEO?

No. Google has publicly confirmed there is no ranking penalty for AI-generated images as long as they’re relevant and high quality. We covered this in detail in our myth-buster on AI images and SEO. The EU AI Act’s watermarking rules kick in August 2026 and affect disclosure, not rankings.

---

Beehiiv has more automation surface area than most newsletter platforms, but the image generator and the post API don’t connect on their own. For the 99% of writers not on Enterprise, semi-automation is the realistic ceiling: generate the image in 30 seconds with a URL-in tool, paste it into the editor in 10 seconds, and get the creative hours back. For Enterprise users, the full pipeline is buildable today. If you want to try it, imghero’s free tier covers three images with no credit card. Start here.