Best-fit use cases
API architecture decisions
Social card systems
Report snapshots
Marketing asset automation
Implementation
A reliable four-step workflow
1
Identify ownership
Decide whether developers maintain markup or operators maintain visual templates.
2
Define the output
Separate webpage screenshots from repeated branded compositions.
3
Test real content
Compare long text, remote images, fonts, responsive behavior, and render consistency.
4
Choose maintenance
Adopt the model the team can safely update after the first implementation.
Concrete example
- trigger
- A new article publishes
- inputs
- Title, category, author, hero image
- output
- A consistent social card from a visual template
- destination
- Open Graph metadata
Frequently asked questions
Does Duply render arbitrary HTML and CSS?
No. Duply is designed around reusable visual templates and structured dynamic fields, not arbitrary webpage screenshots.
When is HTML-to-image the better fit?
Choose it when the existing HTML or public webpage is exactly what must be captured and developers own its presentation.
Continue the workflow
Build one production-shaped example
Start with one approved template, realistic data, and the exact trigger your team intends to use.
Start free