Last updated: June 08, 2026  ·  Updated quarterly to reflect current pricing and features.
Migration Guide · Marketing Image API

Switching from DynaPictures to RenderPix: A Step-by-Step Guide

June 08, 2026 5 min read Marketing Image API

Ready to switch from DynaPictures to RenderPix? This guide walks through the API differences, code changes, and everything you need to complete the migration in under an hour.

Why migrate from DynaPictures to RenderPix?

The most common reasons: lower pricing, native n8n/Make.com integration, batch rendering, or template variables. This guide covers the API differences and code changes needed to complete the migration.

API differences

DynaPictures and RenderPix share the same core concept — send HTML, get an image — but the API design differs. RenderPix uses a single POST /v1/render endpoint with a JSON body. Authentication is via X-API-Key header.

Before (with DynaPictures)

# DynaPictures — typical request pattern curl -X POST https://api.dynapictures.com/render \ -H "Authorization: Bearer YOUR_KEY" \ -d '{"html": "<div>Hello</div>", "width": 1200}'

After (with RenderPix)

# One API call. That's all. curl -X POST https://renderpix.dev/v1/render \ -H "X-API-Key: YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "html": "<div style=\"width:1200px;height:630px;background:#0f0f0f;color:#fff;display:flex;align-items:center;justify-content:center;font-size:48px\">Hello, RenderPix</div>", "width": 1200, "height": 630, "format": "png" }' --output card.png

Migration checklist

What stays the same

Your HTML templates work without modification. PNG, JPEG, and WebP output formats are all supported. Width and height parameters are identical.

Try RenderPix free — no credit card needed

100 renders/month on the free plan. Full HTML control. Native n8n node.

Get your free API key →

More about DynaPictures

Compare other tools