Image 2.6 costs more tokens for generating low and medium quality images, so it ends up being a bit more expensive. Could refer to https://developers.openai.com/api/docs/guides/image-generati...
Yeh using sprites to make frames consistent (kinda tilting latent space towards a character consistency, zero-shot ~LoRA hack?) is old-school. I did this 3 years ago. https://j11y.io/dance/
From what I can tell after some preliminary testing, you have to pass an additional large language model to the OpenAI API when generating SVGs.
I couldn't find this requirement in the documentation, but if you don't pass one in, you get this error:
400 {"message": "SVG generation requires 'svg.model'.",
"param": "svg.model", "code": "missing_required_parameter"}
Recraft is probably the only group I know of that had a native text-to-SVG generator pretty early on, but since it’s a closed model, I’m not familiar with what they were doing under the hood technically.
Re:Introducing Images 2.6
by petercooper on Thursday November 05, 2026 @02:52PM
(#50383595)
Re SVG: and it would likely strip any SynthID watermarks.
It could be viable to encode SynthID-like variables in subtle variations of positioning of elements, path lengths, etc. I think I saw an article on here a couple weeks ago which used such techniques to hide 'messages' in SVGs. It might even be possible to do it in a way which survives basic manipulations, as with rasters.
> It's possible OpenAI has pipelined a raster-to-vector tool that does the conversion automatically. (I developed a similar pipeline and it works extremely well; I'll open source it at some point)
If I could somehow subscribe to ensure I see this when you do, I would.
Please do so and share on HN!
However, adherence between frames is generally tricky, and even in the examples there is a lot of noise between frames although that could be due to compression.