Reve2.0 inserts code between prompt and pixels

On June 3, Silicon Valley startup Reve released the second-generation image generation model Reve2.0, which on launch day rocketed to #2 on the Image Arena text-to-image leaderboard — only behind OpenAI gpt-image-2, and ahead of Google Nano Banana2 and Microsoft MAI-Image-2.5. What really caught the tech world's eye wasn't the SOTA ranking, but the fact that it redefines image generation: write the code first, then render the pixels.

I. The "fireworks dilemma" of the past four years

Reve officially described the previous image generation mode as the "fireworks phase": stuff the prompt into a black box, pray the pixels look good enough; want to edit a part and you have to regenerate, breaking the overall composition. The one-shot "make or break" workflow is something image tools have never truly solved.

II. Reve2.0's core: layout-first architecture

Reve2.0 decouples planning and rendering into two steps. Planning first generates a structured image layout — each region has a label, coordinates, and semantic relationships, equivalent to the image's source code. Rendering then takes the layout and uses the renderer to draw it into native 4K pixels.

This code-based image approach brings three things: addressable editing (directly modify a region of the layout, without regenerating the whole image), agent-native (LLMs can directly read and modify the layout), and compute efficiency (translating into the next-token prediction mindset, reducing the repeated denoising overhead of diffusion). Reve1.0 used data structures to replace caption to verify the hypothesis, and Reve2.0 expands parameters by 3× and introduces a new planning architecture, entering the SOTA ranks.

III. Where does the paradigm shift lie?

Reve2.0 drives a new paradigm in image models: images shift from black-box output to structured objects, reviewable, diff-able, and mergeable; LLMs become the conductor's baton of image models, no longer just writing prompts; iterative creation becomes the default workflow, and designers can for the first time swap local parts without breaking the whole.

Code as the image's intermediate representation — together with GPT-Rosalind injecting reasoning into images, FLUX.2 introducing collaborative division of labor, and Ideogram 4.0 turning to open-source weights — points to one judgment: image generation is shifting from one-shot fireworks to a programmable industrial process. If this path holds, the form of the next wave of image tools may be closer to an IDE than imagined.