• 1 min read Support for the legacy now.json config file will be officially removed on March 31st, 2026. • Migrate existing now.json files by renaming them to vercel.json, no other content changes are required. • For more advanced use cases, try vercel.ts for programmatic project configuration. • Learn more about configuring projects with vercel.json in the documentation. • 1 min read Support for the legacy now.json config file will be officially removed on March 31st, 2026. • Migrate existing now.json files by renaming them to vercel.json, no other content changes are required.

Article Summaries:

  • Vercel will discontinue support for the legacy now.json configuration file on March 31, 2026. Developers are urged to rename existing now.json files to vercel.json; no additional changes to the file’s contents are required for the migration. For projects needing more complex, programmatic configuration, Vercel recommends using vercel.ts. The announcement includes a link to the official documentation on configuring projects with vercel.json, providing guidance on the transition and best practices for updating project settings.
  • Vercel will discontinue support for the legacy now.json configuration file effective March 31, 2026. Developers are instructed to rename any now.json files to vercel.json; no additional modifications are required. For projects needing more complex, programmatic configuration, Vercel recommends using vercel.ts. This change is part of Vercel’s effort to streamline project configuration and consolidate documentation. Updated guidance and examples are available in the Vercel documentation. The transition is expected to be straightforward, with minimal impact on existing deployments. This update aligns with Vercel’s broader initiative to unify configuration formats and improve developer experience. Teams should review their deployment pipelines to ensure compatibility before the cutoff date.

Sources: