Siter.io for photographers · every price and plan limit checked 2026-09-03

Website builder for photographers

A portfolio is mostly photographs, and that decides everything: how the galleries sit, how much the page weighs, and whether you can sell from it. Siter.io publishes the layout you drew in Figma. It has no store, so prints get sold elsewhere.

Start for free -> See the plans

The short answer.

Siter.io turns a Figma file into a published website. For a photographer it fits when the site is a portfolio — the grid you spent an afternoon getting right is the grid that ships, and hosting is in the plan from $7/mo billed yearly, with a domain you already own pointing at it for nothing extra. It stops fitting the moment you need to take money on the site, or to run a journal that maintains itself.

The design is the site

Frames come across from Figma on every plan, including the free one, and you finish them on the canvas with your own uploaded fonts and on-canvas animation. The layout is yours rather than the nearest thing a theme could manage.
You cannot sell from it

E-commerce? No — listed as upcoming, with no date. There is no cart, no checkout and no paid downloads, so prints, licences and digital files are sold somewhere else and linked to. Settle that before you spend an evening building.

Where the print sales have to live.

Decide this first, because it changes the buttons on every page.

A site built here is a portfolio that sends people elsewhere to buy. That split keeps payment, tax and fulfilment off your own site, which is the part of a shop least worth running yourself. It only goes wrong when you find out halfway through building.
Three routes that do work

Sell on a storefront and link to it. Print labs and print-on-demand services host the shop, take the payment and ship the order. The cost is a visible jump to another domain at the moment of purchase, so design that hand-off rather than hiding it.

Take enquiries with a form. For commissions and licensing this beats a cart anyway, because the price depends on usage, territory and term. Solo includes 3 forms and Plus includes 5; Pro is unlimited. An enquiry form and a mailing-list form fit inside the smallest paid plan. How forms work here.

Leave shoot delivery where it is. Proofing galleries, client selects and high-resolution downloads are a different job, done by tools built for it. Making a website builder behave like one is how you end up with a site nobody can navigate.

How a portfolio gets built.

Five steps, and the first decides how the finished site feels.
1. Export images at display size.
2. Send the frames with the plugin.
3. Rebuild the interactions on canvas.
4. Lay out the three breakpoints.
5. Fill the SEO fields, then publish.
Image weight, in detail

A gallery of full-resolution exports is what makes a photography site feel slow, and no platform rescues you from it: a 6 MB JPEG weighs 6 MB wherever it is hosted. The fix happens in your export dialogue, before anything is uploaded.

Export at the size it is displayed. Measure the frame in your design. A photograph in an 800 px column needs an 800 px file, not the 6000 px one off the camera. Double it for high-density screens — roughly 2x the displayed width is the sensible ceiling, and one click in Figma’s export panel. Keep JPEG for photographs; PNG is for flat graphics and can multiply the size of a photograph for nothing visible in return.

Full-bleed images are the expensive ones. Something spanning a 1440 px layout at 2x is a 2880 px file. One as a hero is fine; twelve stacked down the homepage is the whole problem. Total what a visitor downloads before they scroll, and if that runs to tens of megabytes the layout is asking too much of a phone on mobile data — so check the homepage on one before you decide it is finished.

Four things that catch people out.

None of these is hidden. All four are easier to read now than to discover on the evening you meant to publish.

The prototype does not come across
The import brings the design, not the prototype. Click-throughs, hover states and smart-animate transitions wired up in Figma do not travel. Siter.io has its own on-canvas animations and interactions, so a fade-in or a hover state gets rebuilt there.
The import is one-way
Send a frame across and the two files stop being connected. Editing the Figma file afterwards moves nothing, because there is no re-sync. Decide early which copy is the master.
Three fixed breakpoints
Desktop, tablet and phone, rather than a fluid layout you tune at any width. For image-led work that is usually enough, since the layouts you need are one column, two columns and a grid.
How the breakpoints work
Video has a hard cap
YouTube embeds work on every plan. Direct upload is capped at 10 MB on paid plans, which is a few seconds of anything worth showing, so a showreel belongs on YouTube and arrives as an embed.

Which plan a portfolio actually needs.

Publishing is the thing you are paying for. The free plan builds and previews privately and cannot put a site on a public address, so the real starting line is from $7/mo billed yearly. What separates the paid plans, for a photographer, is pages rather than price.

Solo — $7/mo billed yearly

1 published website, 10 pages, 3 forms. Home, about and contact have already used three, so this suits a portfolio with a handful of series pages.
Plus — $12/mo billed yearly

50 pages and 3 published websites. The plan for a photographer who gives every series its own page, or who keeps commercial and personal work on separate sites.
Pro — $24/mo billed yearly

Unlimited pages, unlimited forms, 5 published websites, and you can download a page as HTML. Worth it once the archive keeps growing rather than settling.

Month to month costs more: $8, $14 and $28. On any paid plan hosting is included, the Made with Siter badge comes off, the per-page SEO fields open up — title, description, slug and share image — and a domain you already own points at the site at no extra cost. See the pricing table, connecting a domain and the SEO fields.

When this is the wrong tool.

You sell prints, licences or downloads from the site. There is no store, and you cannot code around it: paid plans give you site-wide head code and an on-canvas embed element, but no per-page body scripts.
You publish often. There is no CMS, so a new post means editing the design and republishing. If the writing is how people find you, host it somewhere built for that.
You need the site in two languages. Nothing in the product manages a second language, so a bilingual site means maintaining two sets of pages by hand.
Two of you need to be in the file at once. Real-time co-editing is listed as upcoming, which means it is not here today, so agree who is editing before you both open the site. Roles organise who can change what, though the exact permissions are not written down anywhere — check them in the app before you hand a client site over. How roles and seats work.
You do not design in Figma. The product assumes a file you already have. There are 20 templates inside the app if you would rather not start blank, but importing your own design is the reason to be here. See the templates.

If none of those is you, the fit is good and the rest is layout — which is better learned from sites built with Siter.io and the structure of a personal site than from another feature list.

Frequently asked.

What is the best website builder for photographers?

It turns on one question, and it is not about design. If you sell prints, licences or downloads from the site itself, you need a builder with a shop in it, and this is not one. If the site exists to get you hired, the question becomes how close the published page is to the layout you drew — and if you already work in Figma, sending that file over beats rebuilding it in somebody else’s editor.

Can I sell prints from a Siter.io website?

Not from the site itself. E-commerce is listed as upcoming with no date attached, so there is no cart, no checkout and no paid file delivery. The workaround is a print lab or print-on-demand storefront you link to, or licensing enquiries through a form and an invoice.

Can I run a blog or a journal on it?

There is no CMS, so no post list that fills itself and no archive by date. A journal here is a page you design and republish by hand — workable at a handful of entries a year, tiring at one a week.

How many pages do I get?

Solo at $7/mo billed yearly gives 10 pages, which is seven series after home, about and contact. Plus gives 50 and Pro is unlimited. One long scrolling page with series as sections counts as a single page, which is a fair way to stay on the smaller plan and often reads better anyway.

Do my Figma prototype interactions come across?

The import brings the design, not the prototype, and it is one-way with no re-sync afterwards. Siter.io has its own on-canvas animations and interactions, so a fade-in or a click-to-enlarge is rebuilt there. Try it on one gallery before promising a client a particular effect. More on the Figma plugin.

Is there a free plan I can put my portfolio on?

There is a free plan and it builds and previews privately, but it cannot publish to a public address. Treat it as the way to see how your own Figma file lands before paying anything. Putting the portfolio in front of clients starts from $7/mo billed yearly, and the custom domain, the SEO fields and the badge removal arrive with it.

Who else it is built for

Also useful: the Figma to HTML plugin, sites built with Siter.io and the full pricing table.

Your portfolio, the way you drew it.

Send the frames over with the Figma plugin, set the three breakpoints and publish. The free plan builds and previews as much as you like; publishing to your own domain starts at $7/mo billed yearly.
Get the plugin ->
Start for free with Siter.io
Start for free ->