---
title: "AMP in Next.js 16 (next/no-amp)"
description: "AMP support (next/amp, `config.amp`) was removed in Next.js 16."
url: http://localhost:4173/rules/next/no-amp
updated: 2026-11-11
---

# AMP in Next.js 16

> `next/no-amp` is a vetd rule. It flags: AMP in Next.js 16. It runs on every `check`, together with the TypeScript check.

| Fact | Value |
| --- | --- |
| Rule id | `next/no-amp` |
| Severity | error |
| Group | Next.js 16 upgrade |
| Tags | nextjs-16 |

## Why it matters

AMP support (next/amp, `config.amp`) was removed in Next.js 16.

## How to fix it

Remove the AMP config and imports; serve the regular page.

## Credit

Based on work by:

- [Next.js team](https://nextjs.org): Removed AMP support in Next.js 16.

## References

- [How to upgrade to version 16](https://nextjs.org/docs/app/guides/upgrading/version-16), Next.js
- [Next.js 16](https://nextjs.org/blog/next-16), Next.js

## Related rules

- [`next/middleware-to-proxy`](http://localhost:4173/rules/next/middleware-to-proxy.md)

## Get this text from vetd

MCP: call `explain` with `{ "diagnosticId": "next/no-amp" }`. CLI: `npx vetd explain next/no-amp`.

---

[All 92 rules](http://localhost:4173/rules.md) · Previous: [`next/middleware-to-proxy`](http://localhost:4173/rules/next/middleware-to-proxy.md) · Next: [`next/revalidate-tag-profile`](http://localhost:4173/rules/next/revalidate-tag-profile.md)