How to Build and Publish a Portfolio Website with AI Without Coding

Building a portfolio site with AI comes down to four stages: take stock of your work, generate the copy, generate the site itself, and publish it on free hosting. Even without any coding skills, it often takes half a day to a day to get it live.

Many freelancers, writers in particular, put off building a portfolio site for years and get by with sending a PDF of past work whenever a prospect asks. The reasons are usually simple: no budget to hire a web designer, and no skills to build it themselves. AI shrinks both of those obstacles. Here is the process, organized as a step-by-step guide for anyone starting from scratch.

Before asking AI: take stock of your work

The first step is not opening an AI chat. It is writing down the material you want to show. AI is good at building the structure of a site and polishing the wording, but only you have the actual track record. Skip this step and just ask for "a cool portfolio for a freelancer," and you'll get a generic template filled with made-up copy that you'll end up rewriting from scratch.

Write down three kinds of material:

• Around five representative projects (what you did, for whom, in what role, and what came of it)
• Material for your bio (background, specialties, availability, how to contact you)
• Images you're allowed to use (a headshot, screenshots of your work, and so on)

The common sticking point for freelancers is confidentiality. Projects where you can't name the client or show the deliverable are not unusual. In those cases, abstract it to industry, company size and role. Something like "Planned and produced articles for the owned media site of a mid-sized manufacturer" is a level of detail most contracts allow. AI can speed up the work of drafting alternative phrasings at different levels of vagueness, though the final call should be yours, made alongside a check of your contract.

Once the material is ready, AI can handle most of what follows.

Can you really publish without writing code?

Yes. But how much hands-on work you do depends a lot on which route you take. There are three broad routes:

The first route takes the most legwork but teaches you the most. Ask for "a one-page portfolio site as two files, HTML and CSS," paste in your material, and you'll get a set of files you can open right away. Then put them on free static hosting such as GitHub Pages, and you're live. Uploading and checking the URL remain your job, but for a portfolio with only a few pages, this route is entirely sufficient.

The second route assumes developer tooling like a code editor and extensions, so it's a detour unless you already use a dev environment. There's no need to start here for a single portfolio page.

The third route is the chat-integrated approach: what you build in a chat goes straight to a public URL, with no server setup or file uploads. Desktop apps such as osFoundry work this way, and its apps feature shows concretely what that looks like. If publishing is where you're most likely to get stuck, starting with this type of tool makes it much easier to finish.

One note about the URL once you're live. The hosting provider's free URL is fine at first, but if you'll put it on business cards and email signatures for years, a custom domain is worth considering. It often costs around $10 to $20 a year, and if you work under a business name, getting one early saves you a migration later.

The copy matters more than the design

You don't need to spend much time agonizing over design. Clients don't visit to admire the layout; they visit to decide whether they can hire you. Even a template-like look works for sales purposes as long as your work and terms are easy to read. (Designers, whose site is itself part of the portfolio, are the exception.)

The copy, on the other hand, is worth real time, and that's where AI earns its keep. Three tips:

1. Give it material and let it write. Hand over your bullet-point project notes and ask: "Write a description of each in three sentences or fewer, for a hiring manager to read." Describing your own work is oddly hard, so having it written once in someone else's voice means you start from editing instead of a blank page.

2. Check for exaggeration. AI tends to fill gaps with plausible content, so check each entry for results you never provided, especially specifics like numbers or awards. A portfolio is a sales document. A false claim in it is a trust problem on a completely different level from a typo. Assume every fact in the generated text needs checking against your original notes.

3. Specify the reader and the situation. Conditions like "assume a first-time client skimming for 15 seconds" or "order it to reduce a buyer's concerns before hiring" push the copy toward what the reader wants to know, rather than what you want to say.

FAQ

How much does it cost?
Free hosting is enough, and you can start with a chat AI's free tier. The main costs are a custom domain (often around $10 to $20 a year) and possibly a paid AI plan if you do a lot of regenerating. Compared with hiring someone to build the site, the total is usually smaller by an order of magnitude or more.

Will it look decent without any design knowledge?
Yes. The trick is to put the feel of sites you like into words. Instructions like "generous whitespace, white background, no more than two colors, few photos" are enough to get the direction across. Prioritizing a clear, top-to-bottom list of your work over fancy animations tends to bring in more inquiries.

I built one, but I never keep it updated.
Make it part of wrapping up each project: write a short note about the work, hand it to AI, and turn it into portfolio copy. On the site itself, you only touch one block in the project list, so adding an entry takes a few minutes. A portfolio that hasn't been updated in years can by itself suggest you're no longer taking work, so a small, sustainable update habit is worth setting up.