Publish

Put a project live straight from the editor, or export it as standard web source code and deploy it anywhere. Both paths are open on every plan, so nothing you build is locked in.

Publish on Lediv

Click the Publish icon in the header.
Choose the address your site will live at.
Click Publish site.

The site is live within seconds, and publishing again updates it in place. A new version goes live only once it is fully uploaded, so visitors never see a half-updated site.

Only the project owner can publish. People you invite edit the project with you, and on a team project publishing belongs to the team owner.

Every file in public/ keeps exactly the address you gave it for as long as the site is published. Shared links and fetch() calls in your own JavaScript keep working after every republish, and visitors get the new version the moment you publish, with nothing to configure or purge.

The Publish panel

Republish pushes your current work live. Next to the address, three buttons name themselves when you hover them.

The pencil changes the lediv.site address.
The crossed-out eye hides the site from search engines.
The bin unpublishes it.

On Pro, History keeps the last 10 deploys. The refresh icon on an earlier one, Restore this deploy, puts it back live. For the owner, the panel ends with Download project, which exports the whole project as a ZIP.

An address you release is free immediately, and anyone can take it. Nothing is forwarded, and we cannot get it back for you.

Moving a project to the trash takes its site offline, on your custom domains too, and reserves its lediv.site address so that restoring the project brings the site back at the same address. While reserved, the site still counts towards the three a Free plan may publish, and no timer frees it. Unpublish before trashing, or empty the trash, to get the slot back.

Two things never come back after a restore. The earlier deploys are removed, so there is nothing to roll back to, and a preview link you shared is turned off for good. Emptying the trash goes further. It releases the address for anyone to take and disconnects your domains. Neither can be undone.

Sharing a preview before you publish

Create a preview, under Preview link in the Publish panel, builds the project at its own address so you can show it to a client or a teammate. It works on a project that was never published, and on a published site it leaves the live version untouched. The link lasts seven days, and the panel counts down what is left.

Update preview refreshes it with your latest work at the same address, so a link you already sent shows the new version. The seven days restart once the new build is ready, so a preview you keep updating stays up. Two buttons beside it, named on hover, copy the link and delete the preview.

A preview is always kept out of search engines, and moving the project to the trash turns it off. When it runs out, its pages stop being served and the next preview gets a new address, so the old link stays dead. Deleting the preview does the same thing sooner.

Anyone with the link can open it. The address is long and unguessable, and search engines are told to skip it, but it is not a password. A preview on a project you never published also takes one of the sites your plan allows while it lasts. Deleting the preview gives that back straight away.

Keeping a site out of search engines

Some sites are not meant to be found, like a client review, a staging copy or an invitation page you send by hand. The crossed-out eye turns this on and off at any time. Before the first publish, you can tick Keep this site out of search engines so the site goes live with it already on.

While it is on, every address the site answers on carries the instruction, your own domains included. While it is off, the site is offered for indexing, except on the lediv.site address of a site with a custom domain. That address always carries the instruction, so your own domain is the one that gets indexed.

This hides the site from search engines, it does not make it private. Anyone with the address can still open it, and honoring the instruction is up to each search engine.

Domains and redirects

On Pro a published site can also answer at a custom domain. It takes one DNS record, and the panel walks you through it. See Custom Domains for the record, the apex, several domains on one site, and what to do when one stops working.

All lediv.site addresses share one domain, so a cookie set there is visible to every other published site. Keep state in localStorage or prefix cookies with __Host-. A domain of your own shares nothing with other sites.

A _redirects file at the project root sends visitors from old paths on your site to new ones. Lediv applies it when you publish on Pro. On any plan it travels with the export, and hosts that read the same file honor it. See Redirects for the format.

What each plan includes

Free publishes up to 3 sites, each keeping only its latest deploy.
Pro publishes unlimited sites, with custom domains, redirects, and the last 10 deploys of each site, any of which you can roll back to in one click.

If your plan lapses, sites you already published stay online and publishing falls back to the 3 sites of the Free plan. The people you invited lose access to your projects, export included, until you take up Pro again. Connected domains keep serving for 30 days, as Custom Domains explains.

The deploy history goes within a day, leaving only the live version, so go Pro again straight away to keep it. If you had rolled back, the newer deploys you rolled away from go too. Your _redirects rules last until your next publish.

A mount script that uses import stops a publish, because publishing does not bundle imports. You can still export the project and deploy the built output, as described below.

Export and deploy anywhere

Click the Publish icon in the header.
Click Download project to export a ZIP file.
Upload or import that project in the hosting provider.

Setup is short with most hosts. These guides walk through three of them.

Netlify Git-based deploy or manual deploy with prebuilt output. Open guide Vercel Import from Git or deploy from local source with Vercel CLI. Open guide Cloudflare Git integration or Direct Upload for prebuilt assets. Open guide

The export is a standard static website, so any other static host works too. To run it locally or control the build yourself, see Local Development.

Next steps

Custom Domains Point a custom domain at a published site. Redirects Move old URLs to new ones with a _redirects file. Local Development Go deeper into local runs and advanced build workflows.