CLIENT WEBSITE PREVIEW
Share a client website preview link
A client website preview is a real browser preview instead of a ZIP, a screenshot or a local address only you can reach. Upload the built files, share one URL, and let the client click what is wrong and type what it should say.
Free plan, free SSL, no credit card.
- 15
- republishes a day, one per round of comments
- 5
- expiry options: 6 hours, a day, a week, a month, or a date
- Starter
- is where edge-enforced password protection starts
- 5,000
- visits a month included on the free plan
How it works
Three steps, start to live link
-
Upload the build
Drop the finished HTML or ZIP that your workflow produced. What the client sees is exactly what you uploaded, on their own device and browser.
-
Send it for review
A <a href="/features/client-review">review link</a> opens on any device, with a bar the client uses to approve the version or click the thing that is wrong and say what it should be.
-
Answer and republish
Each comment arrives on the element it names, so the fix is aimed rather than guessed. Publish, and the address they already have shows the new version.
The plain answer
What is a client preview link?
A temporary public address for a site that is not finished, so the person reviewing it can open the real thing in their own browser. It exists because the two obvious alternatives both distort the review: a screenshot cannot be scrolled, clicked or opened on a phone, and a local development address only resolves on your machine.
The property that makes a preview link work is that it is stable while the content behind it is not. You send the address once, at the start of the review, and every revision after that lands at the same place. Nobody has to be told "ignore the old link", nobody comments on a version from four days ago, and the link in the calendar invite for the review call is still correct when the call happens.
The second property is that the feedback comes back attached to the page. A review link carries a bar the client did not install and does not need an account for: they approve the version, ask for changes, or click any heading, paragraph or image and type what should be different about it. Each of those lands in your dashboard naming the element in its own words, which is the difference between "the headline should mention our new hours" and a screenshot with a circle drawn on it.
The third is that it is not public in the sense that matters. Unfinished work should not be indexed or forwarded outside the project. Review addresses are served noindex and no-referrer, a password is one field, and the link can be set to close on its own once the round is over. The pricing page lists which tier carries which allowance.
Who it is for
The people who reach for this
-
Designers
A coded design in front of a client on their own phone, where the type and spacing actually land.
-
Developers
A built branch shared for sign-off without giving anyone access to a repository or a staging server.
-
Marketing teams
A landing page reviewed by legal, brand and the person who asked for it, from one address.
-
Agencies
Several previews in flight, each on its own address, each expiring when its round closes.
In detail
What you actually get
The address stays put while the site changes
A review is several versions long. Everything else about the process assumes the link is constant, so that is the property the product protects. When the review ends in a handover rather than a launch, see <a href="/static-hosting-for-freelancers">static hosting for freelancers</a>.
- Publishing a revision swaps the content behind the same address, atomically.
- No visitor ever sees a mixture of the old and new build.
- From Pro, going back to the version the client commented on is one click.
Not findable, not forwardable
Unfinished work leaking is a real cost, and "nobody will guess the URL" is not a control. Three that are:
- Password protection from Starter, checked at the edge, so assets are covered and not just the landing page.
- Free sites are served noindex, so a preview cannot appear in a search result.
- Expiring links from Starter: 6 hours, 1 day, 7 days, 30 days, or a date you set. The link flips to an expired page and can be restored later.
They comment on the page, not about it
The review bar is served by us, from our domain, onto your page. Nothing to install, no account for the reviewer, and every comment is recorded against the element it was left on. <a href="/features/client-review">Client review</a> is the feature in full.
- Approve the version, ask for changes, or pin a comment to any element on the page.
- A comment can go straight to the AI builder with the element already selected.
- The client is told a comment is done once a version has gone live carrying it, never before.
- A link shows one version, so approving version twelve can never be read as approving thirteen.
No card required
What the free plan includes
A single preview runs on the free plan indefinitely. The controls that make a preview private start one tier up.
- 1 live site on a real free plan, not a trial of a paid one, and no card to start.
- Up to 25 MB per upload and 25 MB of storage across the account.
- 5,000 visits and 5 GB of traffic a month.
- HTTPS with a real certificate, issued and renewed for you.
- Up to 15 publishes a day, so you can iterate without asking permission.
- The deploy-time security check, which reads what you published and warns about a stray .env file, a .git folder, a private key or an API key left in your JavaScript.
- A small Droply badge in the corner of the page. Removing it starts on Starter.
- Free sites are served noindex, so search engines do not list them. Search visibility starts on Starter.
Droply vs Netlify Drop
How this compares with a quick drag-and-drop deploy
Netlify Drop is the fastest way to get a folder online at a large host and a reasonable choice for a one-off look. These rows matter once the preview has to last through a review.
| Droply | Netlify Drop | |
|---|---|---|
| Is the link yours straight away? | Yes. Publishing needs an account, so there is nothing to claim afterwards. | No. An anonymous drop creates a temporary project you have one hour to claim. |
| Same address after a revision | Yes. Publishing replaces the content behind it, atomically. | Yes. An updated folder publishes as the latest production version of the same project. |
| Password protection | From Starter, enforced at the edge before any file is served. | From its Pro plan. An unclaimed drop gets a temporary password of its own, which is not the same thing. |
| Expiring preview link | From Starter: 6 hours, a day, a week, a month, or a date you pick. | Not offered. An unclaimed drop expires in one hour whether you want that or not. |
| Rollback to a reviewed version | From Pro, in one click. | Yes. Publishing a previous deploy is instantaneous and does not rebuild. |
| Size guidance | 25 MB per upload on free; substantially higher on paid tiers. | Deploys under 50 MB work best, and individual files over 10 MB may cause the deploy to get stuck. Larger projects are told to use the CLI. |
| Account needed to view | No. The client opens a link. | No. |
| What the product is for | Publishing finished files, previews included. That is the whole product. | The on-ramp to a Git-based platform. |
Netlify Drop details come from Netlify's own documentation, checked 8 September 2026: the Netlify Drop quickstart (drag-and-drop shapes, the temporary password on an unsigned-in drop, the 50 MB and 10 MB size guidance, redeploying to the same project), the create-deploys page (\"a temporary project with a live URL that you can claim within one hour\"), the password-protection page and the manage-deploys page. Product features can change.
When Droply is the wrong choice
A preview link is a viewing surface, not a review tool or a staging environment. If the process needs more than "look at this", something else fits better.
- You need threaded discussion, assignees and due dates on each comment. The comments here are a queue you work through, not a project tracker.
- The site under review is a dynamic application that needs a database or a login to behave correctly. A static preview will not represent it.
- You need per-reviewer access control and an audit log of who saw what. One shared password is the level of control available here.
- You need a database, a login system, or code that runs on the server. Droply serves files; it does not execute your application.
- You want a build to run on every push to a repository. Droply has no Git integration and no CI: you build locally and upload the result.
- You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot.