Muse Spark 1.3 vs 1.2: Should You Upgrade? (2026)

Meta shipped Muse Spark 1.3 on 2 September 2026, four weeks after 1.2 landed on 5 August. There was no keynote and no launch blog post — as of 3 September, the ai.meta.com blog index still lists "Introducing Muse Spark 1.1" (9 July 2026) as the only Muse Spark announcement. 1.2 and 1.3 both arrived as documentation-and-API point releases.

That makes the upgrade question harder than usual: the two versions are indistinguishable on every number a pricing page can show you. Here is what actually changed, what independent measurement says so far, and the one concrete reason some teams should stay on 1.2.

What actually changed between Muse Spark 1.2 and 1.3?

On the published specification: almost nothing. Here is the head-to-head, taken from Meta's pricing and rate-limits page and the live OpenRouter model records for both SKUs. The identical rows are the finding.

* See the audio caveat below — it is the only spec-level regression in 1.3.

Meta states the position plainly in its model docs: the three Muse Spark versions each share "the same modalities and context window, and differing only by capability." There is no long-context premium on either version, and no version-specific parameter to learn.

What does Meta say is different in 1.3?

Meta's Models page gives one sentence of claim, and it is worth reading closely. Muse Spark 1.3 is described as "the latest version, tuned for agentic workflows (multi-step tool, browser, and long-horizon tasks) with improved coding over 1.2," and is marked "Recommended for new work." It is also now the default model in every code sample across the documentation, which 1.2 previously was.

The OpenRouter descriptions track the same shift in emphasis. 1.2 is described as "a reasoning model designed for complex agentic tasks" that "supports multi-agent workflows, whether as either a main agent that plans and delegates or as a subagent executing in parallel." 1.3 is described as being "for long-running agentic, multi-agent, and coding workflows," designed "to keep track of information across extended tasks, work through conflicting inputs, and request clarification or confirmation when needed, with an emphasis on concise execution."

Two of those phrases are new and specific enough to be testable: work through conflicting inputs and request clarification or confirmation when needed. If the tuning is real, 1.3 should ask a question rather than guess when a long agent run hits contradictory context — the exact failure mode that makes long-horizon agents expensive. Meta has published no eval backing it, so treat it as a stated design goal, not a measured result.

What do independent benchmarks show for 1.3 vs 1.2?

One day after launch, the independent picture is thin but consistent, and it points the same direction.

The two harnesses that have run both versions agree on a real gain. Artificial Analysis puts 1.3 at 62 on its Intelligence Index against 57 for 1.2 — a five-point move on a composite of nine evals including Terminal-Bench v2.1, τ³-Banking, GPQA Diamond and Humanity's Last Exam. OpenRouter's vgi_bench figure moves further, 53.4% to 61.4%, an eight-point jump.

Three caveats. First, AA labels the 1.3 run "max" and the 1.2 run "xhigh"; both models expose the identical five-step reasoning_effort ladder, so these are almost certainly the same top setting under different labels — but it is a naming inconsistency, not a confirmed apples-to-apples. Second, AA notes 1.3 emitted 120M output tokens across the index, above typical verbosity for its class, so some of the gain is bought with reasoning tokens you pay for. Third, 1.3 has no Arena or Design Arena data yet; 1.2's #5 placement rests on 3,240 votes.

The honest read: the delta is real and larger than a typical point release, but it is a two-harness result on a one-day-old model. Our earlier look at whether Muse Spark 1.2's benchmark claims held up against Claude Opus 5 is the pattern to expect again — headline indices move first, agentic numbers settle later.

Why should audio users stay on Muse Spark 1.2?

This is the one place where 1.3 is a downgrade, and it is documented by Meta rather than inferred. Both the Models page and the Video and audio understanding guide carry the same note:

Audio understanding in Muse Spark 1.3 is currently not fully supported, and response quality for requests including audio content may be degraded.

