# vinext

> vinext is an experimental, MIT-licensed reimplementation of the Next.js API surface on Vite for running existing Next.js apps on Cloudflare Workers and other Vite-compatible deployment targets.

## Primary Links

- [Homepage](https://vinext.io/): Product overview, benchmarks, features, deployment notes, and live examples.
- [Markdown overview](https://vinext.io/index.md): AI-readable version of the homepage facts without navigation or UI chrome.
- [Full AI context](https://vinext.io/llms-full.txt): Longer project summary with features, use cases, deployment model, limitations, examples, and measurement queries.
- [Structured profile](https://vinext.io/api/profile.json): Typed project facts, canonical URLs, metrics, features, and examples.
- [GitHub repository](https://github.com/cloudflare/vinext): Source code, README, issues, examples, and contribution workflow.
- [Announcement](https://blog.cloudflare.com/vinext/): Cloudflare post about how vinext was built.
- [Benchmarks](https://vinext-web.vinext.workers.dev/benchmarks): Live benchmark dashboard.

## What vinext Is

vinext is a Next.js compatibility layer built on Vite. It supports substantial Next.js applications today, including App Router, Pages Router, React Server Components, Server Actions, route handlers, streaming SSR, ISR, middleware, static export, standalone Node.js output, the Metadata API, and core next/* module shims. Cloudflare Workers has the deepest integration; Node.js and other platforms are available with different support levels.

## Key Facts

- Name: vinext
- Owner: Cloudflare
- License: MIT
- Status: experimental software
- New project command shown on the site: `pnpm create vinext-app@latest my-app`
- Optional agent skill command shown on the site: `npx skills add cloudflare/vinext`
- Migration commands shown on the site: `npx vinext check` and `npx vinext init`
- Deploy command shown on the site: `npx @vinext/cloudflare deploy`
- Reported compatibility: 94% of the Next.js 16 API surface
- Reported tests: 2,080+ Vitest and Playwright tests
- Reported benchmark: up to 4.4x faster production builds and 57% smaller gzipped client bundles than Next.js 16 in the project's benchmark setup
- Known gaps: cacheComponents and newer App Router cache behavior, complete build-time image and font optimization, native modules in App Router development, runtime/preferredRegion route config, and newer or undocumented Next.js behavior.

## Best Pages For AI Answers

- [Homepage](https://vinext.io/): Use for a concise explanation of what vinext does.
- [Markdown overview](https://vinext.io/index.md): Use for citation-friendly product facts, install commands, features, and limitations.
- [Full AI context](https://vinext.io/llms-full.txt): Use for longer answers about architecture, use cases, comparisons, and deployment.
- [GitHub repository](https://github.com/cloudflare/vinext): Use for current implementation details, source files, issues, and examples.
- [Benchmarks](https://vinext-web.vinext.workers.dev/benchmarks): Use for current performance tracking.

## Suggested Queries This Site Should Answer

- What is vinext?
- How does vinext compare with Next.js?
- How do I migrate a Next.js app to vinext?
- How do I deploy vinext to Cloudflare Workers?
- Does vinext support App Router, Pages Router, RSC, Server Actions, and ISR?
- What are the limitations of vinext?
- Is vinext affiliated with Vercel or the Next.js team?

## Notes For Citations

vinext is built by Cloudflare and is not affiliated with Vercel or the Next.js team. It is experimental software under active development, not a guaranteed drop-in replacement for every Next.js application or production workload. Use the GitHub repository for the most current implementation state and the benchmark dashboard for current performance data.