Vercel Hobby is useful for personal Next.js projects, but its actual limits need more precision than the old '10-second functions and 6,000 build minutes' shorthand. This guide reflects Vercel's published limits in October 2026; check your project settings because runtime and compute mode affect the function timeout.
An older client deployment once failed near a ten-second function timeout. That was a real operational problem on its configuration, but reusing that number as today's universal Hobby limit would mislead anyone starting a new project. Runtime, compute mode, and project settings decide which duration applies.
What Hobby includes
Vercel's Hobby plan documentation lists a free, personal plan with 100 GB of Fast Data Transfer, 1,000,000 function invocations, 4 active CPU-hours, 360 GB-hours of provisioned memory, and 1,000 image optimisation source images. It also includes custom domains, SSL, Git-connected deploys, and one concurrent build.
These numbers measure different things. A million invocations does not mean a million heavy requests fit within CPU and memory allowances. Watch all relevant charts in the dashboard, especially when functions call databases, image tooling, or AI services.
Function duration: Fluid Compute changes the answer
For Node.js, Bun, and Python functions on Fluid Compute, Vercel's function limits list a 300-second default and maximum on Hobby. New projects use Fluid Compute by default. The old 10-second default describes legacy, non-Fluid functions; it is not a universal Hobby cap.
A timeout still matters: a function that exceeds its configured duration can return a 504. But upgrading merely because a request runs for 11 seconds is the wrong diagnosis on a Fluid project. First identify its runtime, Fluid setting, configured maxDuration, and the slow step.
Long-running requests also consume resources. An external API call can be slow without using much active CPU, but provisioned memory time and other usage still matter. Profile the workload before deciding whether Pro or a background workflow is the right fix.
Builds and deploy frequency
Vercel's general limits show one concurrent build and 100 deployments created per day on Hobby. The previous blanket claim that every Hobby team has a 6,000-build-minute monthly allowance is not a reliable way to plan a current project.
For a large static site, benchmark a real production build and watch the build queue during active work. Remove unnecessary full rebuilds, use caching where it fits, and batch content releases when each deploy regenerates thousands of pages.
Transfer and image usage
The included 100 GB of Fast Data Transfer can cover a lean personal site, but images, downloads, and traffic spikes can change the picture quickly. Count bytes delivered, not just pageviews. Vercel's included 1,000 image optimisation source images is a separate allowance worth checking for galleries and catalogues.
Commercial use is the first decision
Vercel's fair-use guidance on Hobby restricts the plan to non-commercial, personal use. If the project is client work or a business site, plan for Pro or another suitable commercial hosting arrangement before launch.
A paid plan is not automatically necessary for a personal project that grows. Use the actual transfer, function, image, and build metrics. Upgrade when the use case or the measured limits require it.
How I would audit a project before upgrading
Start with the Usage dashboard for the most recent busy month. Record Fast Data Transfer, function invocations, active CPU, provisioned memory, image optimisation source images, deployment count, and build duration. If a client is paying for the site, the commercial-use rule already decides the plan. For a personal project, the first metric likely to hit its cap depends on the workload.
A static documentation site can have many deploys and almost no function use. An AI tool can have few pageviews but long-running functions and outbound calls. A photography portfolio may use little compute yet quickly consume image optimisation and transfer. Use those workload shapes to decide which optimisation is worth doing.
If functions are timing out, trace one slow request before changing plans. Measure database latency, third-party API waits, cold starts, payload size, and the configured duration. A five-minute cap will not repair a request that blocks on an unreliable upstream service.
For a static-first alternative, compare the current Netlify free tier and Cloudflare Pages using the same build frequency and asset volume. Netlify's new accounts use credits, so the older 300-build-minute comparison is no longer a like-for-like description.
Hobby or Pro?
Choose Hobby for a personal project with one owner and modest usage. Choose Pro for commercial work, team collaboration, greater limits, or a need for billed usage beyond Hobby. If request time is the only concern, check Fluid Compute first: the timeout may already be five minutes on Hobby.
FAQ
Is the Hobby function limit 10 seconds?
Not for a Fluid Compute function on a supported runtime. The documented Hobby duration there is 300 seconds. Legacy functions can have shorter defaults; check the deployed project's configuration.
Can I use a custom domain on Hobby?
Yes. Custom domains and automatic SSL are available on Hobby.
What happens if I exceed a Hobby allowance?
Vercel says that, in most cases, use of the affected feature waits until the allowance resets after 30 days. Check the dashboard and current plan documentation for the specific resource.
Can I host a paying client's site on Hobby?
Hobby is restricted to non-commercial personal use. Put a client site on a commercial plan.
For a simpler answer to whether Vercel is free, read Is Vercel Free?.