Meta's recommendation is to use Muse Spark 1.2 for audio, or the dedicated muse-voice-transcribe-1.0 model for speech-to-text. The audio guide follows its own advice — every audio example in it is written against muse-spark-1.2, not the 1.3 default used everywhere else in the docs.

This applies to embedded audio in video too. Muse Spark reads a video's soundtrack alongside its frames, so a pipeline summarising meeting recordings or narrated screen-captures is an audio workload even if you think of it as video. The word "currently" implies a fix is intended; Meta has published no timeline.

What is the Contributor tier, and what do you trade for it?

Both 1.2 and 1.3 ship a second SKU — muse-spark-1.2-contributor and muse-spark-1.3-contributor — at a fraction of standard pricing.

The trade is explicit in Meta's docs: Standard means "your prompts and completions are not used to train Meta models"; Contributor is "heavily discounted token pricing in exchange for permission to use your prompts and completions to train future Meta models." On a realistic 1M-in / 200k-out job that is $2.10 on Standard against $0.14 on Contributor — about 15× cheaper.

The catch most write-ups miss is the throughput ceiling. Contributor is capped at 100 requests per minute against Standard's 3,000 — a 30× reduction, applied per team rather than per API key. Contributor is built for prototyping and burst experiments, not for serving a chatty production agent, and no amount of extra keys will raise it.

The timing tells you something about Meta's intent. 1.2 shipped on 5 August and its Contributor SKU only appeared 16 days later, on 21 August. 1.3's Contributor SKU appeared 53 minutes after the base model, on the same day. Muse Spark 1.1 has no Contributor variant at all. The tier started as a bolt-on experiment and is now a standing part of the product line. One further detail: muse-spark-1.2-contributor carries the canonical build date 20260805 — the same snapshot as base 1.2, despite being listed two weeks later. Contributor is a billing-and-terms tier over identical weights, not a different or smaller model.

The full terms deserve more room than this comparison gives them — we cover what the data-sharing grant actually permits in what Contributor pricing really costs you, and the 1.3 SKU specifically in the Muse Spark 1.3 complete guide.

Is Muse Spark 1.2 deprecated or still available?

Still available, and not deprecated. Meta's Models page lists 1.3 as "the latest version," 1.2 as "the previous version" and 1.1 as "the original version" — three neutral labels with no sunset notice, no end-of-life date and no migration deadline attached to any of them. All three remain on the Standard tier at the same price.

Serving status backs that up. As of 3 September 2026, both muse-spark-1.2 and muse-spark-1.2-contributor are live with a normal status flag, 100% uptime over the trailing window, and no expiry date on the record. Meta has kept 1.1 addressable nearly two months after 1.2 replaced it — a reasonable prior for how long 1.2 stays reachable. Pin explicit version strings rather than relying on a default and you control your own timing.

Do you need to change any code to upgrade?

For nearly every application, the change is one string. The two versions share the same endpoints (Responses, Chat Completions and Messages), the same 1,048,576-token context, the same 943,718-token output ceiling, the same reasoning_effort ladder from minimal to xhigh, the same tool-calling and structured-output surface, and the same prices. OpenRouter reports byte-identical supported-parameter lists for both.

- model="muse-spark-1.2"
+ model="muse-spark-1.3"

Three things to check before you flip it:

• Audio paths. If any request can contain an input_audio part — or a video with a soundtrack you rely on — keep those calls on 1.2 and route only text/image/PDF traffic to 1.3.
• Output token budget. Artificial Analysis measured 1.3 as more verbose than its class average. Same price per token still means a higher bill if the model thinks longer, so re-baseline cost on your own traffic rather than assuming parity.
• Prompt-cache warmth. Switching model IDs starts a fresh cache. Expect a short window paying $1.25 rather than $0.15 on prefixes that were previously hitting cache.

Neither version supports reasoning_effort: "none", so there is no thinking-disabled path on either — that has not changed.

Who should switch to Muse Spark 1.3 — and who should wait?

