What Are Netlify Functions?

They are AWS Lambda functions Netlify manages for you. You drop a JavaScript or TypeScript file in a netlify/functions folder, export a handler, and Netlify exposes it at /.netlify/functions/your-name. No servers, no deployment config.

How to Create Your First Function

1. Create netlify/functions/hello.js.
2. Export a handler that returns a status code and body.
3. Push to your repo. Netlify deploys the function automatically.
4. Call it from your front end with fetch('/.netlify/functions/hello').
5. For scheduled work, add a cron-style schedule config to the function.

Cold starts on the free tier run 200-500 ms for Node functions. Warm invocations answer in tens of milliseconds.

How Do Netlify Forms Work?

Add a data-netlify="true" attribute to an HTML form and Netlify starts capturing submissions — no endpoint code required. You get a submissions dashboard, email or webhook notifications, and spam filtering. JavaScript-rendered forms need a hidden static copy of the form in the HTML so Netlify’s build bot can detect the fields.

How Do You Secure a Function?

Never put secrets in front-end code. Use Netlify environment variables, which are available to functions at runtime via process.env. For endpoints that shouldn’t be public, check an auth header inside the function. Functions are public URLs by default — anyone can call them.

Where Do Functions Fall Short?

Execution time is capped (10 seconds on the free tier’s default, longer with configuration), so long-running jobs fail. They also don’t hold state between invocations. For background processing, use background functions on Pro or hand the job to a queue service.

Quick Summary

• Netlify Functions are managed serverless endpoints, no config needed.
• Add data-netlify="true" to a form to capture submissions instantly.
• Free tier: 100 form submissions and 125K function calls monthly.
• Store secrets in environment variables, never in front-end code.
• Function timeouts make them unsuitable for long jobs.

What Kinds of Sites Does Netlify Host?

Anything that builds to static files: Astro, Hugo, Jekyll, Next.js in static export, React SPAs, plain HTML. It also runs serverless functions and edge functions, so light backend logic is possible without a separate server.

How to Deploy Your Site

1. Sign up at netlify.com with GitHub, GitLab, or email.
2. Click Add new site and choose Import an existing project, then pick your repo.
3. Set the build command (e.g. npm run build) and publish directory (e.g. dist).
4. Click Deploy. First build takes a minute or two.
5. Or skip Git entirely: drag a folder of files onto the dashboard for an instant deploy.

How Do You Add a Custom Domain and SSL?

Go to Domain settings, add your domain, and point DNS at Netlify’s nameservers or add the A/CNAME records they show. Netlify provisions a Let’s Encrypt certificate automatically within minutes. HTTPS is on by default — there is no setting to enable.

Is Netlify Free?

Yes, the Free plan includes 100 GB of bandwidth and 300 build minutes per month, with unlimited sites and automatic deploys. That covers most personal projects and landing pages. Paid Pro starts around $19/month and adds more bandwidth, password protection, and background functions.

What Are the Common Pitfalls?

Bandwidth overages on the free plan can pause your site until the next cycle — a viral page can burn 100 GB in a day. Build minutes run out if you deploy constantly. And large images should be optimized before upload; Netlify serves them fine but your bandwidth budget pays for the size.

Is Netlify Right for Your Project?

Great for static sites, JAMstack apps, and docs. If you need long-running servers, websockets, or heavy background jobs, look at a platform like Render or a VPS. Netlify is built around the static-and-functions model.

Quick Summary

• Netlify deploys static sites from Git or drag-and-drop.
• Free plan: 100 GB bandwidth and 300 build minutes monthly.
• Custom domains get free automatic SSL.
• Bandwidth overage can pause a free site.
• Best for static/JAMstack; use another host for long-running servers.