Midjourney Sref Codes Are Version-Bound: Fix Your Library

If a style reference you saved months ago now renders something different, nothing is broken – your library is version-bound. A numeric sref code is a pointer into the style system that minted it, and --sv is the parameter that chooses the interpreter: V6-era codes keep their look with --sv 4, V6.1-era codes with --sv 6, and since March 2026 new codes are minted under the rebuilt --sv 7 baseline (about 4x faster and cheaper) that the V8 family inherited. Maintaining a catalog of captured srefs across those transitions produced the era table and the library strategy below.

TL;DR

• A numeric sref code is not a style. It is a pointer into a specific style algorithm. Change the algorithm version and the same integer renders a different aesthetic.1
• Era determines the pin. V6-system codes keep their look with --sv 4; V6.1-era codes with --sv 6. Codes minted since the --sv 7 baseline arrived (March 2026) run natively, and earlier V7-era codes ride the V8 launch’s declared full backward compatibility with V7 srefs.1 For codes you use constantly, consider regenerating the reference on current models rather than living on pins.
• Image-URL srefs are the durable form. A reference image is interpreted fresh by whatever algorithm runs it; a numeric code is frozen against the one that minted it. New library entries should be images first, codes second.
• --sref random is the discovery engine, and it pairs with Draft Mode on V8.1 – half-cost 24-image grids for style hunting.2
• The current --sv 7 system is about 4x faster and 4x cheaper than its predecessor.3 Regenerating your working set on it is cheap; era pins are for the archive.
• Full parameter coverage lives in the Midjourney guide; the V7-to-V8 migration map covers the rest of the surface.

What an Sref Actually Transfers

The --sref parameter transfers aesthetic qualities from a reference – color palette, lighting style, artistic technique, mood, and compositional tendencies – without transferring subject matter. Strength runs through --sw (0-1000, default 100): under 50 is a whisper, 50-150 is a balanced transfer, 150-300 asserts the style, and above that the style dominates the prompt. Multiple references blend: --sref [url1] [url2] mixes aesthetics into combinations no single image holds.

Srefs reward distinctive sources. A reference with a strong visual identity – consistent palette, recognizable technique – transfers cleanly; a generic photo transfers mush. This matters for library-building: the codes worth cataloging are the opinionated ones.

The Version-Binding Problem

Here is the part that costs people their libraries. When you capture a numeric sref code, the integer is meaningful only to the style system that minted it. Midjourney has moved that system through successive generations – the V6 system (--sv 4), the V6.1 system (--sv 6), the V7-era system whose codes the V8 family carries by declared compatibility, and the current --sv 7 baseline that arrived with the V8 Alpha – and a legacy code needs its home version’s pin to keep the look you cataloged it for. When an old sref “looks wrong,” this is the usual reason: the code did not drift, the interpreter changed underneath it.

And nothing in the product does this bookkeeping for you. The integer and its era travel separately – nothing in the prompt UI surfaces which system minted a code – so only your own notes connect a saved sref to the --sv that gives it back.

The Compatibility Matrix

Six rows cover every case:

The asymmetry in that table is the strategy. Numeric codes need era bookkeeping to stay faithful; image references need none, because an image is re-interpreted by whatever algorithm receives it. The cleanest V8-native path is image-based srefs – and for legacy codes you still care about, consider regenerating the reference natively on current models rather than living in compatibility mode.

Building a Library That Survives

The practice that emerged from maintaining a large sref catalog through successive algorithm transitions:

1. Capture the image, not just the code. When a random hunt or a generation produces an aesthetic worth keeping, save the source image alongside the numeric code. The code is a fast handle for today’s algorithm; the image is the style’s permanent record. When the next --sv arrives, your codes will wobble and your images will not.

2. Tag every code with its --sv era at capture time. A bare integer in a notes file is a future mystery. 1234567890 (sv6, captured 2026-03) is usable forever, because the matrix above tells you exactly how to run it. (Inherited a bare integer anyway? The FAQ below has the three-run recovery procedure.)

