Skip to content
modeldeprecations.dev
Amazon nova-reel-1-0

Amazon Nova Reel v1.0 (Amazon)

Deprecated Shuts down in 58 days

Yes — Amazon deprecated Amazon Nova Reel v1.0 on March 30, 2026 and shuts it down on September 30, 2026 (in 58 days). The recommended replacement is MiniMax H3.

The first release of Amazon's video generation model, producing 720p at 24 frames a second from a 512-character prompt. Both Reel versions were moved to Legacy on the same day and share a 30 September 2026 end of life, so there is no newer Reel to migrate to. The Bedrock invoke id is amazon.nova-reel-v1:0.

The facts

Provider Amazon
Model id nova-reel-1-0
Released
Deprecated March 30, 2026
Shutdown September 30, 2026 · in 58 days
Status Deprecated
Last verified August 3, 2026

What to use instead

MiniMax H3 MiniMax-H3 Active

Amazon names no successor and Nova 2 ships no video generation model. MiniMax H3 is the nearest live video model in this catalogue; it is our suggestion, not Amazon's.

What parameters MiniMax-H3 accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them.

- "model": "nova-reel-1-0"
+ "model": "MiniMax-H3"

Frequently asked questions

When will Amazon Nova Reel v1.0 shut down?
Amazon Nova Reel v1.0 is scheduled to shut down on September 30, 2026, in 58 days.
What replaces Amazon Nova Reel v1.0?
Amazon recommends MiniMax H3 (`MiniMax-H3`) as the replacement for Amazon Nova Reel v1.0. Amazon names no successor and Nova 2 ships no video generation model. MiniMax H3 is the nearest live video model in this catalogue; it is our suggestion, not Amazon's.
Is Amazon Nova Reel v1.0 still available?
Yes, for now. Amazon Nova Reel v1.0 is deprecated but still answers requests until September 30, 2026. Deprecated models get no further updates and are the first to lose capacity.
How do I migrate from Amazon Nova Reel v1.0 to MiniMax-H3?
Swap the model id in your API call: replace "nova-reel-1-0" with "MiniMax-H3". Amazon names no successor and Nova 2 ships no video generation model. MiniMax H3 is the nearest live video model in this catalogue; it is our suggestion, not Amazon's.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

Drop the badge in a README so it turns red the day this model is retired:

[![nova-reel-1-0](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/amazon/nova-reel-1-0.json)](https://modeldeprecations.dev/amazon/nova-reel-1-0)

Other Amazon models

All Amazon deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.