Developers struggle to render reliable HTML across contexts
Developers who generate images or canvas content from HTML have to manage page readiness, data, fonts, CSS, and other resources themselves. Some instead render HTML on the server and insert it into the page to avoid complex frontend rendering, but that shifts work into custom endpoints. Free conversion services also raise concerns about long-term availability.
For developers building HTML-rendering workflows. Mentioned from Aug 2018 to Dec 2025 on GitHub and Hacker News.
5 different people described this problem in 4 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 4.4/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
I need this to get around difficulties knowing when the page is rendered when using page.setContent. With POST support, I could have an internal route rendering HTML, and POST a json body that contains all the context variables needed to render the template
But your HTML-in-SVG document will need to load all its own resources, fonts, CSS etc.. which makes this process rather tedious
dtf on Hacker NewsMar 2024
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks