How to Share Design Mockups With a Client Privately
To share design mockups with a client privately, put them on one web page that only the people you name can open, and send that link. Each mockup can be its own page, or your AI can lay all of them out on a single page that you publish as a folder. Either way the client opens a link on their phone, confirms their email once, and sees the designs. Nobody who was not named gets past the first screen, and when round two is ready you update the page and the link stays the same.
This post covers the two ways to do that, which image formats work and which are refused, how to decide who can open the page, how to run feedback rounds without sending a new link every time, and the things a page does not do, so you can decide before you send anything.
Why share design mockups with a client privately
You exported six screens, or your AI produced a landing page in three colour directions, and now the client needs to see them. The usual options each cost you something.
- Attaching PNGs to an email sends copies. The client opens them one by one, out of order, at whatever size their mail app chose, and "final_v3" lives in their inbox forever next to "final_v2".
- A zip is the same problem with an extra step. What to send a client instead of a zip file goes through why it is the wrong shape for anything a person is meant to look at.
- A public link to an image host is open to anyone who has it. Forward the email once and the unreleased homepage is in a group chat.
Mockups are usually confidential and usually not finished, which is the combination a public link handles worst. What you want is one address that opens for your client and nobody else, and that you can change without a new link.
One image, or one page with all of them
There are two ways to publish mockups on SnapHost, and which one you want depends on how many there are.
For a single design, drag the image file in. It gets a page of its own, with the image served so that downloading works, and that page has one link. This is the right move for one hero screen or one poster.
For a set, ask your AI to build the page. Tell Claude or ChatGPT something like "make a single page that shows these six screens in order, with a heading above each one and the two colour directions side by side", and you get an HTML file and a folder of images next to it. Zip the folder and publish it: SnapHost serves the whole thing and picks the starting page itself. The result is a gallery that reads top to bottom, with your captions, the way you would have walked the client through it in a meeting.
One rule for that page: the images have to be in the zip. A published page does not pull in files from other places on the web by default, so a page that points at images on some other server shows empty boxes where they should be. The same goes for fonts, so have your AI include the font file rather than link to it.
A page and its files together can be up to 50 MB. Screens exported at two times resolution add up quickly, so if the zip is refused for size, export them at the size they will be viewed.
Formats that work, and the ones that are refused
SnapHost takes PNG, JPG, GIF, WebP, AVIF, SVG and BMP files, both as single images and inside a zip. That covers an export from any design tool and anything an AI image model hands you.
It does not take HEIC, which is what an iPhone photo arrives as, nor TIFF, nor a layered PSD. Upload one of those and the refusal names the export that will work, a JPG or a PNG in all three cases. For a Photoshop file that is a good thing: the flattened PNG is the picture, and the layers and your working notes stay on your machine.
One caveat about photographs. A photo is carried as it is, so if the file holds a capture time and a location, they travel with it, and a reader who downloads it can read them. Design tool exports do not usually carry that, but a phone photo of a whiteboard sketch does. Screenshot it first if that matters.
Who can open the page
A page has one link and a setting that decides who gets past it. Restricted means only the people you name can open it, and each one confirms their email before any content loads. Anyone with the link means exactly that, no sign in.
For mockups, restricted is the one you want. You add your contact at the client by email, or the whole client company at once by its domain, like acme.com, so the design lead can show the CEO without asking you to add anyone. If someone you did not name opens the link, they can ask for access from the page itself, and approving the request adds them to the list.
Two more controls fit client work well. A one-time link lets one person open a restricted page once, with no sign in, if it is used within seven days, and it is spent after a single sitting of about an hour. That suits the stakeholder who will look once and never come back. A link expiry puts an end date on the whole page, after which the link stops working until you clear the date. The full set, including taking a page offline without deleting it, is in sharing and access control.
What each plan gives you here: on Free you can have up to three pages at a time, each private to up to three people or public, and a new page starts out public, so name your readers before you copy the link. On Pro a new page is restricted from the start, there is no cap on pages or readers, and you can add a password or an end date to any page.
Rounds of feedback without a new link each time
Mockups go through rounds. With attachments, each round is a new email and more files in circulation, and by round three nobody is sure which set is current.
With a page, you publish the new version and the link stays the same. The client opens the address they already have and sees round two. That works on every plan. If you want the next round set up before the client sees it, keep the new page as a draft; nothing is reachable until you publish it.
On Pro, each update is also saved as a version, the ten most recent are kept, and you can go back to an earlier one in one step while keeping the same link. The client who says "actually, the first direction was better" gets the first direction back without you digging through exports. The rollback is saved as a version too, so moving forward again is one more step. Versions and rollback has the details.
If your AI is connected to SnapHost, the round is shorter still: make the changes in the same conversation, say "update the mockups page", and the page is replaced at the same address. Connecting is optional and takes about two minutes, once. Without it, you drag the new zip in yourself and get the same link.
Knowing whether they looked
Every open of a restricted page is recorded with the time and the reader's email, since they confirmed it on the way in. Requests from people who were turned away are recorded too. So before the review call you can see that jane@acme.com opened the page on Tuesday and her colleague has not yet.
Be clear about what the log is. It records the open, not how long they looked or which screen they lingered on. A page opened with a view password alone is not logged at all, which is one reason the list beats a password for client work.
What a page does not do
Three limits, said plainly, because they decide whether this is the right tool for a given round.
- No pinned comments. A page shows the designs. It does not let the client drop a pin on a button and type a note. Feedback comes back by email or in the call, with the page open on both sides. If a round needs annotation on the canvas, your design tool's own review mode is the better fit for that round.
- The image can always be saved. A single image is its page, and a reader can always download it. On a page your AI built, the images are files in the page like any other, and a browser can save those too. A restricted page controls who gets in, not what they do afterwards. If a client must never hold a copy, do not send them a picture at all.
- It is for looking, not editing. If the client's designer needs to work on the files, send the source files. The page earns its place when the designs are ready to be seen.
Setting it up
- Export the screens as PNG or JPG at the size they will be viewed. Convert any HEIC, TIFF or PSD first.
- For one design, drag the file into SnapHost. For a set, ask your AI for a single page with the images in a folder beside it, zip the folder, and drag the zip in. Or, if your AI is connected, say "publish this to SnapHost".
- If you are on Free, open Share and add your client's email before you copy the link, because a new page there starts out public. On Pro the page is restricted from the start, so add the names, or the client's domain, and send.
- Open the page yourself on your phone before the client does. Check every image loaded; an empty box means a file was missing from the zip.
- For round two, publish the new version to the same page. Look at the access log before the call if it matters who has seen it.
Free pages live at sites.snaphost.ai with a small SnapHost mark in the corner. Pro is 19 euros a month per member who can publish, the people who look cost nothing, and it is where passwords, end dates, the company-wide domain entry and version history live. Pricing has the current plans, and what you can publish has the full list of formats beyond images.