Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 37 ยท Getting Started

Vercel and Netlify Compared

Compare Vercel and Netlify: shared concepts, vocabulary that differs, config files, function folders, and how to choose. A translation table you can keep open while you work.

Vercel and Netlify solve the same problem with slightly different words and defaults. Learning where they agree lets you move between them easily, and learning where they differ stops you from copying the wrong setting into the wrong dashboard.

This lesson is a map. Later lessons go deep on each feature, so treat the tables here as a glossary to return to. Product details change, so when a limit or price matters, check the platform's current documentation.

The shared model

Both platforms use the same five ideas:

  • A project (Vercel) or site (Netlify) connected to a Git repository.
  • A deployment (Vercel) or deploy (Netlify) created on every push.
  • A production deployment on your main branch, and preview deployments on everything else.
  • Environment variables scoped to those situations.
  • Functions for server logic, plus an edge layer for code that runs close to the visitor.

Vocabulary translation table

Concept Vercel Netlify
Unit you create Project Site (also called project in newer UI)
One build result Deployment Deploy
Config file vercel.json (also framework config) netlify.toml
Preview for a pull request Preview Deployment Deploy Preview
Preview for a non-main branch Branch preview URL Branch deploy
Server code folder api/ (or framework routes) netlify/functions/
Edge code Routing Middleware / Edge runtime netlify/edge-functions/ (Deno)
Scheduled jobs Cron Jobs (crons in vercel.json) Scheduled Functions
Command line vercel netlify
Undo a bad release Instant Rollback / promote Publish an older deploy
Default free URL project.vercel.app site.netlify.app

Differences worth knowing

Framework fit. Vercel is built by the Next.js team, so new Next.js features usually appear there first. Netlify supports Next.js, Astro, Remix, SvelteKit, Nuxt and others through adapters and runtimes. Both detect most frameworks automatically.

Bundled extras. Netlify has historically bundled products such as form handling and identity. Vercel emphasizes its storage marketplace, analytics and observability. You can use any third-party service on either, so none of this is lock-in.

Config style. netlify.toml is a TOML file with build, redirect, header and per-context sections. vercel.json is JSON with keys such as redirects, rewrites, headers, crons and functions. A later lesson compares them side by side (see vercel.json and netlify.toml).

Function style. Netlify Functions use a Web-standard (request, context) signature and live in netlify/functions. Vercel Functions export handlers such as GET(request) from files under api/ or from framework route files. You will write both in the serverless chapter.

A translator you can run

Here is a stand-in that translates a concept name between the two vocabularies. It is a learning toy based on the table above, not a product feature.

Node.js Vocabulary translator (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

How to choose

Ask these questions in order:

  1. What framework do you use? Next.js with the newest features: Vercel is the natural home. Astro, Eleventy, Hugo, plain static: both are excellent.
  2. Which add-ons do you need? If you want built-in forms with no code, Netlify is convenient. If you want a managed database marketplace integrated into the dashboard, look at Vercel's integrations.
  3. Who pays and how many people collaborate? Check each platform's free tier terms (commercial use, team seats, bandwidth) before choosing for a business.
  4. Does it matter? For a portfolio, blog or documentation site the answer is usually "not much". Both let you switch later because your code lives in Git.

Keep platform-specific settings in a config file in your repository rather than only in the dashboard. That makes the setup reviewable, and moving platforms later is mostly translating one file.

A decision helper

Node.js Which platform to start with? (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does Netlify call the result of one build that Vercel calls a deployment?

    A Vercel deployment corresponds to a Netlify deploy.
  2. 2. Which file holds Netlify's build, redirect and header settings?

    netlify.toml is Netlify's configuration file; Vercel uses vercel.json.
  3. 3. Why keep settings in a file in your repository instead of only in the dashboard?

    Configuration in Git is versioned, reviewable and portable.
  4. 4. Which statement is true?

    The core model is shared, with different names and defaults.

Summary

  • Both platforms connect a Git repository, build on every push, publish production and preview deploys, and offer functions and edge code.
  • Names differ: project/site, deployment/deploy, vercel.json/netlify.toml, api//netlify/functions/.
  • Choose by framework, needed add-ons and team terms, and remember you can switch later.
  • Prefer configuration in the repository.

Next: Your First Deploy