tech, developers, and the code underneath

issue 025· essay·

Everything is Ghibli now

Native image generation in a chat model produced a two-week global aesthetic event and a copyright question nobody wants to answer.

OpenAI shipped native image generation in GPT-4o this week and within seventy-two hours a substantial fraction of the internet's profile pictures looked like a Studio Ghibli production cel.

The technical achievement is real and got buried under the meme, which is a shame, because the technical achievement is the interesting part.

what is actually different#

Previous image generation from a chat interface was a handoff: the model wrote a prompt, a separate diffusion model rendered it, and the chat model never saw the result in any meaningful sense. You could not say "same picture but move the cat" because there was no shared representation.

Native generation means the same model produces the image tokens. That gives you:

  • Real editing. "Make the sign say something else" works, because the model understands the scene it produced.
  • Text that renders correctly. This has been the single most obvious tell of AI images for three years, and it is largely fixed. Infographics, diagrams, menus, and UI mockups now come out legible.
  • Instruction following at a level diffusion models never had. Ten objects with specified positions and colors. Diffusion models fall apart around four.

For developers specifically, the practical unlock is diagrams and mockups. "Draw me an architecture diagram with these six services and these arrows, in a clean technical style" now produces something you can actually put in a document.

the part everyone is arguing about#

Studio Ghibli did not consent to this and Hayao Miyazaki has been publicly, memorably contemptuous of AI-generated animation for years.

The legal position is genuinely unsettled. Copyright does not protect style — you cannot own "watercolor backgrounds and round faces" — which is why the outputs are probably not infringing on their face. Whether training on the works to acquire the style is infringement is the actual contested question, and it is being litigated in several jurisdictions simultaneously with no consistent answer yet.

The ethical position is less unsettled and more uncomfortable. A studio spent four decades developing a visual language through enormous manual labor — Miyazaki's teams famously hand-drew crowd scenes frame by frame — and that language is now a free preset. Whatever the courts decide, something was taken that was not offered.

I do not think "it is legal" resolves that, and I do not think "it is theft" resolves it either. It is a genuinely new situation and the reflex to force it into an existing category is making the conversation worse.

the practical guidance#

If you are shipping a product that generates images:

  • Do not name living artists or active studios in prompts you send on behalf of users, and filter for it. The legal risk is unquantified and the reputational risk is not.
  • Understand your provider's indemnification terms. They vary a lot and most people have not read them.
  • Provenance metadata (C2PA) costs you nothing to include and will matter more every year.

the thing that will actually change#

Stock photography as a business is finished, and has been finishing for a while. So is a large chunk of low-end commercial illustration — the spot art, the blog headers, the marketing filler.

What is not finished is illustration where the point is that a specific person made it. Miyazaki's films are not valuable because they look like that. They look like that because of what they are.

The model can produce the surface. It has nothing to say.

Dom, March 31, 2025

get README in your inbox

One dispatch, no noise. Tech and developer news, plus the occasional long piece on the craft.

subscribe →