RenderPix
HTML to Image API - Paste HTML, get a pixel-perfect image.
The product changed significantly. The landing page hadn't.
After a full week of updates, I rebuilt renderpix.dev from the ground up.
What changed:
The old hero: "HTML-to-image API"
The new hero: "Turn any HTML into pixel-perfect images — automatically. Built for n8n, Make, and Zapier."
That's not just a copy change. It's a positioning change.
The sandbox:
The biggest improvement. Before: a blank textarea with a Render button.
Now:
- 5 preset templates (Instagram Carousel, OG Image, Certificate, Invoice, Custom)
- Template variables: fields auto-appear when {{key}} is detected in HTML
- Left column: editor + controls. Right column: live preview.
- "Copy API Code" button — one click to get working code
The goal was to reduce time-to-wow. Pick a template, hit Render, see a real image in 10 seconds. No signup needed.
New sections:
- Trust bar (85+ n8n installs, ~300ms render time)
- Integrations (n8n, Make, Zapier — with real links)
- How it works (3 steps + code snippet)
What I learned:
The old page was developer-first. The new page speaks to both developers AND automation users. Those are different people with different questions.
A developer asks "how does it work?"
An automation user asks "does this work with my tool?"
The new page answers both in the first scroll.
Current state:
- MRR: $9
- Registered users: ~30
- n8n installs: 85+
Next: Reddit distribution and outreach to the ICP.
Building RenderPix in public. It's an HTML-to-image API — you send raw HTML, get back a PNG/JPEG/WebP. No templates, no lock-in.
Where I am right now:
$9 MRR (1 Starter customer)
~15 registered users
2 active free users with real usage patterns
n8n community node live on npm
~20 blog posts + use-case pages indexed on Google
What's actually working:
Reddit is the only channel driving signups right now. Specifically r/n8n — posting real workflow examples (not "check out my tool" posts) gets people to click. One post about Instagram carousel automation in n8n brought 3 signups in a week.
The n8n community node was the right move. Automation users don't want to write API calls — they want a node they can drag in. Usage went up after publish.
What's not working:
SEO is slow. 35+ pages indexed, impressions growing, clicks basically zero. I know this takes time but it's hard to watch.
Cold outreach to active free users — sent 2 emails, one reply, no conversion. Not giving up but response rate is rough.
What I learned this month:
Distribution before features. I spent the first 3 months building things nobody asked for. The month I stopped building and started posting on Reddit, I got my first paying customer.
Also: find the niche your bigger competitors ignore. Rendex (main competitor) is going all-in on AI agents and enterprise. Nobody is talking to the Make.com/n8n/Zapier crowd. That's where I'm focusing.
What's next:
Weekly Reddit posts targeting automation communities
Make.com integration (blueprint ready, needs testing)
Get to 3 paying customers before considering new features
If you're building something similar or using HTML-to-image in your automations, happy to chat.
After weeks of planning and a focused weekend sprint, I just pushed the biggest feature update since launch.
What shipped:
Batch rendering — send up to 50 HTML items in one API call, get 50 images back. Partial failure support (HTTP 207 — failed items don't block successful ones). Plan-gated: Starter gets 10, Pro gets 50, Scale gets 100.
Template variables — use {{placeholders}} in HTML, pass a vars object. No more string interpolation. Available on all plans including free.
Async callbacks — callback_url parameter for fire-and-forget rendering. API returns 202 immediately, RenderPix POSTs the result when done. Pro+ feature.
waitUntil parameter — control when Chromium considers the page "ready" before capturing. load, domcontentloaded, or networkidle.
The motivation:
My only paying customer (Instagram carousel automation via n8n) was calling the API in a loop — one request per slide. Batch was the obvious solution. But instead of building just batch, I built the full automation-native feature set in one sprint.
Current state:
- MRR: $9 (1 Starter customer)
- Registered users: ~21
- n8n community node: 85+ installs
What's next:
- Landing page and docs updated to reflect the new features
- Distribution: blog posts, Reddit, Dev.to
- Outreach to current users about the new capabilities
The product is now meaningfully different from where it was a month ago. The question is whether the distribution can catch up.
-
1
This is a solid product move, especially because the feature sprint came from real usage instead of guessing.
The part I’d be careful with now is treating “distribution” as one big problem.
You already have a narrow signal: n8n installs, one paying workflow, and automation-native features. The risk is spreading the next push across blog posts, Reddit, Dev.to, and current users without deciding what signal you actually need from each.
I would not solve that loosely in the thread because the next move changes depending on whether you’re trying to prove the niche, find more of the same workflow, or move users from installs to paid usage.
If you’re open to it, share your email and I’ll put the tighter customer path together properly.
-
1
Hi, I am very new and still experimenting the moves. Please reach me out from
hello@renderpix.dev
Regards-
1
Sent you a note by email.
I think the customer-path decision matters more than the distribution discussion right now.
-
-
Hey IH! Quick build-in-public update.
We just shipped an n8n community node for RenderPix (our HTML-to-image API).
What it does:
- Convert any HTML to PNG/JPEG/WebP directly in n8n workflows
- Perfect for automating certificates, OG images, Instagram posts
Stats so far:
- 557 npm downloads
- Submitted to n8n verified nodes (4 week review)
- First Reddit post got traction
npm: n8n-nodes-renderpix
GitHub: https://github.com/ozgurdogus/renderpixn8n
Happy to answer questions!
Finding your HTML-to-image API niche through user behavior data.
Posted: May 2026
Status: $9 MRR, 1 paying customer (Starter plan), 2 months in
The Wrong Assumption
I launched RenderPix on March 29, 2026.
My thesis was clear: OG image generation is the pain point. Every SaaS needs social sharing cards for link previews. Template tools like Bannerbear exist, but they're overpriced and restrictive. I'll undercut them 60% with a developer-first, HTML-only API.
I shipped:
✅ HTML-to-image API (PNG/JPEG/WebP rendering)
✅ Pre-warmed Chromium pool (no cold starts)
✅ 4 pricing tiers ($0, $9, $29, $79)
✅ Landing page with live demo
✅ API docs, dashboard, Node.js SDK
I launched on Reddit (r/webdev, r/node, r/SideProject), dev.to, IndieHackers, HackerNews. Got 200-300 visitors/week. ~10 signups. Zero paying customers.
For 4 weeks, nothing.
Then I stopped guessing and looked at the data.
The Data Whispered
One user had rendered 79 times in a single day. Not the OG image use case. Not certificates. Not invoices.
The renders were:
Size: 1080×1350 (Instagram story aspect ratio)
Frequency: Once a day, like clockwork — scheduled rendering
HTML: Dynamic (different each time)
Pattern: Posted to a schedule, probably automated workflow
They were automating social media image generation.
I checked my logs. No OG image usage. No certificate generators. Just one active user, hammering the /v1/render endpoint with dynamic HTML on a daily schedule.
I realized: I'd built the right product for the wrong audience.
The Second Look
I Googled: "n8n automated image generation" and "Make.com social media automation"
The search results were sparse. No native HTML-to-image integrations. People were doing manual workflows:
Create template in Figma/Canva
Export PNG manually
Upload to scheduling tool
But developers using n8n and Make.com? They were looking for:
API-first image generation (not UI-first)
HTML control (not template variables)
Pricing under $10/month
The overlap was tiny but extremely profitable:
Automation enthusiasts (n8n, Make.com communities)
Indie SaaS founders with repetitive automated social content
Small agencies automating client graphics
The fact that my solo customer had found me through organic search and was already using the image rendering API daily told me everything: I didn't need more marketing. I needed the right audience.
What I Did
1. Analyzed the Customer's Workflow
I checked their profile (looked like an agency account).
Their automated rendering pattern:
Always 1080×1350
HTML varied daily (different quotes, colors, CTAs)
Posted consistently Monday-Friday
No API key rotations (stable user)
This wasn't a experimenter. This was someone with a real automation workflow for social media content generation.
2. Doubled Down on Social Media Automation Niche
Created a niche landing page:
/use-cases/social-media-automation.htmlPosted on Reddit in r/nocode, r/automation, r/Zapier communities (not just r/webdev)
Wrote n8n + RenderPix integration tutorials
Added to directories where automation tool enthusiasts cluster: SaaSHub, AlternativeTo
3. Talked to the Customer
I wasn't able to reach my first customer (they went silent after hitting the free tier limit), but I knew their workflow by heart. Every tutorial, every Reddit post, every landing page spoke to them.
4. Kept Building for the Niche
Instead of adding:
❌ Template marketplace
❌ Drag-and-drop builder
❌ Advanced webhook scheduling
I focused on:
✅ Clear API docs for n8n users
✅ Social media dimension presets (1080×1350, 1200×630, 1200×800)
✅ Response headers for quota tracking
✅ Integration examples (Node.js, Python, cURL)
The Result
Within days of pivoting:
My second Starter customer signed up (an active user automating social media visuals)
444 renders in one month (consistent n8n automation workflow pattern)
No churn (subscription active)
Usage aligns: they're automating visual content generation on a predictable schedule
Current MRR: $9 (Starter plan)
Current projections: If I can acquire 1 customer per month, I'll hit $100 MRR by December.
Why This Matters (And Why I'm Sharing)
Most product advice says: "Build for a broad market. Marketing is hard."
But at the pre-traction stage, finding ONE paying customer automating a specific workflow is worth 10,000 unqualified visitors.
I had the usage logs all along. I just needed to read them.
The lesson: Don't assume your use case. Let the data reveal it.
Lessons
Usage logs > customer surveys. What people do beats what they say. My customer never emailed me, but their automated rendering pattern told me everything.
Find your "one customer" wedge. I didn't build for "developers." I built for "people automating social media image generation with n8n and Make.com." That specificity is what differentiated me from Bannerbear.
Distribution is localized. Instead of trying Reddit-wide, I posted in r/nocode and r/Zapier where automation people actually hang out.
Pricing isn't your constraint. If the image rendering API solves a real automation problem, $9/month for 2,000 renders/month is a no-brainer.
Pre-warmed pools matter for specific niches. OG image generators need sub-100ms latency. Automated social media workflows tolerate 500ms-1s. That's why my Chromium pooling resonates with automation users, not OG teams.
What's Next
Product: No new features planned. The HTML-to-image API is stable and does what it needs to do.
Distribution: Doubling down on automation communities (n8n, Make.com, Zapier, IFTTT), not general dev communities.
Timeline: 30-day signup metric in June. If I don't add 1-2 more customers using automated image rendering workflows, I'll pivot back to consulting.
Open Questions for the Community
Other automation use cases I'm missing? (beyond social media graphic generation)
Have you used n8n for automated image generation? How?
Would you pay $9/month for a no-template HTML-to-image API?
Drop a comment. Or DM me on Twitter @renderpixdev.
Shameless plug: If you're automating visual content generation with n8n, Make.com, or Zapier, RenderPix might save you hours. Free tier gets you started — no credit card.
Edit (May 12, 2026): Both my paying customers are using RenderPix for automated social media image generation with n8n. This validates the HTML-to-image automation niche hard. If this resonates, I'll write a follow-up about distribution strategy in automation communities (n8n, Make.com, Zapier).
I've been building RenderPix — an HTML-to-image API — for a few weeks. Core idea: you POST raw HTML, get back a pixel-perfect PNG/JPEG/WebP. No templates, no proprietary DSL. Just HTML.
This week I shipped a small feature that I think has more leverage than it looks: GET /og-image
The problem I kept seeing:
Developers setting up OG images for their blog or SaaS write the same Puppeteer boilerplate every time. Or they use a template service, get locked into their design system, and pay per render. It's too much friction for something this common.
What I built:
https://renderpix.dev/og-image?title=My+Post&domain=myblog.com
That URL returns a 1200×630 PNG instantly. No signup, no API key, no HTML required. Drop it into a <meta> tag and you're done.
The monetization question:
Making it fully free felt wrong — no upgrade path. Rate limiting alone felt weak ("10 req/min is fine for me"). I went with watermark + freemium: anonymous requests get a "Free tier · renderpix.dev" badge in the corner. API key removes it. The watermark also acts as passive distribution — every OG image carries the brand.
If you're building a blog, docs site, or SaaS and need OG images without the hassle — try it: renderpix.dev
Got my first real user feedback on RenderPix today 🎉
A reddit user pointed out that WebP output could be improved. Took it as an opportunity to properly implement it: Playwright renders PNG → sharp converts to WebP, giving much better compression and quality control.
Fixed and deployed in under an hour.
Small win, but it means people are actually poking around and using it. That's the real milestone.
renderpix.dev if you want to check it out — HTML to image API, bring your own HTML, no templates.
I got my first paying customer for the starter pack for $9/m. a few days ago.
Numbers so far (14 days live):
6 users signed up
1 paying customer ($9/mo)
Running on a $30/yr VPS
Zero marketing spend — all organic
Hey IH!
I'm Özgür, solo dev from Turkey. I just launched RenderPix — an API that converts HTML/CSS to pixel-perfect images (PNG, JPEG, WebP).
The problem: Every dev building OG images, certificates, or invoices ends up wrestling with Puppeteer/Chromium. Self-hosting is painful, cold starts are slow, and it crashes under load.
The solution: One POST request with your HTML, get an image back in ~230ms. No infra to maintain.
Tech stack: Node.js, Fastify, Playwright, Chromium on a RackNerd VPS.
What I'd love to know:
Would you use something like this?
What's missing that would make you pay for it?
Try the live demo (no signup): https://renderpix.dev
Happy to answer any questions about the build, pricing, or growth strategy.
Comment