3. Hunt on the cheap tier, render on the good one. --sref random under Draft Mode on V8.1 is the discovery engine – 24-image grids at half cost, sampling aesthetics you would never prompt for deliberately.2 Catalog the hits, then apply them to real work as image references on V8.2.

4. Deduplicate and cohort. A library past a few hundred entries develops near-duplicates – the same aesthetic family captured five times under different codes. Periodically cluster by visual similarity and keep the strongest exemplar of each cohort; a library’s value is its range, not its count.

5. Regenerate the working set, archive the rest. The current --sv 7 system runs about 4x faster and cheaper than its predecessor.3 For the twenty styles you actually use, re-establish them natively (from the saved source images); keep the long tail in compatibility mode with era tags rather than migrating everything.

Srefs vs Moodboards: The Division of Labor

They compose: a moodboard supplies your baseline taste while an sref steers an individual render, and both ride the same --sv 7 infrastructure in the V8 family.3 The library strategy differs accordingly – moodboards are tended like a garden (curated additions over time), srefs are cataloged like a spice rack (labeled, dated, reached for by name).

FAQ

Why does my old Midjourney sref code look different now?

Because numeric codes are bound to the style system that minted them, and Midjourney has moved through several of those systems: V6 (--sv 4), V6.1 (--sv 6), the V7 era, and the current --sv 7 baseline. A legacy code needs its home system’s pin to keep its look – same code, different interpreter, different result. Pin legacy codes to their era, or regenerate the reference natively.

Do numeric sref codes work in Midjourney V8?

Yes. Midjourney’s compatibility chart lists style-reference codes as supported across the V8 family, and current-era codes run natively on its --sv 7 baseline. Legacy V6 and V6.1-era codes keep their look through their era pins (--sv 4 and --sv 6); for frequently used ones, consider regenerating the reference on current models for better results. Image-URL references carry no era binding at all, which is why a durable library stores images, not just integers.

What is –sv in Midjourney?

The style-version parameter: it selects which style-reference algorithm interprets your sref. --sv 4 and --sv 6 are earlier systems kept for backward compatibility; --sv 7 is the V8-era baseline, roughly 4x faster and cheaper than its predecessor.3 A numeric code only means what its home algorithm says it means.

How do I find the era of an untagged sref code?

Empirically. Run the code three ways against the same prompt – bare (current baseline), with --sv 6, and with --sv 4 – and compare the results to the output you originally cataloged the code for. Whichever run reproduces the look you saved reveals the code’s home era; tag it, and it never needs the experiment again. (No saved render to compare against? The three runs then surface three candidate looks to choose between – you recover a usable style, if not the original era.) Three cheap generations turn a mystery integer back into a usable library entry.

Should I use an sref or a moodboard?

Sref for steering a specific render toward a specific reference; moodboard (--p) for applying your accumulated personal taste everywhere by default. They combine in one prompt for layered control – baseline from the moodboard, per-shot direction from the sref.

1. Midjourney, Version documentation – the V8-family compatibility surface for style references, and the merged V8.1/V8.2 column this post’s matrix is checked against. The V7-era row rests on the V8 Alpha launch announcement (March 17, 2026): “Full backwards compatibility with V7 profiles/moodboards/srefs.” Full working detail in the Midjourney guide. ↩↩↩↩
2. Midjourney, Draft Mode for V8.1 – Draft Mode’s 24-image grids at half the fast-hours of a standard V8.1 job. The compatibility chart does not carry Draft Mode to V8.2, but the Draft Mode article as revised July 27, 2026 documents V8.1/V8.2 drafts explicitly (24 images, 512x512px, 0.4 GPU minutes, web-only) – the docs disagree, and V8.1 remains the unambiguous pin. The --sref random pairing arrived with Random Styles in Draft Mode (June 25, 2026). ↩↩↩
3. Midjourney, Relax Mode for V8 Alpha (March 2026) – the --sv 7 baseline: approximately 4x faster and 4x cheaper than the previous style system, supporting --hd, --p, --stylize, and --exp, with moodboards defaulting to the same system. ↩↩↩↩