Switch now if you are starting new work (Meta's own recommendation), you run long-horizon or multi-agent loops where the "conflicting inputs" and "ask for confirmation" tuning targets your actual failure mode, or you are coding-heavy and want the measured index gain at zero extra list price. With prices identical, the downside is bounded: if 1.3 underperforms for you, reverting is the same one-line change.

Wait if audio is anywhere in your pipeline — that is a documented regression, not a rumour. Also wait if you are cost-sensitive on output-heavy workloads until you have measured 1.3's verbosity on your own prompts, or if your team requires human-preference evidence before a production swap: Arena has no 1.3 data yet, and 1.2 sits at #5 with a real vote count behind it.

The one thing not worth doing is agonising over it. This is not a pricing decision or an architecture decision — it is a model string, both versions stay served, and a two-hour A/B on your own eval set will tell you more than any leaderboard will. If you want the wider context on where Muse Spark sits against the frontier, start with our Muse Spark guide and the 1.3 vs Claude Opus 5 comparison. And if you are staffing the engineers who have to run these evaluations properly, that is the kind of work Codersera places for.

FAQ

What's new in Muse Spark 1.3?

Meta describes 1.3 as tuned for agentic workflows — multi-step tool, browser and long-horizon tasks — with improved coding over 1.2. OpenRouter's description adds that it tracks information across extended tasks, works through conflicting inputs, and asks for clarification when needed. Price, 1M context, max output and the parameter surface are all unchanged from 1.2.

Is Muse Spark 1.3 better than 1.2?

On the two harnesses that have measured both, yes. Artificial Analysis scores 1.3 at 62 versus 57 for 1.2 on its Intelligence Index, and OpenRouter's vgi_bench shows 61.4% against 53.4%. But 1.3 is one day old, has no Arena or Design Arena data yet, and is documented as worse at audio. The gain looks real; the evidence base is still narrow.

Is Muse Spark 1.3 more expensive?

No. Both versions are $1.25 per million input tokens, $4.25 per million output, and $0.15 per million cached input on Meta's Standard tier, with web-search grounding at $2.50 per 1,000 queries on either. There is no long-context premium on either version. Your bill can still rise if 1.3 generates more reasoning tokens on your prompts.

What is the Contributor tier?

A discounted SKU — muse-spark-1.3-contributor — priced at $0.10/1M input and $0.20/1M output in exchange for permission to train future Meta models on your prompts and completions. Standard tier never trains on your data. Contributor is also rate-limited to 100 requests per minute against Standard's 3,000, so it suits prototyping rather than production serving.

Is Muse Spark 1.2 deprecated?

No. Meta's docs label it "the previous version" with no sunset date, end-of-life notice or migration deadline. Both the standard and Contributor 1.2 SKUs were serving normally with full uptime as of 3 September 2026, and 1.1 is still addressable two months after being superseded. Meta recommends 1.3 for new work but does not require you to move.

Do I need to change my code to upgrade?

For most applications, only the model string. The two versions share endpoints, context window, max output, reasoning-effort levels, tool-calling and structured-output support, and pricing. The exception is audio: keep input_audio requests and audio-bearing video on 1.2. Also expect a cold prompt cache immediately after switching model IDs.

Does Muse Spark 1.3 support audio?

It accepts audio input, but Meta states audio understanding "is currently not fully supported" and response quality "may be degraded." The official recommendation is Muse Spark 1.2 for audio understanding, or the dedicated muse-voice-transcribe-1.0 model for speech-to-text. Meta's own audio documentation examples use 1.2. This includes the embedded soundtrack of an uploaded video.

Why did Meta not publish a blog post for Muse Spark 1.3?

Meta announced Muse Spark 1.1 with a blog post on 9 July 2026, but shipped both 1.2 and 1.3 as documentation-and-API point releases. As of 3 September 2026, the ai.meta.com blog index carries no 1.2 or 1.3 announcement. The authoritative sources for what changed are Meta's Models and Pricing pages, plus the live model registry.