Documentation

Deploy a site
Browse documentation

Upload and publish

Every way to put something online with Dplooy, which one fits what you have, and what happens between clicking Deploy and your site going live.

Ways to publish

One HTML fileDrop it on the dashboard, or Browse filesA single-page site
A folder of filesChoose folder, or drop the folderA multi-file site
A website as a ZIPDrop it and choose ZIP to siteA multi-file site
A PDF, an image or a ZIP to hand outDrop it (choose ZIP file for a ZIP)A link that opens or downloads it
A GitHub repositoryDeploy from GitHub — see GitHub deploysA site that can update on every push
A Claude artifactDeploy Claude artifactA single-page site
Nothing yetStart in Site Builder — see Site BuilderA site built from a template or by AI
A site you want ChatGPT, Claude or Gemini to writeAI Prompt in the Features menu — see belowA detailed prompt your AI builds the site from
Code, a script or an AI agentThe API or the MCP serverA site deployed without the dashboard

Before you upload

  • A website's homepage must be called index.html. In a folder or ZIP it sits at the top, or inside one folder at the top.
  • React, Vue, Vite, Next.js and other framework projects must be built first — upload the build output, not the source. See Website hosting.
  • Check the size: every file — on its own or inside a folder or ZIP — can be up to 5 MB on Free, 50 MB on Plus and 100 MB on Pro, and one ZIP or folder up to 50 MB on Free and 500 MB on Plus and Pro, within your storage. Full rules in Limits.
  • Every plan has a number of sites. When they are all in use, the drop zone says You've used every project slot — delete a site or upgrade to add another.

Publish from the dashboard

  1. 1On your dashboard, drag your site onto the drop zone — the box that says Drop anything. We figure out the rest. Or click Browse files for a single file, or Choose folder for a whole folder.
  2. 2Dplooy reads what you dropped. An HTML file goes live as a page and a folder as a whole website. For a ZIP it asks: ZIP to site puts the pages inside it online, ZIP file shares the ZIP itself as a download. A PDF or an image becomes a share link.
  3. 3Type a Project Name — it becomes your address, like my-site.dplooy.com — or press the shuffle button for a random one.
  4. 4Click Deploy. Your pages, stylesheets and scripts are scanned for phishing and malware before anything goes live.
  5. 5When you see Deployed!, click Visit Site.

Choose an address

The Project Name becomes the site's address: tidewater-cafe is tidewater-cafe.dplooy.com.

  • Use 3 to 50 characters: lower-case letters, numbers and hyphens. Anything else is turned into a hyphen.
  • Names that impersonate banks, payment services, well-known brands or sign-in pages are refused, along with a few reserved words such as www, api and admin.
  • If the name is taken, Dplooy adds a few digits to it — check the address on the success screen before you share it.
  • The address can't be changed after the site is published. To move to a new name, publish the site again under that name and delete the old one.

What happens before it goes live

  • Framework source code is recognised and refused before anything is uploaded, with the exact build commands to run instead.
  • Sizes and file counts are checked against your plan's limits.
  • For a folder or ZIP, Dplooy finds index.html and keeps every other file at the same path, so relative links keep working. Hidden files and clutter such as .git, .env, node_modules and .DS_Store are left out.
  • Pages, stylesheets and scripts are scanned for phishing and malware, and program files such as .exe are never published. If something is found, nothing goes live and you are told which file was flagged and why.

If an upload is refused, Troubleshooting lists each message and its fix.

Check the result

  • Click Visit Site on the Deployed! screen, then open the address in a private window and on a phone — that is what visitors see.
  • Click through every page and check the images load. File names are case-sensitive online: Logo.png and logo.png are different files.
  • On the Free plan a site goes offline 3 days after you deploy it — updating it doesn't restart the clock. Keep it online on the success screen moves you to Plus ($4.99 a month), where sites stay up until you delete them.

Claude artifacts

  1. 1In Claude, open the chat where the artifact was made, open the artifact and click Publish. Copy the public link.
  2. 2On your dashboard, choose Deploy Claude artifact, paste the link and pick a name.
  3. 3Dplooy fetches the page and puts it live on your own address. From then on it is an ordinary single-page site.
  • Only single-file HTML artifacts work. If Claude made a React component, ask it to turn the artifact into one self-contained HTML file and publish that.
  • The site is a snapshot of the artifact at import time. To update it, import the new link, or edit the live page with Visual Edit.
  • Visitors don't need a Claude account.

Have an AI build it

AI Prompt writes a detailed prompt for ChatGPT, Claude, Gemini or any AI that builds websites. Open the Features menu in your dashboard and choose AI Prompt, then work through five short steps — the basics (type, name and goal), the sections, the pages, a layout for each section, and the design, colours and fonts. Click Generate Prompt and copy the result into your AI. Start from a template, or a prompt you saved, to skip ahead.

If your AI is connected to Dplooy through the MCP server, the prompt has it build the site with working forms, content and bookings and publish it for you. Any other AI asks you once whether to connect, and otherwise writes the files for you to upload here.

Share a file

Drop a PDF, an image (JPG, PNG, GIF, SVG, WebP, BMP or ICO) or a ZIP (choosing ZIP file) and it gets its own link: PDFs and images open in the browser, ZIPs download. A shared file can be up to 5 MB on Free, 50 MB on Plus and 100 MB on Pro, and has analytics and a QR code on every plan and a password on Plus and Pro. File sharing is for handing files out — to put a website online, upload its HTML.

Publish a new version

Keep the address and update what is behind it: Replace files for uploaded sites, a push for GitHub sites, Update in the Site Builder, or an API deploy with the same project name. See Edit a live site.