LOG 018: Do V7 Srefs Still Work in Midjourney V8.1?

Short answer: yes.

Every time Midjourney ships a new version, the same question lands in my DMs within a week. "I built my whole library on V7. Is it all dead now?"

I get why people ask. We've been trained by years of AI tooling to expect that everything breaks on every update. Prompts that stopped working. Workflows that needed rebuilding from zero. So when V8.1 became the standard alongside V7, people assumed their sref collections had just become museum pieces.

They didn't. Here's what I've actually seen, running both versions side by side.

Srefs carry over. Really well.

A style reference code is not a fragile prompt trick. It's a compressed fingerprint of an aesthetic — color behavior, texture, light, mood. When you paste an sref into a prompt, you're pointing the model at a visual territory, not giving it brittle instructions.

That's why they survive version changes. All the sref codes I built and curated on V7 — including the full 61 worlds across both of my packs — run in V8.1. And honestly, V8.1 handles them really well. The aesthetic holds. In some worlds the rendering even comes out cleaner, because the underlying model got better at the things srefs describe: coherent light, consistent texture, controlled color.

So no, your library is not dead. Paste the same code in either version and the world is still there.

What does NOT carry over

One thing breaks on version changes, and it's worth being precise about it: profiles.

Personalization codes are tied to the model version they were trained on. A V7 profile won't behave the same way in V8.1 — each version needs its own. That's always going to be the case: new model, new profile. If your workflow leans on personalization, plan to rebuild that layer when you switch versions.

Srefs and profiles get lumped together because they're both "codes," but they're different animals. The sref describes a style; the profile describes you. Styles transfer. Taste needs re-teaching.

The two versions are not interchangeable

Working in both, the thing that surprised me most is that V7 and V8.1 interpret the same prompt differently — same sref, same words, different temperament. Not better or worse. Different.

So I keep both in rotation. When a world isn't landing in one version, I run the same sref in the other before I touch the prompt. Half the time the version switch is the fix. This is the same reason I still occasionally reach back to older models for mood boards — each version has its own personality, and a world builder uses the whole toolbox.

The real lesson

Here's the part that matters more than any compatibility chart.

The question "will my codes survive the update?" only feels existential if codes are all you have. If your entire creative practice is a folder of magic strings, then yes — every model release is a small apocalypse.

But codes were never the asset. The asset is knowing how to build a world: how to define its logic, lock its visual language, and curate ruthlessly inside it. That's the part no version bump can delete. The fundamentals I teach transfer across every model I've used, because they're about creative direction, not syntax.

Srefs are a head start. The method is the moat.

If you want the head start, the packs are here — originally built on V7, running really well on V8.1, and they'll keep working as a curated reference library even when V9 eventually shows up and we all ask this question again. If you want the method, that's what the Academy is for.

Either way: stop worrying about the update. Build the world.