Cover Image
Last month, a designer friend showed me his Vercel dashboard. He had launched a modest photography portfolio three months earlier — maybe 2,000 visitors a month. His bill? $87. For a static site with eight pages of images.
He's not alone. Across design communities and freelance groups, the same story keeps surfacing: Vercel is a joy to deploy with, until the bill arrives. The platform that made git-push-to-deploy feel magical has a pricing model that punishes exactly the kind of visual, image-rich work designers create.
I've spent the last few weeks testing every major alternative through a designer's lens — not a developer's. No YAML config files, no talk of cold starts or edge middleware. Just the stuff that matters: how fast can I get a portfolio live, can I share previews with clients, and will I wake up to a surprise charge?
Here's what actually works in 2026.
Why Designers Are Looking Past Vercel
Vercel is still excellent at what it does. The developer experience is polished — connect a Git repo, push, and your site is live with a preview URL before you've opened another tab. For Next.js projects especially, nothing integrates more smoothly.
But the cracks start showing the moment you use it as a designer, not as a full-stack engineer.
The pricing doesn't scale for visual work. Vercel's free Hobby tier gives you 100 GB of bandwidth per month. That sounds generous until you realize a single unoptimized portfolio image viewed 1,000 times burns through 3 GB. Add AI crawlers aggressively scraping your images — a problem multiple creators reported in 2025 and 2026 — and you can blow past the limit within days. The Pro plan bumps you to 1 TB, but at $20 per seat per month, it adds up fast for a freelancer with one or two client sites.
The free tier prohibits commercial use. Here's the fine print most designers miss: Vercel's Hobby plan is for personal, non-commercial use only. If your portfolio promotes your freelance services or hosts a client's landing page, you're technically in violation. Netlify and Cloudflare Pages both allow commercial use on their free tiers.
Hidden defaults drain your wallet. Turbo Build and Fluid Compute are enabled by default on Pro projects, and they bill at premium rates. One developer documented burning through $10 with only 50 daily users — not because of traffic, but because of defaults he didn't know existed. As a designer who would rather spend time in Figma than a billing dashboard, that's a dealbreaker.
The support gap is real. Non-enterprise customers regularly report tickets going unanswered for weeks. When your client's site goes down the night before a launch, a 3-to-5-business-day response window isn't acceptable.
This isn't to say Vercel is bad. It's to say Vercel was built for a specific developer workflow, and designers — with our image-heavy portfolios, client preview needs, and preference for visual tools over CLI config — deserve options that fit how we actually work.
Cloudflare Pages: The Free Hosting Designers Overlook
If you take one thing from this guide, make it this: Cloudflare Pages is the best free hosting option for designers in 2026, and most of us don't even know it exists.
What makes it different
Cloudflare Pages sits on Cloudflare's global network — 330+ data centers worldwide. But the feature that changes the game for designers is this: unlimited bandwidth, completely free, with commercial use allowed. No asterisks, no fine print, no up-to-100-GB cap.
I moved my own portfolio there six months ago and the entire experience cost me exactly zero dollars.
Here is what you get on the free tier:
Unlimited bandwidth and static requests — your portfolio can go viral and your bill stays at $0
500 builds per month (a build takes roughly 30 seconds — that's more than enough for active portfolio updates)
Free SSL certificate, auto-renewing, zero configuration
Custom domain support — connect your own URL in under two minutes
Unlimited team members — collaborate with other designers or developers at no cost
Automatic deploy on every Git push, just like Vercel
What it is like to use
The setup flow is refreshingly simple. Connect your GitHub or GitLab repository, select your framework (Astro, Hugo, Next.js, SvelteKit, plain HTML — it handles all of them), and click deploy. Your site is live in under a minute on a your-project.pages.dev subdomain.
For static portfolios — HTML/CSS, Astro sites, Hugo blogs, 11ty builds — Cloudflare Pages is genuinely unbeatable on value. The global CDN means your portfolio loads fast whether your visitor is in New York, Nairobi, or Nagoya.
The trade-offs worth knowing
If you are building a full Next.js application with server-side rendering, Cloudflare Pages plays catch-up. The @cloudflare/next-on-pages adapter works but does not support every Next.js feature the way Vercel natively does. For a static or mostly-static portfolio, though, this does not matter.
The dashboard UI is functional rather than beautiful — coming from Vercel's polished interface, it feels a little dated. But once your site is deployed, how often are you really staring at the dashboard?
Pro tip: If you need a contact form on your portfolio, pair Cloudflare Pages with a free Formspree account. Drop a single HTML snippet into your page, and submissions land in your email — no backend required.
Netlify: When You Want Forms, Previews, and Drag-and-Drop
Netlify is the closest direct alternative to Vercel, and in several ways that matter to designers, it is actually better.
Built-in forms — no backend needed
This is Netlify's standout feature for designers. Add a netlify attribute to any HTML form, and submissions automatically appear in your Netlify dashboard. No server, no API, no Formspree account. It handles spam filtering, file uploads, and email notifications out of the box. For a portfolio contact form or a client landing page collecting leads, this alone saves you from wiring up a backend.
Drag-and-drop deploys
You do not need Git. You do not need a terminal. You can literally drag a folder of HTML, CSS, and JavaScript onto the Netlify dashboard and it goes live immediately. If you are exporting a static site from Webflow, Framer, or hand-coding your portfolio, this is the fastest path from folder-on-desktop to live-website.
Branch previews for client review
Every pull request generates its own unique live URL. Share that link with a client, they see exactly what the site will look like — not a screenshot, not a mockup, but the real thing. When you push changes, the preview updates. It is the closest thing to a Figma commenting experience for live websites, and it is included on every plan including free.
The trade-offs
Netlify's free tier is generous — 100 GB bandwidth, 300 build minutes, 125,000 serverless function invocations per month — but the 300 build minutes can run out faster than you would expect if you are iterating heavily. The $9/month Personal plan is the lowest entry-level paid tier of any major platform.
Credit-based billing, introduced in late 2025, makes cost prediction harder than flat-rate pricing. And bandwidth overages at $55 per 100 GB are notably more expensive than Vercel's $15 per 100 GB.
Who it is best for: Designers who need contact forms, hate the command line, or want to share live previews with clients without teaching them how to use staging environments.
Self-Hosted for Creatives: Coolify on a $5 VPS
This is the option that surprised me most. I expected self-hosting to mean SSH-ing into a server at 2 AM, grepping through logs while something was on fire. Instead, I found a tool called Coolify that makes running your own hosting platform genuinely approachable — even for someone whose primary software is Figma, not a terminal emulator.
What Coolify actually is
Coolify is a free, open-source platform you install on your own server. Once set up, you get a clean web dashboard where you can deploy apps, databases, and services with the same git-push workflow you are used to from Vercel. It supports over 280 one-click application templates — WordPress, Ghost, n8n, Plausible Analytics, and practically every modern web framework.
The economics are what make it compelling: a Hetzner VPS with 4 GB of RAM and 40 GB of SSD storage costs roughly $5 per month. That single server can host multiple portfolio sites, client projects, and small web apps simultaneously. Compare that to $20 per user per month on Vercel Pro, and the math speaks for itself.
The real-world experience
After the initial setup — which took me about 25 minutes following Coolify's installation script — deploying a site feels familiar. You connect your Git repository, Coolify detects the framework, and builds go live automatically. You can even set up preview deployments per branch, though the setup is slightly more involved than Netlify or Vercel's automatic behavior.
One developer I interviewed runs over 100 services on Coolify for hackclub.com and described it as clearly the best self-hosted option, as long as you are comfortable with the trade-off: you are responsible for keeping the server updated, applying security patches, and monitoring uptime.
Is it right for a designer?
If you enjoy tinkering with tools and want complete ownership of your hosting stack, Coolify is genuinely empowering. You own your data, your costs are fixed, and there is no vendor lock-in. If a platform changes its pricing model, you are unaffected.
If you would rather never think about servers at all, stick with Cloudflare Pages or Netlify. The 25-minute setup and occasional maintenance is not much, but it is still more than zero.
Heads up: Self-hosting means you handle security. Coolify had a vulnerability disclosure in early 2026 affecting older versions — if you go this route, enable automatic updates and subscribe to their security announcements.
How to Migrate Without Breaking Your Portfolio
Switching platforms sounds intimidating — custom domains, DNS records, broken links. In practice, for a static portfolio, the process takes under 30 minutes and the risk of breaking anything is close to zero.
Moving to Cloudflare Pages
Sign up at Cloudflare and connect your GitHub or GitLab account.
In the Pages dashboard, click Create a project, select your repository, and choose your framework preset.
Cloudflare builds and deploys your site to a pages.dev subdomain. Confirm it looks correct — every page, every image.
In your domain registrar (Namecheap, Porkbun, Google Domains), update your DNS to point to Cloudflare's nameservers. Cloudflare provides these automatically when you add your custom domain in the Pages dashboard.
Wait for DNS propagation (usually 5 to 15 minutes). Your site is now live on Cloudflare Pages with your own domain.
Moving to Netlify
Sign up at Netlify and click Add new site, then Import an existing project.
Connect your Git provider and select your repository.
Netlify detects your framework automatically. Confirm the build settings and deploy.
Add your custom domain in the Netlify dashboard under Domain settings. Netlify handles the SSL certificate automatically.
Update your domain's DNS to point to Netlify's servers — the dashboard gives you the exact records to add.
Moving from Vercel specifically
If you are currently on Vercel with a custom domain, the migration is straightforward:
Deploy your site to the new platform first (before touching DNS).
Verify every page, image, and link works on the new platform's preview URL.
Remove the domain from your Vercel project settings.
Add the domain to your new platform and update DNS as instructed.
Wait for propagation and test again with your real domain.
The key principle: deploy first, switch DNS second. That way there is never a moment where your site is down.
Pro tip: Before switching DNS, run your old and new sites side by side in two browser tabs. Scroll through every page. Click every link. Check forms and images. Five minutes of manual testing prevents five hours of panic.
Which Hosting Platform Is Right for You?
After weeks of testing and conversations with designers who have switched, here is the honest framework I use to decide:
Choose Cloudflare Pages if your portfolio is static or mostly static (HTML, Astro, Hugo, 11ty, or a pre-built Next.js export). You want unlimited bandwidth, zero cost forever, and never want to think about usage limits. It is the safest default for 90% of designer portfolios.
Choose Netlify if you need a contact form without wiring up a backend, want to drag-and-drop folders instead of dealing with Git, or regularly share live preview links with clients for feedback. The built-in forms alone justify choosing it over Cloudflare Pages for client-facing work.
Choose Coolify on a VPS if you are comfortable with (or curious about) managing a server, want to host multiple client projects under one fixed monthly cost, or value complete ownership over your infrastructure. It is the cheapest option at scale and the most empowering one to learn.
Stick with Vercel if your portfolio is built with Next.js and uses server-side rendering or incremental static regeneration heavily. The integration is still best-in-class, and for a personal portfolio under the free tier's 100 GB bandwidth cap, it works fine. Just know what you are signing up for if your traffic grows.
The hosting landscape for designers has never been better. In 2026, you have genuinely excellent options that do not require becoming a DevOps engineer or accepting unpredictable bills. Pick the one that fits how you work, deploy your portfolio, and get back to designing.
Author