Loading…
Spend an afternoon reading through any design or coding community and you'll see the same question in a dozen different words.
How do I make a personal website by myself?
Not a company site. Not a SaaS landing page. A personal site: your name, your work, a short bio and a way to reach you.
The replies usually split into two camps. One says learn HTML, CSS and JavaScript for six months. The other says pay for a builder and be done with it. Both answers are outdated.
You can now describe the site you want, have an AI tool write the first version, and put it online for free in an afternoon.
Making a website has never been easier. This is the guide I wish I'd had.
Make a one-page site first. Write down who you are, what you do, three pieces of work and how to reach you. Give that to an AI tool and ask for one index.html file with the CSS inside it. Open the file in your browser, fix what looks wrong, push it to GitHub and connect the repo to Vercel.
That's the whole launch. No paid host. No server. No framework required.
You can have a live URL today and make it better next weekend. Everything below is detail on top of that.
I've had this conversation enough times to know the wording changes. The questions don't.
Start with the content, not the code.
A personal website is four blocks:
That's v1. No blog. No dark mode toggle. No animated cursor. Those are v4 problems.
Once the content exists, the build is small: one page, one stylesheet, a few images. The question feels huge because people imagine a product. It's a page.
No. Not for a personal site.
AI can write the HTML, CSS and JavaScript from a plain description. You still need to do three things:
That's enough. You don't need to know what a closure is. You do need to know what a file is, where the folder lives and how to refresh a browser.
If you want to understand what you're shipping, spend an hour on HTML basics after launch. You don't need to become a developer to keep a static site alive.
For a static personal site: $0 to launch, $10–15 a year if you want your own domain.
Hosting is free on GitHub Pages, Vercel, Netlify and Cloudflare Pages. The free URL looks like yourname.vercel.app or yourname.github.io. The free tiers of ChatGPT, Claude and OpenCode are enough to build the site.
A builder is the optional expense. Framer starts at $10/mo billed yearly, Wix at $17/mo, Squarespace at $16/mo, and Carrd is $19/year for a one-page site. That's fine if you want a template and zero maintenance. It's a bad deal for a five-page portfolio you'll edit twice a year.
I priced all of it below: AI tools, hosts and builders.
It depends on what you want to own.
For a personal site, static HTML is the sweet spot. For a site like this one, with a blog, search and structured data, a framework is worth it.
Yes, for a personal website.
The work is mostly layout and copy, which is exactly what AI is good at. It can produce a clean hero, a work grid and a contact section in one pass.
The catch is the last 10%. AI is weaker at spacing, mobile edge cases and the small decisions that make a page feel designed. You are the art director. Ask for three directions, pick one, then fix it one change at a time.
People are often surprised by how far AI gets them, then stuck on the last few details. That's normal.
All four of these have a free tier that a personal site will never outgrow:
The setup is the same everywhere: put the files in a repo, connect the repo, pick the branch. No server to configure.
No. Launch on the free subdomain.
A domain matters when you have something worth pointing at it. Buy one later from a registrar like Namecheap or Porkbun, connect it in the host's dashboard and keep the free URL as a redirect.
Don't buy hosting with the domain. For a static site, you don't need it.
Yes, for one reason: it's the only profile you own.
Your Instagram, LinkedIn and Dribbble are rented land. The algorithm changes, the format changes, the account can disappear. A personal site is one link you control, with your work presented the way you want.
It doesn't need traffic to be useful. It needs to exist when someone Googles your name. A simple site beats no site.
Ten years ago, a personal website meant learning a stack, renting a server and configuring DNS. Today the hard part is writing three honest paragraphs about yourself.
Three things changed:
You don't need a CS degree, a subscription or permission. You need a clear brief and a couple of hours. The tools are genuinely good enough now. The taste is still yours.
There are two honest paths. Both work. Pick based on how much you want to maintain.
Omid Tootoonchi is an Iranian director and editor based in Tehran. I built his site as plain HTML pages: index.html, works.html, contact.html and one page per film.
No framework. No database. No build step. Every page is a file you can open, edit and upload. The folder is the website.
The whole site is a handful of pages sharing one stylesheet. That's why it loads fast, costs nothing to host and will still work in ten years. You can view it at omidtootoonchi.ir.
For a portfolio, this is still the most underrated option. AI can generate the first page in minutes, and every change after that is a text edit.
The site you're reading is the other path. It runs on Next.js and Node.js, uses shadcn/ui for components, Tailwind for styling and MDX for the blog. It has tags, search, a sitemap, structured data, a Spotify widget and a page transition.
That's more moving parts. You don't need any of it for v1. But it's the right choice if you want:
AI can scaffold this too. Ask for "Next.js with the App Router, TypeScript, Tailwind and shadcn/ui", or start from a template and edit it. The trade-off is maintenance: dependencies, builds and deploys. Vercel's free tier covers a personal site like this one.
My advice: start static. Move to a framework when you feel the static site holding you back, not before.
Any of these can write a personal site. The tool matters less than the brief you give it.
ChatGPT is the all-rounder. Ask for a single index.html file with inline CSS. Upload a screenshot of a site you like and ask it to match the spacing and type. Iterate in the same chat so it remembers the decisions.
Claude is strong on long files and design detail. Give it your content, ask for three directions, then pick one and refine it. It's patient with "move this 8 pixels up" feedback.
OpenCode with free models is different. It's an open-source coding agent that works inside your project folder. It can create files, run commands, read errors and fix them. Free models are enough for a one-page site, and it's the tool I use when I want changes made directly in the codebase instead of pasted from a chat window.
If you've never coded, start with ChatGPT or Claude and one HTML file. If you want a real repo and a project that grows, use OpenCode.
All three have a $0 path that is enough for a personal site. You do not need a subscription to follow this guide.
US list prices, checked October 2026. Taxes are excluded; annual billing is noted. Prices change, so confirm on each provider's pricing page before you pay.
The free tiers are not toys. A one-page site is a small generation: one file, a few sections and two or three rounds of layout fixes. You will likely stay inside the free limits. If you iterate for hours, ChatGPT Plus or Claude Pro at $20 a month buys more room, but it is optional. OpenCode is the cheapest way to let an agent edit files in your project, because the app is open source and its free models cost $0 per token.
Two catches. Free model lists rotate, so check the current models in OpenCode before you start. And free plans have usage limits; if a tool stops mid-task, start a new chat or switch models instead of buying a plan you only need for one afternoon.
"Modern and clean" gives you generic output. A reference site gives the model something concrete to aim at.
Pick a site whose layout, typography or color mood you like, and ask the AI to mimic that style with your content. Then:
A line you can paste into the prompt:
Use [reference URL or screenshot] as a visual reference for layout, spacing, typography and color. Do not copy its text, logo or images. Build my site with the content below and make the design my own.This works with ChatGPT, Claude and OpenCode. If the tool can't open a URL or read a screenshot, describe the reference in words: layout, type, spacing and the parts you want to keep.
Copy the prompt that matches the path you picked, replace the brackets with your details and paste it into ChatGPT, Claude or OpenCode. Use the copy icon in the top-right corner of a block to copy the whole prompt.
Use this with ChatGPT or Claude if you want one file, no build step and a site you can open by double-clicking.
Build me a one-page personal website in a single index.html file, with the CSS and JavaScript inline.
Who I am: [name], [role] based in [city].
What I do: [one sentence].
Sections:
- Hero: name, role and a one-line intro.
- Selected work: three projects with title, one-line description and link.
- About: two short paragraphs in first person.
- Contact: email and two social links.
Style: dark background, one warm accent color, generous spacing,
large serif headings, no animation, system fonts only.
Design reference (optional): [URL or screenshot of a site you like].
Borrow its layout, spacing, typography and color mood, but do not
copy its text, logo or images.
Requirements: responsive down to 360px, semantic HTML,
accessible contrast, meta title, meta description, Open Graph tags,
no external libraries, no build step.
Write the full file. Use my real copy, not lorem ipsum.Use this with OpenCode if you want a real project, or with ChatGPT or Claude if you are happy to copy files into a folder. It produces the setup this site uses: Next.js, TypeScript, Tailwind and shadcn/ui.
Build me a personal website with the current Next.js App Router, TypeScript, Tailwind CSS and shadcn/ui. Work directly in this folder and create every file.
Who I am: [name], [role] based in [city].
What I do: [one sentence].
Pages:
- Home: hero with name, role and a one-line intro; three selected projects; short about; contact.
- Works: a responsive grid of projects with title, one-line description, image and external link.
- Blog: a list of MDX posts from content/blog and a post template with title, date and body.
Style: dark theme, one accent color, generous spacing, serif headings, minimal animation.
Design reference (optional): [URL or screenshot]. Borrow layout, spacing,
typography and color mood; do not copy text, logo or images.
Requirements:
- Mobile-first and responsive down to 360px.
- Semantic HTML and keyboard-accessible components.
- Per-page metadata: title, description, canonical, Open Graph and Twitter tags.
- Person and WebSite JSON-LD on the home page.
- No database or CMS. Keep content in typed data files.
- Use next/image, next/font and the built-in sitemap.
- Add a README.md with local setup and Vercel deploy steps.
Write the full file tree and the contents of every file. Use my real copy, not lorem ipsum.Then improve it one instruction at a time:
Specific beats clever. "Make it better" gives you a different site. "Reduce the gap under the hero by half" gives you the site you meant.
Name, role, three projects, contact and one reference site (URL or screenshot). This is the part AI can't do for you.
Ask for one index.html file. Resist the urge to add a blog, a CMS or a framework on day one.
Open the file in your browser. Resize the window to phone width. Click every link. Read every line out loud.
Copy first, then spacing, then mobile, then polish. Don't mix all four in one round of feedback.
Create a repository and upload the folder. Keep index.html at the root. This is your backup and your deploy source.
Import the repo, keep the default settings and deploy. For a static site there is nothing else to configure.
Send the link to three people. Add a domain when you're ready. Update the work section every few months.
A static site is just files. The host sends the files; the visitor's browser does the rest. You don't need a server, a database or a monthly plan.
US list prices, checked October 2026. Vercel's Hobby plan is for personal, non-commercial projects, so read the fair-use terms if the site is also your business. Netlify's free plan has a hard 300-credit monthly limit (about 15 GB of bandwidth); that is plenty for a portfolio, but a viral page can pause it. Cloudflare does not charge for static requests or bandwidth; you only pay if you add Functions.
Your free URL will look like yourname.github.io, yourname.vercel.app, yourname.netlify.app or yourname.pages.dev. Every one of these supports custom domains, and all four are enough for a personal site. The only real cost is the domain: $10–15 a year from a registrar. Connect it in the host's dashboard and keep the free URL as a backup.
A builder is not a host. You pay for the editor, the template and the hosting together. If you would rather drag things around than edit files, these are the real entry prices:
US list prices, checked October 2026, annual billing unless noted; taxes and add-ons are extra. Domain names may be included in the first year of an annual plan, so check the checkout. Paid plans mostly buy a custom domain, more bandwidth, more pages and no builder badge.
One year of Framer Basic costs about the same as eight to twelve years of a domain. One year of Wix Light costs more than ten years of Carrd. If you need a visual editor, pay for the one you will actually use. If you just need a page that exists, the free path is not a compromise.
Write like you talk. The site is not the work. It's the door.
I wrote about the common mistakes when building with AI if you want the longer version. Most of them apply to websites too.
Yes. Use a static site and a free host like GitHub Pages, Vercel, Netlify or Cloudflare Pages. The free tiers of ChatGPT, Claude and OpenCode are enough to build it. You only pay if you want a custom domain, and that costs about $10–15 a year.
No. AI can write the HTML and CSS for a personal site. You need to be able to edit text, test the page on a phone and describe what looks wrong. Basic HTML knowledge helps after launch, not before.
Yes, for a personal site or portfolio. Give the tool your real content, a reference site (URL or screenshot) for layout and type, and clear requirements. Ask it not to copy the reference's text, logo or images. Expect three to five rounds of fixes, mostly spacing and mobile layout. You are still the editor.
No. Static hosting is free on GitHub Pages, Vercel, Netlify and Cloudflare Pages. Paid plans exist (Vercel Pro at $20/user/mo, Netlify Personal at $9/mo, Cloudflare Workers Paid at $5/mo for Functions), but a personal site rarely needs them. A domain is optional; the free subdomain is fine to launch with.
For a personal portfolio, a static site is simpler and cheaper. Use WordPress if you want a blog with plugins and don't mind hosting and updates. Use a builder if you want a template and zero maintenance and are happy with the fee: Framer starts at $10/mo billed yearly, Wix at $17/mo, Squarespace at $16/mo and Carrd at $19/year.
An afternoon for a first version with AI and a free host. A weekend for something you're proud to share. Most of the time goes into writing the content and fixing the mobile layout, not the code.
Show what you have: school projects, personal experiments, writing, photography, open-source contributions. Two or three honest pieces are enough. The site can grow with you.
Yes. It's the one profile you own and control. It doesn't need traffic to be useful; it needs to exist when a client, recruiter or collaborator looks you up.
Pricing and plans (checked October 2026):
Official docs: GitHub Pages · Vercel · Netlify · Cloudflare Pages · Learn HTML
The best personal website is the one that exists. Pick a path, write the brief, ship the first version this week. You can always make it better once it's live.
Keep reading
A human guide to the Figma MCP server in 2026. What each command does, what gets triggered inside Figma, localfig, prompt examples, and how to connect it with Claude, ChatGPT, Cursor, and other AI harnesses.
36.9% of PM teams now use AI for limited workflows and 62% save 4+ hours weekly. Tools, prompts, and workflows that actually 10x productivity.
A practical guide to making a simple browser game with AI and putting it online for free, with real Reddit answers, tools, screenshots and a 7-step plan.