# Droply: full text Every public Droply page, as Markdown, in one file. Generated from the same content sources as the site itself. Each document below is also available on its own at the page URL with a `.md` suffix, for example `https://droply.host/pricing.md`. Generated: 2026-09-16 # Product --- Source: https://droply.host # Droply Droply is a no-code static website and file hosting service. Upload finished HTML, a ZIP of a static site, a PDF, an image, or a document and turn it into a shareable HTTPS URL in seconds. No Git or server configuration is required. ## What it does not do - Droply hosts static content only. It does not run WordPress, PHP, Node.js, databases, server-side rendering, or any other server code from an upload. - React, Vue, Astro, Vite and other framework projects must be built first. Upload the finished static output, not the source project. - Published links are public by default. Password protection is available on eligible plans. - Customer sites on droply.id subdomains and connected custom domains hold user-generated content. They are not official Droply documentation. ## How it works 1. Upload a file, a folder, or a ZIP of a finished static site. 2. Pick a name. The site is live at that name on a droply.id subdomain, over HTTPS. 3. Re-upload to publish a new version at the same URL. Previous versions are kept per your plan. ## Plans and limits | Plan | Price | Sites | Storage | Visits / month | Bandwidth / month | Publishes / day | |---|---|---|---|---|---|---| | Free | Free | 1 | 25 MB | 5,000 | 5 GB | 15 | | Starter | $5/month | 2 | 50 MB | 10,000 | 10 GB | 50 | | Pro | $15/month | 5 | 500 MB | 100,000 | 50 GB | 300 | | Business | $35/month | 15 | 10 GB | 500,000 | 100 GB | 1,000 | | Enterprise | $89/month | 100 | 20 GB | 5,000,000 | 1,024 GB | Unlimited | Prices are in US dollars. Limits are counted per account, not per site. ## Frequently asked questions ### What can I host on Droply? An HTML file, a ZIP or folder of a static website, a built React, Vue or Astro app, a single React or JSX file from an AI tool, a PDF, an image, media, or a document. Droply is for files and sites that run in a browser without a server. ### Does Droply run WordPress, PHP, or Node? No server-side code ever runs. WordPress and Node apps need a server, so they cannot be hosted here. A PHP file that is really just HTML, including one split up with include, is converted to HTML when you upload it; anything that needs PHP to actually run is rejected with an explanation. ### Can I upload a React or Next.js project? Upload the built output and any framework works. If you have not built it, Droply can still run a single React or JSX file, and small projects that only use React, straight in the browser. Projects that pull in other npm packages need a build first. Server-rendered frameworks such as Next.js, Nuxt, Remix and TanStack Start have to be exported as a static site, or hosted somewhere that runs Node. ### Can I host something an AI tool built for me? Yes. Files from Claude, v0, Lovable and similar tools work, including a single .jsx or .tsx file with no build step, which Droply renders in the browser. If a project needs a build, you are told exactly which packages are missing instead of getting a blank page. ### Can I use my own custom domain? Yes, custom domains are included on Pro, Business, and Enterprise plans. Point your domain at cname.droply.id; Droply verifies the domain and serves it over HTTPS. ### Are Droply links public? Yes by default. A published link is meant to be shareable, and every site is served from a droply.id subdomain or a connected custom domain. Password protection is available on Pro, Business, and Enterprise plans. ### Can I update a site without changing the link? Yes. Re-uploading creates a new deployment at the same URL, so the link and any QR code you already shared keep pointing to the latest version. One-click rollback to a previous version is included on Pro plans and higher. ### Is there free static website hosting? Yes. The free plan hosts one site on a droply.id subdomain with no credit card. Free sites include the Droply banner; paid plans remove it. ### Can I cancel a paid plan anytime? Yes. You keep access until the end of your billing period, then your account falls back to the free plan. Your sites remain subject to the free plan limits after the downgrade. --- Source: https://droply.host/pricing # Droply pricing Plans, prices and the real per-plan limits. Every number below is the number an account is measured against, not a marketing figure. ## Plans and limits | Plan | Price | Sites | Storage | Visits / month | Bandwidth / month | Publishes / day | |---|---|---|---|---|---|---| | Free | Free | 1 | 25 MB | 5,000 | 5 GB | 15 | | Starter | $5/month | 2 | 50 MB | 10,000 | 10 GB | 50 | | Pro | $15/month | 5 | 500 MB | 100,000 | 50 GB | 300 | | Business | $35/month | 15 | 10 GB | 500,000 | 100 GB | 1,000 | | Enterprise | $89/month | 100 | 20 GB | 5,000,000 | 1,024 GB | Unlimited | Prices are in US dollars. Limits are counted per account, not per site. ## What each plan includes | Feature | Free | Starter | Pro | Business | Enterprise | |---|---|---|---|---|---| | Custom domains | No | No | Yes | Yes | Yes | | Indexed by search engines | No | Yes | Yes | Yes | Yes | | No "made with" badge | No | Yes | Yes | Yes | Yes | | Visitor analytics | No | No | Yes | Yes | Yes | | Password protection | No | Yes | Yes | Yes | Yes | | QR code for your link | Yes | Yes | Yes | Yes | Yes | | One-click rollback | No | No | Yes | Yes | Yes | | Auto-expiring links | No | Yes | Yes | Yes | Yes | | In-app file editor | Yes | Yes | Yes | Yes | Yes | | Email and lead capture | No | No | No | Yes | Yes | | API access | No | No | Yes | Yes | Yes | | Migrate an existing site by URL | Yes | Yes | Yes | Yes | Yes | | Link in bio page builder | Yes | Yes | Yes | Yes | Yes | ## Billing questions ### Is there a free plan? Yes, and it does not expire. The free plan publishes 1 live site on a droply.id subdomain with 25 MB of storage, and needs no credit card. Free sites carry a small “made with Droply” badge and are served with noindex, so they do not appear in search results. Both of those lift on any paid plan. ### Do I need a credit card to start? No. You can sign up, upload a file, and get a live HTTPS link without entering any payment details. A card is only asked for at the moment you choose a paid plan. ### Can I change or cancel my plan later? Yes, from the billing screen in your dashboard, at any time and without contacting support. An upgrade applies immediately. A cancellation keeps your plan running until the end of the period you have already paid for, and then drops the account to the free plan rather than deleting anything. ### What currency will I be charged in? Prices are listed in US dollars. Cards issued in Brazil are charged in Brazilian reais at the listed BRL price for the plan, because a Brazilian card cannot be charged in USD by our payment processor. The currency is decided by the card, not by the country you are browsing from, and it is shown on the checkout screen before you pay. ### Do you offer refunds? First-time subscribers can request a full refund within 14 days of their first paid charge by emailing contact@droply.host. After that window, and on renewals, fees are not refundable, and we do not pro-rate partial periods or downgrades. Non-waivable consumer rights are unaffected, including the 7-day right of withdrawal for consumers in Brazil. ### What happens if I go over my visit or bandwidth limit? Nothing is deleted and you are never billed for overage. Once an account passes its monthly limit, its sites serve a notice page instead of the content until the next monthly window opens or the plan is upgraded, at which point the original site is republished automatically at the same URL. Limits are counted across the whole account, not per site. ### How many times can I publish per day? Each plan carries a daily publishing allowance, listed in the comparison table above and counted over a rolling 24-hour window rather than reset at midnight. It exists to stop automated abuse, not to ration normal work. Editing and republishing a link-in-bio page from the builder does not count against it. ### Which plans include custom domains? Custom domains, with automatic SSL certificates, are included on Pro, Business and Enterprise. Every other plan publishes to a droply.id subdomain, which is free and served over HTTPS. ### Will my site show up in Google? Sites are indexable by search engines on Starter, Pro, Business and Enterprise. Free sites are deliberately served noindex, nofollow at the edge. That is an anti-spam control rather than an upsell: it is what keeps the shared droply.id domain worthless to link farms, and so keeps it reputable for everyone hosted on it. --- Source: https://droply.host/link-in-bio # Build a free link-in-bio page that actually looks like your brand Create a fast, mobile-first home for every link you share. Every Droply theme and design control is free, including image backgrounds, profile effects, featured links, UTM tags and campaign redirects. ## Frequently asked questions ### What is a link-in-bio page? A link-in-bio page is a mobile landing page that collects your important destinations behind one URL. Add that URL to a social profile so visitors can reach your content, store, services and other profiles without searching for them. ### Is the Droply link-in-bio builder really free? Yes. Free includes one published site with up to 60 content blocks, all 15 themes, every design control, custom image backgrounds, featured links, schedules, UTM parameters, campaign redirects, SEO fields and automatic SSL. The free page includes a Droply banner. ### How much can I customize my link-in-bio page? The selectable theme, typography, button, portrait, social-icon and motion controls create more than 13,063,680,000 preset combinations. Custom colors, gradients, patterns and uploaded images expand that even further. ### Is Droply a free Linktree alternative? Yes. Both products put many destinations behind one bio link. Droply includes its complete theme and design system, uploaded image backgrounds, hero portrait sizes, featured links, UTM parameters and a campaign redirect on Free. Some of those controls sit on paid Linktree tiers. ### Can I organize links into folders? Yes. Add collapsible folders in list or grid layouts, place links inside them and create one nested subfolder level. You can also use section labels and 5 divider styles to make a longer page easier to scan. ### Can I upload my own background image for free? Yes. Uploaded image backgrounds are available in the free builder. You can also use a solid color, two-color gradient, theme artwork or one of 5 CSS patterns, with controls that protect text readability. ### Can I use the same bio link on Instagram and TikTok? Yes. Publish once, then paste the same URL into Instagram, TikTok, YouTube, LinkedIn, X or any other profile that accepts a link. You can update the destinations later without changing the public URL. ### What will my link-in-bio URL be? Your page is published at a subdomain you choose, such as yourname.droply.id, with automatic SSL. Eligible paid plans can connect a custom domain. ### What do paid Droply plans add? The core builder and full design system stay free. Eligible paid plans add business features such as analytics, QR code downloads, lead-capture forms, custom domains and removing the Droply banner. ### Can I change my page after publishing? Anytime. Changes stay in a private draft until you publish again, and your public URL remains the same after every update. --- Source: https://droply.host/ai-website-builder # Build a website with AI, then publish it in one click Every other AI builder hands you a project and leaves hosting to you. Droply writes the page and puts it online at your own address, with HTTPS, in the same minute. The page is plain static HTML you own and can download. ## How it works 1. **Describe the page.** One box. Say who the page is for and what it should say, attach your logo and photos if you have them, and pick a palette, a feel or a language if you want to. If the kind of page needs a fact it does not have, such as an event date or a shop's WhatsApp number, it asks once. Answering those questions is free. 2. **Look at the real page.** The page is written and shown to you in a sandboxed preview. Nothing is online yet. Ask for changes in the same conversation, swap any picture, or start again. 3. **Publish it.** One click puts it at your own address on droply.id with automatic HTTPS, or on a custom domain. It is a normal Droply site from then on: version history, one-click rollback, and the same scans every upload gets. ## What it does - **Change a photo without spending a credit.** Every picture on the page, and every placeholder it drew, is a slot you can click in the preview. Upload an image, it lands instantly. That edit is made directly, not by asking the model again, so it costs nothing from your allowance and cannot redesign the rest of the page. - **Edit a site you already published.** Open a live single-page site and say what to change. The builder changes only what you asked for rather than rewriting the page around it. Nothing goes live until you publish, and the previous version stays in the site history for one-click rollback. - **Your pictures, never invented ones.** The model does not make photographs and cannot fetch them from the web. It places the images you upload, by name, and draws a simple placeholder where you have none. Upload a logo and the palette is read from it automatically, so the page looks like your brand rather than a template. - **A real website you own.** The output is plain static HTML with your images beside it. Download it, host it elsewhere, hand it to a developer. There is no proprietary format, no builder lock-in, and no export step to buy. ## Included AI credits | Plan | Price | AI credits | | |---|---|---|---| | Starter | $5/mo | 10 | per month | | Pro | $15/mo | 100 | per month | | Business | $35/mo | 300 | per month | | Enterprise | $89/mo | 800 | per month | One credit is one page or one edit. Answering the setup questions and swapping pictures cost nothing. ## Limits - One page at a time. The builder makes and edits single-page sites, not multi-page ones. - Static output only. No server code, no database, no server-side forms. Contact buttons are WhatsApp, email, an external form, or any link you give it. - The model never generates photographs. It places pictures you upload and draws simple placeholders where you have none. - Nothing is published until you press publish. Until then the page exists only in a sandboxed preview. - One credit is one page or one edit, whatever its length. Answering the setup questions and swapping pictures cost nothing. ## Frequently asked questions ### What does the AI builder cost? It is included on the paid plans, from $5 a month for 10 AI credits. One credit is one page or one edit, and answering the setup questions and swapping pictures cost nothing. ### Does Droply host the website too, or do I have to publish it somewhere else? It hosts it. That is the difference between this and most AI builders: the page is written and put online in the same product, at a live HTTPS address, in about a minute. There is no export, no build step and no second service. ### Can I edit a website I already published? Yes, for single-page sites. Open the site, say what to change, and only what you asked for changes. Nothing goes live until you publish, and the previous version stays in the site history so you can roll back in one click. ### Does it cost anything to swap a photo? No. Pictures are slots you click in the preview, and filling one is a direct edit rather than another request to the model. It is instant and spends nothing from your allowance. ### Does the AI invent images, phone numbers or addresses? No, and that is deliberate. It uses the pictures you upload and the contact details you give it, and nothing else. Where a picture belongs and you have not given one, it draws a simple placeholder you can fill in one click. ### Do you train AI models on my prompts or my page? No. Requests are sent with data collection switched off at the provider, so your prompt and your page are not used for training. ### Can it build a site with several pages? Not today. The builder makes and edits one page at a time, and only single-page sites can be edited by chat. A multi-page site can still be uploaded to Droply as a folder or ZIP in the normal way. --- Source: https://droply.host/mcp-server # Ask Claude to publish your website Droply runs a remote MCP server, so your AI assistant can publish for you. Connect it once, ask for a page or hand it a finished project, and get a live HTTPS link back. The site lands in your own account, and asking again updates it at the same address. ## How it works 1. **Connect your assistant once.** In Claude, add Droply as a custom connector and approve access on the Droply screen. Claude Code connects with one command, and other assistants use an AI assistant token. 2. **Ask for what you want.** Describe a page, or point Claude Code at a project you have already built. The assistant picks a free address, sends the files and follows the publish until it is live. 3. **Share the link, change it any time.** You get a live HTTPS link on your account. Ask for a change later and the assistant publishes over the same site, so the link you shared keeps working. ## Connect it Server address: `https://droply.host/mcp` - **Claude.ai and Claude Desktop.** In Settings, open Connectors, add a custom connector with this address, and approve access on the Droply screen. Claude's Free plan can add one custom connector. - **Claude Code.** Run this command in your terminal, then run /mcp inside Claude Code and sign in. `claude mcp add --transport http droply https://droply.host/mcp` - **Cursor, VS Code, Windsurf and other clients.** Create an AI assistant token on your Droply API tokens page and add this address to the client with the header Authorization: Bearer followed by the token. Keep the token in your user settings or an environment variable, never in a project file that could be committed: anyone holding it can replace what your sites show until it expires after 90 days or you revoke it. ## What your assistant can do - **Publish a page or a whole site.** One self-contained HTML page, or a folder of HTML, CSS, JavaScript, images and fonts, published as a new site or over one you already have. - **Pick an address that is free.** It checks a subdomain before creating the site, so a new site does not fail on a name somebody else already has. - **Follow the publish until it is live.** Publishing takes a few seconds. The assistant checks until the site is live and gives you the link, or tells you what to fix if a file was refused. - **Only the access you approve.** The connection sees which plan the account is on, and lists and publishes your sites. It cannot delete a site, change a domain or see billing, and you can sign it out from your dashboard at any time. - **The same checks as every upload.** Files from an assistant go through the same malware scan as a dashboard upload, and Autopilot checks every version that goes live for leaked keys. - **Your account, your sites.** Everything lands next to the sites you uploaded yourself, with analytics, custom domains and password protection on the plans that include them. ## What it does not do - It does not build projects. Send the finished files: a project that needs npm install or a build step has to be built first. - One publish carries up to 300 files and 8 MB in total, or one page of up to 5 MB. Upload bigger projects as a ZIP from the dashboard. - It cannot delete sites, manage custom domains or change billing. - An account can publish from an assistant up to 30 times an hour, on top of its plan's own limits. - On the Free plan, sites carry a small Droply banner and are not indexed by search engines, the same as any upload. ## Frequently asked questions ### What is an MCP server? MCP, the Model Context Protocol, is an open standard that lets an AI assistant use tools from other services. Droply runs an MCP server with a small set of publishing tools, so your assistant can put a website online in your account instead of handing you files to upload. ### Is it free? Yes. Connecting an assistant works on every Droply plan, including Free. Your plan's usual limits apply, such as how many sites you can have and how much you can store, and an account can publish from an assistant up to 30 times an hour. ### Which AI assistants work with it? Claude.ai, Claude Desktop and Claude Code sign in directly. Cursor, VS Code, Windsurf and other assistants that can send a request header connect with an AI assistant token from your dashboard. ### Does it work with ChatGPT? Not through this server yet. ChatGPT has a separate Droply GPT, which publishes single HTML pages through the API and needs a plan with API access. ### What can the assistant do in my account? See which plan the account is on, list your sites, check whether a name is free, publish a page or a folder of files, and follow a publish until it is live. It cannot delete sites, change domains or see billing, and it never receives your name or your full email address. You approve the connection on a Droply screen that shows the account it gets and where access is sent, and you can sign it out at any time. ### Can it update a site I already have? Yes. Ask for a change and the assistant publishes over the same site, so the address stays the same. ### Can the site use my own domain? Yes, on plans that include custom domains. Connect the domain to the site once in your dashboard, and every publish from the assistant appears on it. ### My project uses React, Vue or Next.js. Will it work? Yes, once it is built. The assistant publishes the build output, usually a dist or out folder, because nothing is installed or built on Droply. Claude Code can run your build first and then publish the result. ### Do visitors need a Claude account? No. The result is an ordinary public website on a normal link. Only you need an assistant, to publish it. # Publishing workflows --- Source: https://droply.host/static-website-hosting # Static website hosting without the setup Static website hosting for a site you have already built: upload it as a ZIP or a folder and get a secure public URL in seconds. There is no Git remote to add, no server to configure and no build to wait for, because the files you upload are the files we serve. ## What is static website hosting? Static website hosting means a server sends your files to a browser exactly as you wrote them, with no code running in between. The HTML, CSS, JavaScript, images and fonts are the whole product; there is no application on the server assembling a page per visitor. That is why it is fast and why it is cheap: every visitor gets the same bytes, so they can be cached aggressively and served from disk. It is also why the setup is short. A dynamic host has to know your language, your dependencies, your environment variables and your database. A static host only has to know which folder to serve, so the entire configuration is the folder you hand it. The catch is what the word "static" excludes. Anything your site does at request time on the server, a login, a form that writes to a database, a page rendered per user, is not part of the deal. Modern front-end frameworks are still welcome here, because they build down to static files: you run the build on your own machine and upload what it produces. The framework deploy guides list the exact command and output folder for each one. ## How it works 1. **Upload your finished files.** Drop a ZIP of your built site, a whole folder, or a single HTML file. Your CSS, JavaScript, images and fonts stay together and keep their relative paths. 2. **Pick a name and publish.** Choose the subdomain and press publish. The site is live on its own HTTPS address in seconds, with the certificate issued and renewed for you. 3. **Update the same address.** Upload a new build when the work changes. The URL does not move, so links you already sent, bookmarks and printed QR codes all keep working. ## What you get ### Upload the shape you already have Most static hosts accept exactly one shape and reject everything else, which turns a two-minute job into a repackaging exercise. Droply takes the artefact you are actually holding. - A single .html file, dropped on its own, with nothing to zip first. - A ZIP of a built site, extracted with its folder structure preserved. - A whole folder, dragged straight from the desktop. - A single .jsx or .tsx file, which runs in the visitor browser with no build step. - 96 file extensions in total, across 7 groups, including PDFs, images, media and documents. ### One address, every version Each upload becomes a new immutable version, and publishing swaps which version the address points at. Nothing is edited in place, so a publish either fully happens or does not happen at all. - The URL never changes, so anything you already shared keeps resolving. - A visitor mid-page-load never sees half the old build and half the new one. - Rollback to an earlier version is one click, from Pro upward. - The free plan keeps the current version only, which is enough to publish but not to roll back. ### A security check on every publish, on every plan The most common way a static site leaks something is a whole project folder getting zipped instead of the build output. We read what you actually published and say what a stranger can now read. - A committed .env file, a .git directory, a private key, an API key left in a JavaScript bundle. - It runs after the site goes live and reports in plain language, not as a severity score. - Included on the free plan. See how the security check works. ### Your own domain, with the certificate handled A subdomain is fine for a preview and wrong for a launch. From Pro you point a domain you own at the site and it is served from your address. - HTTPS certificates are issued and renewed automatically, on the Droply address and on yours. - Step-by-step DNS guides for the common registrars, with the exact records. - Free sites are served noindex, so search engines will not list them. Indexing starts on Starter. ## What the free plan includes Everything below is on the free plan, with no card and no trial period to run out. - 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. ## Compared with Tiiny Host Tiiny Host is the incumbent in this category and does the same core job well. These are the rows that actually differ for someone with a finished static site. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. Tiiny Host: 1 site, 5,000 visits and 5 GB bandwidth a month, 3 MB per project (0.5 MB for a PDF). - **Single HTML file, no ZIP.** Droply: Yes, drop the .html on its own. Tiiny Host: Yes, HTML is accepted. - **Single .jsx or .tsx, no build.** Droply: Yes. It is transformed in the visitor browser at the published URL. Tiiny Host: Not offered. - **Security check on deploy.** Droply: Every publish, on every plan, including free. Tiiny Host: Not offered. - **Custom domain.** Droply: From Pro, $15 a month. Tiiny Host: From Solo, $18 a month or $13 billed annually, up to 5 domains per account. - **Entry paid price.** Droply: $5 a month for Starter. Tiiny Host: $9 a month for Tiny, or $5 billed annually. - **Free trial behaviour.** Droply: No trial to cancel. The free plan is the free plan. Tiiny Host: Every paid plan carries a 7-day money-back guarantee. Tiiny Host figures come from its own help center, checked 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (updated 2 September 2026), the free-plan link duration article (updated 21 August 2026), the password-protection article (updated 3 September 2026) and the custom-domains guide (updated 7 September 2026). Product plans can change. ## When Droply is the wrong choice Static hosting is a narrow tool and it is the wrong one more often than most hosts admit. If any of the following is true of your project, something else will serve you better and you will find that out faster here than after an afternoon of uploads. - Your site needs a contact form that stores submissions itself, a members area, or a shopping cart with server-side checkout. - You are shipping a Next.js or Nuxt app that uses server rendering or API routes. A fully static export works; the server half does not. - 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. ## Frequently asked questions ### What is static website hosting? It is hosting that serves finished files, HTML, CSS, JavaScript, images and fonts, exactly as you uploaded them. No application code runs on the server, which is why it is fast to serve and short to set up. ### Is static website hosting free here? Yes. The free plan gives you 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included and no card. It is a plan in its own right, not a trial of a paid one. ### Can I host a static site without Git? Yes. You upload the finished files from your browser. There is no repository to connect, no deploy key, no pipeline and no build command to configure anywhere. ### Should I upload my source code or the built output? The built output. If your project uses a framework or a bundler, run its build on your machine first and upload the folder it generates. The deploy guides give the exact command and output folder for 23 frameworks. ### What happens to the URL when I upload a new version? Nothing. Each upload becomes a new version and publishing points the same address at it, so every link you already sent keeps working. On Pro and above you can also roll back to an earlier version. ### Can I use my own domain name? Yes, from Pro at $15 a month. You point a domain you own at the site and it is served from your address with HTTPS handled for you. The DNS guides cover the common registrars. ### Will my static site show up in Google? Only on a paid plan. Free sites are served with a noindex header on purpose, because free subdomains on a shared domain are the raw material for spam farms. Search visibility starts on Starter. ### Does Droply run PHP, Node or a database? No. Static PHP pages are converted to HTML at publish time, but the language does not execute, and there is no Node runtime and no database. Anything that needs those belongs on a platform built for them. ### How big can a static site be? Each plan sets an upload size and a total storage allowance. The free plan is 25 MB per upload and 25 MB overall, which covers a normal marketing site or portfolio; the pricing page lists every tier. ### Can I password-protect a static site? Yes, from Starter. The password is checked at the edge before any file is served, so the pages and their assets are both covered rather than just the front door. ## Related - [HTML Hosting](https://droply.host/html-hosting) - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip) - [Static Hosting for Freelancers](https://droply.host/static-hosting-for-freelancers) --- Source: https://droply.host/html-hosting # HTML hosting: host an HTML file without a server HTML hosting is one drag: drop a finished .html file and it is live at its own HTTPS address in seconds. If the page pulls in a stylesheet, a script or images, zip the folder instead and every relative path keeps working. ## What is HTML hosting? HTML hosting is putting an .html file somewhere a browser can reach it over the public internet, so that opening a URL shows the page instead of downloading the file. That is the whole job: a public address, a server that returns the file with the right content type, and a certificate so the address works over HTTPS. It sounds trivial, and the file itself is trivial, which is exactly why it is annoying. A local .html file opens fine by double-clicking it, but you cannot send that to anyone: an email attachment gets stripped or flagged, a chat app renders it as a download, and a colleague on a different operating system may open it in something that is not a browser at all. Hosting the file removes every one of those failure modes at once. The part that trips people up is assets. A single page with everything inline needs nothing else. A page with or needs those files present at those exact relative paths, which means you upload the folder rather than the page. If you are not sure whether your page is self-contained, the HTML tester renders pasted markup so you can see what is missing. ## How it works 1. **Drop the .html file.** One finished page goes up on its own. There is no archive to build, no folder to prepare and no template to fill in first. 2. **Open it in a browser.** The page gets its own HTTPS address, so a reviewer opens a link instead of downloading an attachment and trusting their machine to render it. 3. **Keep it, or move it to your domain.** The Droply address is yours on the free plan and does not change when you republish. From Pro the same page can be served from a domain you own. ## What you get ### One file really is enough Several hosts in this category accept a folder or an archive and refuse a loose .html file, which means your first step is packaging something that did not need packaging. Here the file is the upload. - Drop the .html or .htm and press publish. Nothing else is required. - The page is served at the root of the site, so the address is the page. - A page that is a single file with inline CSS and JavaScript needs no further thought. ### When the page has assets, upload the folder A stylesheet, a script bundle, web fonts and images all resolve against the page URL. Preserve the folder layout and every reference resolves exactly as it does on your machine. - Upload the folder directly, or zip it and upload the archive. - The entry page must be named index.html and sit at the top of what you upload. - Relative paths are preserved on extraction; absolute paths that start with a drive letter or file:// will not resolve. - If the ZIP wraps everything in one extra folder, that folder is unwrapped rather than becoming part of the URL. Hosting a static site from a ZIP covers the shapes that fail. ### It tells you what you exposed Uploading a folder is the moment a stray file becomes public. Every publish is read after it goes live and reported back in plain language. - Warns about an .env file, a .git directory, a private key or an API key sitting in a script. - Runs on every plan, free included, and never blocks the publish. - The detail is on the security check page. ### Edit and republish without a new link HTML files change constantly while a page is being reviewed. Re-uploading replaces what the address serves and leaves the address alone. - Every version is stored separately, and publishing points the address at the new one. - From Pro, an earlier version is one click away if the new one is wrong. - Up to 15 publishes a day on the free plan, which is more than a review round needs. ## What the free plan includes Hosting one HTML page costs nothing. This is the whole free plan, not a trial of it. - 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. ## Compared with Tiiny Host Both products accept HTML and both are aimed at people without a deploy pipeline. These are the differences that show up once the file is up. - **Single .html accepted.** Droply: Yes, on its own. Tiiny Host: Yes. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. Tiiny Host: 1 site, 5,000 visits and 5 GB bandwidth a month, 3 MB per project (0.5 MB for a PDF). - **Security check on deploy.** Droply: Every publish, on every plan, including free. Tiiny Host: Not offered. - **React file without a build.** Droply: A single .jsx or .tsx runs at the URL. Tiiny Host: Not offered. - **Password protection.** Droply: From Starter, checked at the edge before any file is served. Tiiny Host: From Solo, $18 a month or $13 billed annually. - **Custom domain.** Droply: From Pro, $15 a month. Tiiny Host: From Solo, $18 a month or $13 billed annually, up to 5 domains per account. - **Entry paid price.** Droply: $5 a month for Starter. Tiiny Host: $9 a month for Tiny, or $5 billed annually. Tiiny Host figures come from its own help center, checked 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (updated 2 September 2026), the free-plan link duration article (updated 21 August 2026), the password-protection article (updated 3 September 2026) and the custom-domains guide (updated 7 September 2026). Product plans can change. ## When Droply is the wrong choice An HTML file is the simplest thing on the web and it still cannot do some of what people expect from it. If your page needs any of the following, hosting the file will not give it to you. - The page has a form and you expect the submissions to land somewhere. A static page can post to a service you already run, but nothing here stores them for you. - The HTML is generated per visitor, by a template engine or a CMS. Upload the rendered output, not the template. - 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. ## Frequently asked questions ### Can I host a single HTML file? Yes. Drop the .html or .htm file on its own and publish. It is served at its own HTTPS address in seconds, with no archive to prepare first. ### What if my HTML file uses CSS, images or JavaScript? Upload the whole folder, or zip it and upload the archive, keeping the same layout you have locally. Relative paths are preserved, so every reference in the page resolves the way it does on your machine. ### Is hosting an HTML file free? Yes. The free plan publishes 1 site with HTTPS at no cost, up to 25 MB per upload and 25 MB of storage. Paid plans add custom domains, password protection and removal of the small badge. ### Do I need a server or any configuration? No. There is no server to provision, no web server config to write and no build to run. You need an account, which exists so that every published file has an owner who can be contacted about it. ### What should the main page be called? Name it index.html and put it at the top level of what you upload. A folder or ZIP with no index.html at the root has no entry page, and the published site will say so instead of guessing. ### Can I edit the HTML after publishing? Edit locally and upload the replacement; it is published at the same address. From Pro you can also roll back to a previous version if the new file turns out wrong. ### Can my HTML page call an API? It can call any service that already exists and allows browser requests, subject to that service's CORS rules. Droply provides no server-side runtime, so the API has to live somewhere else. ### Will search engines index my hosted HTML page? Not on the free plan, which is served noindex by design to keep free subdomains worthless to spam farms. Indexing is enabled from Starter. ### Can I upload an HTML file exported from Word, Figma or a page builder? Yes, as long as you upload the export intact. These exports usually produce an .html file plus a folder of assets next to it, so upload both together rather than the .html alone. ## Related - [HTML to URL](https://droply.host/html-to-url) - [Static Website Hosting](https://droply.host/static-website-hosting) - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip) --- Source: https://droply.host/html-to-url # Turn HTML code into a public URL HTML to URL, for people holding code rather than a website: pasted out of an editor, a chat with an AI, or a snippet somebody sent you. Save it as index.html, drop it here and it is a real page at a real HTTPS address in seconds. ## How do you turn HTML into a URL? You save the HTML as a file and put that file on a web server, which gives it an address. There is no way to skip the file: a URL points at something stored somewhere, so the markup has to become a stored thing before it can have a link. What varies between tools is only how much ceremony sits between those two facts. Here the ceremony is one drag. Save your markup as index.html, drop it on the uploader, choose a subdomain, and the page is live. The name matters: index.html is what a web server returns when a visitor asks for the site root, so calling it that means your address opens your page rather than a file listing. The place this goes wrong is markup that is not self-contained. Code pasted out of a project often references ./styles.css or /assets/app.js, files that exist on the machine it came from and nowhere else. Uploading only the .html then produces a page with no styling, which reads like a hosting failure and is not one. Upload the whole folder and the references resolve. If the snippet came from an AI chat, see hosting an AI-generated website for what those tools actually hand you. ## How it works 1. **Save the code as index.html.** Paste your markup into any text editor and save it with an .html extension. The name index.html makes it the page the address opens. 2. **Drop the file.** Upload that one file. If the markup references a separate stylesheet, script or image, upload the folder containing all of them instead. 3. **Copy the URL.** Pick a name, publish, and you have an HTTPS address to paste anywhere. Re-upload later and the address stays the same. ## What you get ### From clipboard to link in about a minute The path is deliberately short because the thing being published is small. There is no project to create, no repository to initialise and no build to configure. - Any text editor works for the save step, including the one already open. - The subdomain is yours to pick, so the link can read like the thing it contains. - HTTPS is on from the first publish, with the certificate handled for you. ### Built for the second, third and fourth version Code you just pasted is code you are about to change. Republishing keeps the address, which is the difference between iterating and re-sending links. - Up to 15 publishes a day on the free plan. - The address is fixed from the first publish, so a link in a message stays correct. - From Pro, an earlier version can be restored in one click. ### React markup works too, with no build If what you are holding is a component rather than a page, a single .jsx or .tsx file runs at the published URL. The transform happens in the visitor browser, not on our servers. - React and the JSX runtime are provided and served from our own edge. - Other packages are not fetched from a public CDN on your visitors' behalf; the page names what is missing instead of rendering blank. - A multi-file project needs its build first. The three-step export guide covers that. ### Pasted code gets read before you find out the hard way Markup copied out of a working project is the single most likely place to find a key that should not be public. Every publish is checked and reported. - API keys in inline scripts, tokens in data attributes, a .env or .git that came along in a folder upload. - On every plan including free, and it never blocks the publish. - More detail on the security check page. ## What the free plan includes Publishing code you just pasted costs nothing, and the free plan is a plan rather than a trial of a paid one. - 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. ## Compared with Tiiny Host Both take an HTML file. The differences show up in what happens to the code around it and how quickly you can publish the second version. - **Single .html accepted.** Droply: Yes. Tiiny Host: Yes. - **Single .jsx or .tsx, no build.** Droply: Yes, transformed in the visitor browser. Tiiny Host: Not offered. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. Tiiny Host: 1 site, 5,000 visits and 5 GB bandwidth a month, 3 MB per project (0.5 MB for a PDF). - **Republish to the same address.** Droply: Yes, up to 15 times a day on free. Tiiny Host: Yes. Updating a project keeps its link and its QR code. - **Security check on deploy.** Droply: Every publish, on every plan, including free. Tiiny Host: Not offered. - **Rollback to an earlier version.** Droply: From Pro, in one click. Tiiny Host: No self-serve rollback is documented. The help center says a deleted link can be restored by contacting support. - **Custom domain.** Droply: From Pro, $15 a month. Tiiny Host: From Solo, $18 a month or $13 billed annually, up to 5 domains per account. - **Entry paid price.** Droply: $5 a month for Starter. Tiiny Host: $9 a month for Tiny, or $5 billed annually. Tiiny Host figures come from its own help center, checked 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (updated 2 September 2026), the free-plan link duration article (updated 21 August 2026), the password-protection article (updated 3 September 2026) and the custom-domains guide (updated 7 September 2026). Product plans can change. ## When Droply is the wrong choice Turning HTML into a URL is a publishing step, not a development environment. These are the cases where you want something else. - You want to edit the code in the browser and see it update live as you type. This publishes a file; it is not an online editor or a playground. - The markup is a fragment, a partial or a component with no surrounding page. Wrap it in a complete HTML document first, or it will render as bare text. - 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. ## Frequently asked questions ### How do I turn HTML code into a URL? Save the code as a file named index.html, upload it here, pick a subdomain and publish. You get an HTTPS address in seconds that opens the rendered page. ### Can I paste code instead of uploading a file? The upload takes a file, so save the markup first; any text editor does it in a few seconds. If you want to see how the markup renders before committing to it, the HTML tester takes pasted code directly. ### Why does my page look unstyled after uploading? Almost always because the markup references a stylesheet that was not uploaded with it. Upload the folder containing the .html and its assets, keeping the same structure, and the relative paths resolve. ### What should I name the file? index.html, at the top level of whatever you upload. That is the file a web server returns for the site root, so naming it anything else means the address does not open your page. ### Does the URL change when I update the page? No. It stays yours while the site is published and within your plan limits. Re-uploading updates the same site rather than minting a new address, so a link you have already shared keeps working. ### Can I turn code from ChatGPT or Claude into a URL? Yes, and it is one of the most common reasons people land here. Save the HTML block as index.html and upload it. A single React file works too, without a build. There is a page per tool: ChatGPT, Gemini and Claude artifacts. ### Is it free to turn HTML into a URL? Yes. The free plan hosts 1 site with HTTPS, 25 MB of storage and 5,000 visits a month, with no card and nothing to claim. ### Can I share the URL with a client privately? Published links are public by default. From Starter you can put a password on the site, checked at the edge before any file is served, so the assets are covered as well as the page. ### Does the page keep working if I change the code later? Yes. Upload the new file and it replaces what the address serves. The previous version is kept, and from Pro you can restore it in one click. ## Related - [HTML Hosting](https://droply.host/html-hosting) - [Client Website Preview](https://droply.host/client-website-preview) - [Host an AI-Generated Website](https://droply.host/host-ai-generated-website) --- Source: https://droply.host/host-static-site-from-zip # Host a static site from a ZIP file To host a static site from a ZIP, zip the built output of your site and drop the archive here and it is extracted and live at an HTTPS address in seconds. Most ZIP uploads that fail do so for one of three reasons, and all three are listed further down this page. ## What should be inside the ZIP? The finished output of your site and nothing else: an index.html at the top level, plus every CSS, JavaScript, image and font file it references, in the folders it expects them in. If you unzip your archive and immediately see index.html, it is shaped correctly. The distinction that causes the most trouble is source versus output. A project folder contains src, package.json, a config file and often node_modules. None of that is a website; it is the recipe. The website is what appears in dist, build, out, _site or public after you run the build command. Zip the contents of that folder. The deploy guides name the command and the output folder for 23 frameworks so you do not have to guess which one your tool uses. The second distinction is what you selected before compressing. Right-clicking a folder and choosing "compress" produces an archive with that folder inside it, so the site ends up one level deep. Droply unwraps a single wrapping folder automatically, but an archive with several folders and no index.html at any obvious root cannot be guessed at, and the published site will tell you that rather than serving a file listing. ## How it works 1. **Zip the built output.** Select the CONTENTS of your build folder, index.html and everything beside it, and compress those. Do not zip the project folder that contains src and node_modules. 2. **Drop the archive.** The ZIP is extracted with its folder structure intact, so every relative path to a stylesheet, script, image or font resolves as it did locally. 3. **Share the address.** The extracted site is live over HTTPS. Upload a new archive whenever the build changes and the address stays exactly where it was. ## What you get ### The three things that go wrong, and what to do Almost every failed ZIP upload in this category is one of these. None of them is a hosting problem, which is why a host that only says "upload failed" is not much help. - No index.html at the root. The archive has files but no entry page, so there is nothing for the address to open. Rename your main page to index.html. - The source project instead of the build. If node_modules or src is in there, you zipped the recipe. Run the build and zip its output folder. - An extra wrapping folder. Compressing a folder puts it inside the archive; select its contents instead. A single wrapper is unwrapped for you, but two levels are not. ### Structure is preserved exactly Extraction keeps your folder layout, so the site behaves the same way it does when you open it locally. Nothing is rewritten, minified or reorganised. - Relative paths such as ./assets/app.css and ../images/logo.svg resolve as written. - Nested routes work: /about/index.html is served at /about. - Absolute paths that begin with a drive letter or file:// point at your machine and will not resolve for a visitor. ### The archive is checked, not just extracted A ZIP is the easiest way to publish something you did not mean to, because you never look at all of it. Extraction is sandboxed and the result is read before you find out from someone else. - Warns about a .env, a .git directory, a private key or an API key in a bundled script. - Executables and installers are refused rather than served. - Runs on every plan including free. See how the check works. ### Rebuild, re-zip, republish The address is tied to the site, not to the archive, so the second upload lands where the first one did. - Up to 15 publishes a day on the free plan. - Each archive becomes its own version; from Pro you can return to any of them. - The switch is atomic, so a visitor never sees a half-extracted site. ## What the free plan includes A ZIP upload costs nothing on the free plan, and the plan does not expire or need a card. - 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. - ZIP extraction is sandboxed, and executables and installers are refused rather than served. ## Compared with Netlify Drop Netlify Drop is the closest thing to this workflow at a large host, and it is a genuinely good on-ramp to Netlify. The rows below are where the two differ for someone who just wants the ZIP online. - **Anonymous drop.** Droply: Not offered. Publishing requires an account, so every hosted file has an owner. Netlify Drop: Yes, and the URL is protected with a temporary password until you claim it. - **Is the link yours straight away?.** Droply: Yes. Publishing needs an account, so there is nothing to claim afterwards. Netlify Drop: No. An anonymous drop creates a temporary project you have one hour to claim. - **Single HTML file.** Droply: Accepted on its own. Netlify Drop: The quickstart documents a project folder, a zip or a pre-built output folder; a loose HTML file is not listed. - **Size guidance.** Droply: 25 MB per upload on free; substantially higher on paid tiers. Netlify Drop: 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. - **Builds your project for you.** Droply: No. You build locally and upload the output. Netlify Drop: Yes, it can build a dropped project. - **Redeploy to the same address.** Droply: Yes, up to 15 times a day on free. Netlify Drop: Yes. Dragging an updated folder publishes it as the latest production version of the same project. - **PDF and document hosting.** Droply: First class, with in-browser viewers and 96 accepted file types. Netlify Drop: Not a product feature. - **Security check on deploy.** Droply: Every publish, every plan. Netlify Drop: Not part of Drop. 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 ZIP upload is a publishing step, not a build system. If you want the host to do more than extract and serve, you want a different host. - You want the platform to run npm install and npm run build for you. That does not happen here: bring the built output. - Your archive is a source project you cannot build locally. Nothing here will turn it into a site, and the deploy guides are the fastest way to get it built. - 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. ## Frequently asked questions ### What should be inside the ZIP? The built output: an index.html at the top level plus every CSS, JavaScript, image and font file it references, in their original folders. If unzipping the archive shows index.html straight away, it is correct. ### Can I upload a React, Vite or Astro project as a ZIP? Upload the build output, not the project. Run the build on your machine and zip the contents of the folder it produces, which is usually dist, build or out. The deploy guides name it per framework. ### Why does my ZIP upload say there is no entry page? Because there is no index.html at the root of what was extracted. Rename your main page to index.html, or re-zip so that it sits at the top level rather than inside another folder. ### Do I zip the folder or its contents? The contents. Compressing a folder puts that folder inside the archive and pushes your site one level down. A single wrapping folder is unwrapped automatically, but it is cleaner to select the files themselves. ### Are relative asset paths preserved? Yes. The archive is extracted with its structure intact, so ./assets/app.css and ../images/logo.svg resolve exactly as they do locally. Absolute paths pointing at your own machine will not. ### How large can the ZIP be? The free plan accepts up to 25 MB per upload with 25 MB of storage overall; paid tiers raise both substantially. The pricing page lists every limit. ### Is the ZIP extracted safely? Extraction is sandboxed, executables and installers are refused, and the extracted result is scanned. If something in the archive should not be public, such as an .env file or a private key, you are told after the site goes live. ### Can I replace the ZIP later? Yes. Upload a new archive and it becomes the live version at the same address. Each upload is kept as its own version, and from Pro you can switch back to any earlier one. ### What if my ZIP contains several sites? It will be published as one site with those folders as subpaths, which is rarely what people want. Zip and publish each site separately so each gets its own address and its own version history. ## Related - [Static Website Hosting](https://droply.host/static-website-hosting) - [HTML Hosting](https://droply.host/html-hosting) - [Client Website Preview](https://droply.host/client-website-preview) --- Source: https://droply.host/static-hosting-for-freelancers # Static hosting for freelancers who deliver client work Static hosting for freelancers who need a finished client site, a proposal or a prototype behind a clean link without turning delivery into a deployment project. Upload the built files, send one address, and replace the build in place as the work moves. ## What freelancers actually need to hand over Not a hosting account. The deliverable is usually a built static site, a PDF proposal or scope document, a set of design exports, or a prototype that has to be seen in a browser rather than described. What a freelancer needs is for each of those to become a link that a non-technical client can open on a phone, and that stays correct after the next revision. The two common alternatives both leak time. Sending a ZIP moves the work of opening it onto the client, who then opens index.html from their downloads folder, sees a page with no styling because the browser blocked something, and replies that the site is broken. Standing up a real host for a project that has not been paid for yet means a server, a certificate and a DNS record you will have to remember to tear down. A publishing step sits between those. Upload, share, replace. When the project is signed off and the client wants it on their own domain, the same site moves there from Pro, and the DNS guides are short enough to paste into an email. If the review needs to stay private, password protection from Starter is checked at the edge, before any file is served. ## How it works 1. **Upload the deliverable.** Drop the built site, the HTML page, the PDF proposal or the design export. It is served exactly as you prepared it, with nothing reformatted. 2. **Send one address.** The client opens a link, not an archive. No download, no unzipping and no instructions about opening a local file in a browser. 3. **Revise without resending.** Publish the new build to the same site. The address in the email thread, the invoice and the printed QR code keeps pointing at the current work. ## What you get ### One address that survives the project The link goes in a proposal, a contract, a chat thread and eventually an invoice. It has to still be right in three weeks, after four revisions. - Publishing a new build swaps what the address serves; the address itself never moves. - From Pro, returning to the version the client approved is one click. - Pick the subdomain, so the link reads like the project rather than like a hash. ### Private while it is unfinished Work in progress should not be indexable, quotable or findable. Two separate controls cover that. - Password protection from Starter, enforced at the edge before any file is served, so assets are covered as well as pages. - Free sites are served noindex, so nothing half-finished turns up in a search result. - Expiring links from Starter: set a preview to lapse after six hours, a day, a week, a month or a date you pick. ### Hand it over cleanly at the end The awkward part of freelance delivery is the moment the client takes ownership. Moving the same site to their domain is the least disruptive version of that. - Connect a domain the client owns from Pro, $15 a month, with certificates handled. - Registrar-specific DNS guides with the exact records to add. - Visitor analytics from Pro, so "is anyone using it" has an answer. ### The paperwork lives in the same place A client project is rarely only a website. Proposals, specs, exports and slide decks all publish the same way and get the same kind of link. - PDFs open in the browser rather than downloading, so a proposal is one tap on a phone. - Images, video, audio, spreadsheets and Office documents are all handled, 96 extensions in total. - Related: turning a PDF into a link. ## What the free plan includes Enough to run one client preview end to end before you decide whether this belongs in your workflow. - 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. ## Compared with Tiiny Host Tiiny Host is used for the same job by a lot of freelancers and does it well. These rows are the ones that come up during an actual project rather than during signup. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. Tiiny Host: 1 site, 5,000 visits and 5 GB bandwidth a month, 3 MB per project (0.5 MB for a PDF). - **Custom domain.** Droply: From Pro, $15 a month. Tiiny Host: From Solo, $18 a month or $13 billed annually, up to 5 domains per account. - **Password protection.** Droply: From Starter, checked at the edge before any file is served. Tiiny Host: From Solo, $18 a month or $13 billed annually. - **Expiring links.** Droply: From Starter: 6 hours, a day, a week, a month or a date you pick. Tiiny Host: Not documented as a feature in the help center. - **Rollback to an approved version.** Droply: From Pro, in one click. Tiiny Host: No self-serve rollback is documented. A deleted link can be restored by contacting support. - **Security check on deploy.** Droply: Every publish, on every plan, including free. Tiiny Host: Not offered. - **Entry paid price.** Droply: $5 a month for Starter. Tiiny Host: $9 a month for Tiny, or $5 billed annually. Tiiny Host figures come from its own help center, checked 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (updated 2 September 2026), the free-plan link duration article (updated 21 August 2026), the password-protection article (updated 3 September 2026) and the custom-domains guide (updated 7 September 2026). Product plans can change. ## When Droply is the wrong choice Client work often needs more than a place to put files. Be honest with yourself about which of these the project is. - The client needs a CMS so they can edit copy after you leave. Hand over a hosted WordPress or a headless setup instead; a static upload leaves them dependent on you for every word change. - The deliverable is a web application with accounts and stored data. That is not a static site and nothing here will make it one. - You need an audit trail of who approved which version, with comments attached. This keeps versions, not conversations. - 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. ## Frequently asked questions ### Who is this for? Freelancers and small agencies who already have a finished site, prototype or document and need it behind a link a client can open, without setting up hosting for a project that may still change. ### Can I use my client's own domain? Yes, from Pro at $15 a month. Point a domain the client owns at the site and it is served from their address with HTTPS handled. Until then the work lives on a Droply subdomain. ### Can I keep a client preview private? Yes, from Starter. The password is checked at the edge before any file is served, so images and scripts are protected as well as the pages. Free sites are also served noindex, so unfinished work does not turn up in search. ### Can I set a preview to expire? Yes, from Starter. A link can lapse after six hours, a day, a week, a month, or on a date you choose, and it flips to an expired page rather than breaking. You can bring it back at any time. ### What happens after client feedback? Publish the revised build to the same site. The address does not change, so the link already in the email thread now shows the new version, and from Pro the previous one is a click away. ### Can I host proposals and PDFs too? Yes. PDFs open directly in the browser rather than downloading, and images, video, spreadsheets and Office documents are all supported, 96 extensions in total. ### How many client sites can I run at once? One on the free plan. Paid tiers raise it, and the pricing page shows the count per tier alongside storage and traffic. ### Do I have to explain anything technical to the client? No. They receive a normal HTTPS link that opens in any browser on any device. Nothing is downloaded, nothing is unzipped and no account is needed to view it. ### Does Droply manage source code or ongoing development? No. It publishes finished output. Keep source control, collaboration and builds in the tools the project already uses; this is only the delivery step. ## Related - [Client Website Preview](https://droply.host/client-website-preview) - [Static Website Hosting](https://droply.host/static-website-hosting) - [Portfolio to Link](https://droply.host/portfolio-to-link) --- Source: https://droply.host/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 replace the build in place as the feedback arrives. ## 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 it is not public in the sense that matters. Unfinished work should not be indexed by a search engine or forwarded outside the project. Free sites here are served with a noindex header, password protection from Starter is enforced before any file is served, and from Starter the link can be set to lapse on its own once the round is over. The pricing page lists which tier carries each of those. ## How it works 1. **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. 2. **Send the preview link.** A normal HTTPS address that opens on a phone, a tablet or a work laptop. Feedback is then about the real page rather than a screenshot of it. 3. **Replace it after each round.** Publish the revised build to the same site. The client refreshes the link they already have and sees the new version. ## What you 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 static hosting for freelancers. - 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. ### The client sees what a visitor will see A preview is only useful if it behaves like the real thing. It is served from the same edge as a published site, over the same HTTPS, with the same caching. - Works on any device with a browser; nothing to install and no account for the reviewer. - Real HTTPS with a valid certificate, so no browser warnings distract from the feedback. - Visitor analytics from Pro, if you want to know whether the review link was actually opened. ## 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. ## Compared with Netlify Drop 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. - **Is the link yours straight away?.** Droply: Yes. Publishing needs an account, so there is nothing to claim afterwards. Netlify Drop: No. An anonymous drop creates a temporary project you have one hour to claim. - **Same address after a revision.** Droply: Yes. Publishing replaces the content behind it, atomically. Netlify Drop: Yes. An updated folder publishes as the latest production version of the same project. - **Password protection.** Droply: From Starter, enforced at the edge before any file is served. Netlify Drop: From its Pro plan. An unclaimed drop gets a temporary password of its own, which is not the same thing. - **Expiring preview link.** Droply: From Starter: 6 hours, a day, a week, a month, or a date you pick. Netlify Drop: Not offered. An unclaimed drop expires in one hour whether you want that or not. - **Rollback to a reviewed version.** Droply: From Pro, in one click. Netlify Drop: Yes. Publishing a previous deploy is instantaneous and does not rebuild. - **Size guidance.** Droply: 25 MB per upload on free; substantially higher on paid tiers. Netlify Drop: 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.** Droply: No. The client opens a link. Netlify Drop: No. - **What the product is for.** Droply: Publishing finished files, previews included. That is the whole product. Netlify Drop: 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 want comments pinned to elements on the page, with threads and resolution. Use a review tool built for that and share this link inside it. - 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. ## Frequently asked questions ### How do I create a client website preview link? Upload the finished HTML or ZIP of the site, pick a name and publish. You get an HTTPS address in seconds that you can send to the client, and republishing keeps that same address. If the site came out of a framework, the deploy guides name the build command and output folder first. ### Can clients open the preview without an account? Yes. Anyone with the link can open it in any browser on any device. An account is only needed by the person publishing the site. ### Can I password-protect a client preview? Yes, from Starter. The password is checked at the edge before any file is served, so images, scripts and stylesheets are protected too, not only the first page. ### Can the preview link expire on its own? Yes, from Starter. Choose six hours, a day, a week, a month, or a specific date. When it lapses the address shows an expired page rather than breaking, and you can restore it later. ### Will the preview show up in Google? Not on the free plan: free sites are served with a noindex header. On paid plans indexing is allowed, so if a preview must stay out of search, keep it on a free site or add a password. ### Can I update the preview after feedback? Yes, and that is the point of the workflow. Publish the revised build to the same site and the link the client already has now shows the new version. ### Can I go back to the version the client approved? From Pro, yes, in one click. The free plan keeps only the current version, which is enough to publish but not to roll back. ### Is this a staging environment? No. It serves static files. An application that needs a backend, a database or server-side routes needs a real staging environment that runs the application. ### How do I know whether the client opened it? Visitor analytics are available from Pro, which is enough to answer whether the link was opened and roughly when. ## Related - [Static Hosting for Freelancers](https://droply.host/static-hosting-for-freelancers) - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip) - [HTML to URL](https://droply.host/html-to-url) --- Source: https://droply.host/host-ai-generated-website # Host an AI-generated website, with or without a build To host an AI-generated website you first have to know what the tool handed back, and it is one of two things: a single file, or a whole project. A single HTML, JSX or TSX file runs here at a real address with no build step. A project needs its build run first, and this page says which one you are holding. ## Why do some AI websites publish instantly and others do not? Because AI tools produce two very different artefacts. A chat that writes you a page produces one self-contained HTML file, which a browser can already render, so publishing it is a copy. A tool that scaffolds an app produces a project: source files, a package.json, a dependency list and a build configuration, which no browser can render until a build has turned them into files. The confusion comes from both being described as "the AI built me a website". They are not the same object. If you look at what you downloaded and see package.json, src/ or node_modules, you have a project, and the missing step is running its build on your machine. The framework deploy guides name the exact command and output folder for 23 frameworks, and the export guide walks through it in three steps. There is one case in between, and it is the one worth knowing. A single React file, a lone .jsx or .tsx component, is not a project and does not need a build. Uploaded here it is transformed in the visitor browser, with React and a Tailwind runtime served from our own edge, and it runs at a real URL. That covers most of what a chat assistant hands back. It does not cover a project that merely happens to contain one component. Which of those two you are holding depends almost entirely on which tool you used, so the grid below is the useful next click. Each page states what that tool actually produces, the steps to get the code out of it using its own menu labels, and the failures specific to its output, with the vendor documentation each claim was read from and the date it was read. ## How it works 1. **Work out what you have.** One file with everything inside it, or a folder with a package.json. The first is ready to publish; the second has to be built first, and the difference is the whole story. 2. **Upload the result.** Drop the single file, or the output folder from the build. Nothing is installed on our side and nothing you upload runs on our servers. 3. **Share a real address.** The page is live over HTTPS. Regenerate, re-upload, and the address stays the same, so a link you sent still shows the current version. ## What you get ### Single-file output runs with no build The common case for anyone generating a page in a chat: one file, no dependencies to install, no bundler. - A self-contained .html page publishes as it is. - A single .jsx or .tsx is transformed in the visitor browser at the published URL. - React and the JSX runtime are served from our own edge, not from a public CDN. - Any other package is not fetched on your visitors' behalf; the live page names what is missing rather than rendering blank. ### Project output publishes after one build When the AI scaffolded a real project, the missing step is a build, and it happens on your machine rather than ours. - Run the framework build, then upload the folder it produced. - Guides for 23 frameworks, each naming the command and output folder. - Upload it as a folder or a ZIP; see hosting a static site from a ZIP for the three ways a ZIP goes wrong. - Server-rendered routes and API handlers do not run here, whatever the tool scaffolded. ### Generated code is checked after it goes live AI-written code is where hard-coded keys turn up most often, because the model helpfully filled in the value it saw. Every publish is read and reported. - API keys in inline scripts, a Supabase service role key, a token in a data attribute. - A .env or .git that came along inside an exported folder. - On every plan including free, and it never blocks the publish. See the security check. ### Built for the tenth regeneration Generated pages are regenerated constantly. The address is fixed from the first publish so the iteration does not cost you a new link each time. - Up to 15 publishes a day on the free plan. - From Pro, going back to the version that worked is one click. - The swap is atomic, so a visitor never sees a half-published page. ## What the free plan includes Publishing generated output costs nothing. That matters here more than elsewhere, because most generated pages are thrown away. - 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. ## Compared with Static.app Static.app has the deepest content in this category and is a serious product. The rows below are the ones its own pricing and documentation make checkable. - **Loose .html file accepted.** Droply: Yes, dropped on its own. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **React artifact without conversion.** Droply: A single .jsx or .tsx runs at the URL, transformed in the visitor browser. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version instead. - **Import from a URL.** Droply: Site import copies up to 40 pages and 600 assets from any site you point it at. Static.app: Import from URL takes claude.ai and claude.site links. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter. Static.app: $5 a month, or $60 a year, for 2 sites and 500 MB. - **Custom domain.** Droply: From Pro, $15 a month. Static.app: Included in the $5 entry tier. - **Builds a project for you.** Droply: No. Build locally, upload the output. Static.app: No. - **Security check on deploy.** Droply: Every publish, every plan, free included. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask Claude for a self-contained HTML version, that Import from URL takes claude.ai and claude.site links, and that the first 7 days are free with no credit card. Product plans can change. ## When Droply is the wrong choice A lot of what AI tools generate is not a static site, and no host will make it one. Recognising that early is cheaper than discovering it after an upload. - The generated app has a database, authentication or server actions. Those need a runtime; only the static half can be published here. - You want the platform to run npm install and npm run build for you. That does not happen here: bring the build output. - The project is multi-file and you cannot build it locally. Nothing here renders it as-is, and pretending otherwise would put a visually broken page at a real address. - 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. ## Frequently asked questions ### Can I host a website an AI generated? Yes. A single self-contained HTML file, or a single .jsx or .tsx file, publishes with no build step. A full project needs its build run on your machine first, and then you upload the output folder. ### How do I know whether I have a file or a project? Look at what you downloaded. One file with everything inside it is a file. A folder containing package.json, src or node_modules is a project, and it has to be built before a browser can render it. ### Does Droply generate the website for me? This page is about publishing output you already have. There is a separate AI page builder that writes, previews and publishes a page from a description, if what you want is the generating step. ### What if the generated project uses a framework? Run its build locally and upload the folder it produces. The deploy guides name the exact command and output folder for 23 frameworks, including the ones AI tools scaffold most often. ### Is there a page for the specific tool I used? Yes, for eight of them: v0, bolt.new, Lovable, Replit, ChatGPT, Gemini, Cursor and Codex, plus Claude artifacts. Each one covers what that tool outputs, the steps to get the code out of it, and what breaks. The grid above links to all of them. ### Can I publish HTML from ChatGPT or Claude? Yes. Save the HTML block as index.html and upload it. If the answer was a React component instead, save it as a .jsx file and upload that; it runs in the browser at the published address. ### What about packages the generated code imports? React and the JSX runtime are provided. Other packages are not fetched from a public CDN on your visitors' behalf, because that would run third-party code and leak visitor IP addresses to it. The live page lists what is missing by name, and the fix is to build the project locally. ### Can the published site use a database or server actions? No. What is published is static. If the page calls an API, that API has to already exist somewhere else and allow browser requests under its own CORS rules. ### Is generated code checked for leaked keys? Yes, on every plan including free. AI-written code is a common place to find a hard-coded API key, and every publish is read after it goes live and reported in plain language. ### Can I keep regenerating and republishing? Yes, up to 15 times a day on the free plan, always at the same address. From Pro you can also return to an earlier version when a regeneration makes things worse. ## Related - [Publish a Claude Artifact](https://droply.host/publish-claude-artifact) - [HTML to URL](https://droply.host/html-to-url) - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip) --- Source: https://droply.host/publish-claude-artifact # Publish a Claude artifact as a real website To publish a Claude artifact you need the one file Claude hands you: a React component or an HTML page. Drop that file here and it runs at a real HTTPS address, in the visitor browser, with no build step, no npm install and no server. Multi-file projects need a build first, and this page says so rather than guessing. ## What is a Claude artifact, in hosting terms? A single file with no build output. Usually a React component in .jsx or .tsx, often with Tailwind classes, sometimes a complete HTML page. Claude renders it inside its own window; publishing it means running that same file at a public address so anyone can open it without a Claude account. The reason this normally requires a build is that browsers do not understand JSX or TypeScript. Something has to transform them into plain JavaScript first, and that something is usually a bundler running on your machine or on a build server. Here the transform happens in the visitor browser instead, using a runtime served from our own edge along with React and a Tailwind runtime. The result is that a lone component file becomes a working page with nothing installed anywhere. That trick has an honest boundary. It works for one file. A multi-file project has its own Tailwind configuration, a dependency tree and often server code, and rendering it without its real build produces something visually wrong rather than something broken enough to notice. So a project upload is told exactly that, with a link to the three-step export guide, instead of being published as a page that looks almost right. ## How it works 1. **Save the artifact as a file.** Download the artifact from Claude, or copy its code into a file. A React artifact is a .jsx or .tsx; an HTML artifact is a single .html page. That one file is all you need. 2. **Drop the file.** Upload it. The JSX and TypeScript are transformed in the visitor browser by a runtime we host ourselves, with React and the Tailwind classes Claude writes. Nothing you upload ever runs on our servers. 3. **Share the link.** The artifact is live on an HTTPS address you can send to anyone. Upload a new version and the link stays the same, so what you already shared keeps working. ## What you get ### The single-file runtime This is the feature the page exists for. It is scoped deliberately, and the scope is stated everywhere rather than discovered. - A .jsx or .tsx file is transformed in the visitor browser, not on our servers. - React, the JSX runtime and a Tailwind runtime are served from our own edge. - A Babel-flavoured HTML page works the same way. - Nothing you upload is ever executed on our infrastructure. We serve static files. ### Packages are named, not silently fetched An artifact often imports an icon set or a UI kit. Pulling those from a public CDN on your visitors' behalf would run third-party code in their browser and hand that CDN their IP address, so we do not. - The live page lists the missing packages by name instead of rendering blank. - The fix is to build the project locally and upload the output folder. - The deploy guides cover the frameworks those projects usually use. ### One link across every revision Artifacts get regenerated. The address belongs to the site, so the link you sent after the first version still shows the current one. - Up to 15 publishes a day on the free plan. - From Pro, restoring the version that worked is one click. - The switch is atomic; a visitor never sees a half-published page. ### It behaves like a published site, because it is one An artifact at an address gets the same treatment as any other site here, which is more than a share link normally gets. - Password protection from Starter, checked at the edge. - Visitor analytics from Pro. - Expiring links from Starter, for something meant to be temporary. - The deploy-time security check, on every plan, including free. ## What the free plan includes Publishing an artifact costs nothing, and the address does not move when you republish, which matters when most artifacts are shared once and then edited twice. - 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. ## Compared with Static.app Static.app has its own Claude hosting page, which makes this an unusually checkable comparison: the rows below come from what each product says about the same file. - **Loose .html file accepted.** Droply: Yes, dropped on its own. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **React artifact without conversion.** Droply: A single .jsx or .tsx runs at the URL, transformed in the visitor browser. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version instead. - **Multi-file project.** Droply: Refused with a named reason and a link to the export guide. Static.app: Accepted as a ZIP of built output. - **Third-party packages.** Droply: Not fetched from a public CDN; the live page names what is missing. Static.app: Depends on the self-contained HTML you supply. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter. Static.app: $5 a month, or $60 a year, for 2 sites and 500 MB. - **Password protection.** Droply: From Starter, enforced at the edge. Static.app: Not listed on any of its plans. - **Security check on deploy.** Droply: Every publish, every plan, free included. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask Claude for a self-contained HTML version, that Import from URL takes claude.ai and claude.site links, and that the first 7 days are free with no credit card. Product plans can change. ## When Droply is the wrong choice The single-file runtime is a real capability with a real edge, and the edge is where people get disappointed. These are the cases it does not cover. - Your artifact is a multi-file project. Build it locally and upload the output; nothing here renders a project without its build. - It imports packages beyond React. They are not fetched for your visitors, so the page will name them rather than render them. - It calls an API that needs a secret. A published page is readable by anyone, so any key inside it is public the moment it goes live. - 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. ## Frequently asked questions ### What is a Claude artifact, in hosting terms? A single file with no build output: usually a React component in .jsx or .tsx, sometimes with Tailwind classes, or a complete HTML page. Publishing it means running that same file at a public URL. ### Do I need to run npm or a build step? No, not for a single-file artifact. The JSX and TypeScript transform happens in the visitor browser using a runtime served from our own edge, with React and a Tailwind runtime included. Nothing is installed and nothing runs on our infrastructure. We still only ever serve static files. ### What about packages the artifact imports? React and the JSX runtime are provided. Any other package, such as an icon library or a UI kit, is not fetched from a public CDN on your behalf: that would run third-party code and leak your visitors' IP addresses to it. The live page lists the missing packages by name, and the fix is to build the project locally and upload the output. ### My artifact is a whole project with several files. Does that work? Not in the browser. A multi-file project has its own Tailwind config, dependency tree and often server code, and rendering it without its build would come out visually wrong. Upload it and the page says exactly that, with a link to the three-step export guide. ### Can I publish artifacts from ChatGPT, v0, Lovable or bolt.new the same way? A single HTML or JSX file from any of them, yes: the path is identical. Lovable and bolt.new exports are usually full projects, so they take the build-first route. There is a page per tool covering the export and what breaks: ChatGPT, v0, Lovable, bolt.new, and the rest are listed on the AI hosting hub. ### Is the published artifact a static site? Yes. It has no server, no database and no server actions. If the artifact calls an API, that API has to exist somewhere else and allow requests from a browser. ### Can I put a password on it? Yes, from Starter. The password is checked at the edge before any file is served, so the runtime and its assets are covered as well as the page. ### Can I update the artifact after sharing the link? Yes. Upload the new file and it is published at the same address, so the link you already sent shows the current version. From Pro you can also restore an earlier one. ### Is it free to publish an artifact? Yes: 1 site with HTTPS, 25 MB of storage and 5,000 visits a month, with no card and nothing to claim afterwards. ### Will the artifact be indexed by search engines? Not on the free plan, which is served noindex on purpose. Indexing starts on Starter if you want the page found rather than just shared. ## Related - [Host an AI-Generated Website](https://droply.host/host-ai-generated-website) - [HTML to URL](https://droply.host/html-to-url) - [HTML Hosting](https://droply.host/html-hosting) --- Source: https://droply.host/react-hosting # React hosting for an app you have already built React hosting without a pipeline: run your build, drag the output folder in, and the app is live on its own HTTPS address in seconds. There is no repository to connect and no deploy configuration to write, because what you upload is what gets served. ## What is React hosting? React hosting means hosting the static files your React build produced, not React itself. React is a library that runs in the browser, so once a bundler has turned your components into HTML, JavaScript and CSS, what is left is an ordinary folder of files that any static host can serve. That is why the question "which host runs React" is slightly the wrong question. React does not run on a server unless you have deliberately chosen a setup that renders on one. A plain React app built with Vite or Create React App is finished at build time, and hosting it is the same job as hosting any other static site. The practical consequence is that the folder matters more than the framework. Vite writes to dist, Create React App writes to build, and a Next.js static export writes to out. Upload the right one and the app works; upload the project folder and nothing does. The framework deploy guides carry the exact command and folder for each. There is one shortcut worth knowing about. A single .jsx or .tsx file with no package imports does not need a build at all: drop the file and it is transformed in the visitor browser at the published address. That covers a component you want a colleague to look at, not a real application. ## How it works 1. **Build it where you already build it.** Run the build on your machine or in whatever CI you already have. Nothing about your toolchain has to change and nothing new gets installed. 2. **Drop the output folder.** Drag the folder your bundler produced, or a ZIP of it. Your JavaScript chunks, CSS, fonts and images keep the relative paths the build gave them. 3. **Ship the next version to the same URL.** Upload a new build when the app changes. The address does not move, so links you have already sent keep resolving to the current version. ## What you get ### Every React toolchain, with the folder named The single most common way a React deploy fails is uploading the wrong directory, because the three popular toolchains disagree about what to call the right one. Each has its own guide here rather than one page of averages. - Vite: the build writes to dist. See the Vite deploy guide. - Create React App: the build writes to build, and absolute asset paths are the usual first failure. See the Create React App guide. - Next.js: needs a static export before there is anything to upload, and it lands in out. See Next.js hosting. - Gatsby: the build writes to public, which catches out anyone expecting dist. ### Client-side routes that do not 404 A React app with a router serves its own paths in the browser. A static host asked for /settings looks for a file at that path, does not find one, and answers 404 before your JavaScript has loaded. This is the single most reported problem with hosting a React build anywhere. - Turn on the Single-page app switch in the site settings and unknown paths are served the root index.html instead, so the router takes over. - It is free on every plan and applies without redeploying the site. - It is off by default, because a multi-page site genuinely wants a real 404 for a path that does not exist. ### The keys your bundle is carrying, named Anything in a React bundle is readable by anyone who opens the page, and environment variables prefixed for the client are compiled straight into it. Every publish is checked and the finding is written in plain language. - A committed .env file, a .git directory, a private key, or an API key left in a JavaScript chunk. - It runs after the site is live and never blocks the publish, so it cannot cost you a deploy. - Included on the free plan. See how the security check works. ### Your own domain when the demo becomes the product A subdomain is right for a review link and wrong for a launch. From Pro the same build is served from a domain you own, with no rebuild and no change to the files. - Certificates are issued and renewed automatically, on the Droply address and on yours. - Step-by-step DNS guides for the common registrars, with the exact records. - Free sites are served noindex, so search engines will not list them. Indexing starts on Starter. ## What the free plan includes Everything below is on the free plan, with no card and no trial to run out, which is enough to put a built React app at a real address today. - 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. ## Compared with Static.app Static.app is the closest competitor here, because it is the only one that publishes a page per framework the way this cluster does. Neither product runs your build, so these are the rows that actually differ for somebody holding a React build folder. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits a month, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter, or $60 a year. Static.app: $5 a month or $60 a year for Starter: 2 sites, 500 MB, custom domain included. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its own documentation states a loose .html file must be zipped first. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: Not offered. - **Single-page app fallback.** Droply: A switch in the site settings, free on every plan, applied with no redeploy. Static.app: Not documented as a per-site setting. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted for upload and must be zipped first. Both products publish finished output rather than running your build, so the rows below compare what each one accepts and what it costs, not build speed. Product plans can change. ## When Droply is the wrong choice A React app is not automatically a static site, and the difference is worth establishing before you upload anything. If your project needs a server at request time, no amount of configuration here will give it one, and finding that out now is cheaper than finding it out after three uploads. - Your app has API routes, server actions, or a session that is established on the server. Only the client half can be published here. - You are server-rendering for SEO or for a personalised first paint. A fully static export works; server rendering does not. - You want the build to run on every push. There is no Git integration and no build step: you build, then you upload. - 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. ## Frequently asked questions ### How do I host a React app? Run your build, then upload the folder it produced. With Vite that is dist, with Create React App it is build. Drag the folder or a ZIP of it in, pick a name, and the app is live on an HTTPS address in seconds. ### Is React hosting free here? Yes. The free plan gives you 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included and no card. It is a plan in its own right, not a trial that expires. ### Do I upload the src folder or the build folder? The build folder. The src folder holds JSX that no browser can run, so uploading it publishes a site with nothing to display. The deploy guides name the exact output folder for 23 toolchains. ### Why does my React app 404 on every page except the home page? Because the routes exist only after JavaScript runs, and the host was asked for a file that is not there. Turn on the Single-page app switch in the site settings and unknown paths are served index.html instead. It is free on every plan. ### Can I host a React app without a build step? Only for a single file. A lone .jsx or .tsx with no package imports is transformed in the visitor browser at the published address. A real application with dependencies has to be built first. ### Does Droply run npm install or npm run build for me? No, and it will not. Running your dependencies on our servers is a different and much riskier product. You build locally or in the CI you already have, and upload the result. ### Can I host a Next.js app here? Only as a static export. Next.js renders on a server by default, so it needs output: "export" before there is anything to publish, and the server features do not survive that. Next.js hosting covers what is lost. ### What happens to the URL when I upload a new build? Nothing. Each upload becomes a new version and publishing points the same address at it, so every link you already shared keeps working. On Pro and above you can roll back to an earlier version in one click. ### Can I use my own domain for a React app? Yes, from Pro at $15 a month. You point a domain you own at the site and it is served from your address with HTTPS handled for you. ### How big can a React bundle be? Each plan sets an upload size and a total storage allowance. The free plan is 25 MB per upload and 25 MB overall, which is comfortable for a typical single-page app; the pricing page lists every tier. ## Related - [Vue Hosting](https://droply.host/vue-hosting) - [Next.js Hosting](https://droply.host/nextjs-hosting) - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip) --- Source: https://droply.host/vue-hosting # Vue hosting for a project you have already built Vue hosting without a pipeline: build the project, upload the folder your tooling produced, and it is live on its own HTTPS address in seconds. Vue, Nuxt and VitePress each write somewhere different, and this page is mostly about getting that part right. ## What is Vue hosting? Vue hosting means serving the static files your Vue build produced. Vue runs in the browser, so once Vite has compiled your single-file components into HTML, JavaScript and CSS, the result is an ordinary folder that needs nothing more than a web server pointed at it. Where it gets confusing is that "a Vue project" covers four quite different builds. A plain Vue app scaffolded with create-vue is a Vite project and writes to dist. Nuxt renders on a server by default and only produces a publishable folder when you ask it to generate one. VitePress and VuePress both write into a folder nested inside a dot-directory, which is why people upload their Markdown source by mistake. None of that is a Vue problem, and none of it needs a special host. It just means the folder you upload is the one decision that matters, and it is different for each tool. The framework deploy guides name the exact command and folder for all four, and the Nuxt guide covers the generate step in particular. ## How it works 1. **Build the project.** Run the build you already run. Nothing about the project changes and nothing new has to be installed for it to be publishable. 2. **Upload the output folder.** Drag the folder the build wrote, or a ZIP of it. Two of the four Vue toolchains hide it inside a dot-directory, which is the part worth checking. 3. **Republish to the same address.** A new build replaces the old one at the same URL. Documentation links and review links you have already sent stay valid. ## What you get ### Four toolchains, four folders, named Uploading the wrong directory is the failure that costs a Vue developer an afternoon, and the Vue ecosystem makes it easy: two of the four write into a hidden folder. Each has its own guide rather than one page of averages. - Vue with Vite: the build writes to dist. See the Vite deploy guide. - Nuxt: npx nuxi generate rather than the usual build, and the site lands in .output/public. See the Nuxt guide. - VitePress: the output is nested at docs/.vitepress/dist, not the docs folder holding your Markdown. See the VitePress guide. - VuePress: same shape, at docs/.vuepress/dist. See the VuePress guide. ### Vue Router paths that resolve Vue Router in history mode produces clean paths that exist only once the app has loaded. Asked for one directly, a static host looks for a file, finds nothing and answers 404. Every static host has this problem and it has a one-switch fix here. - Turn on the Single-page app switch in the site settings and unknown paths are served the root index.html, so the router resolves them. - Free on every plan, applied without a redeploy. - Leave it off for a VitePress or VuePress site: those generate a real file per page and should return a real 404. ### A check on what the bundle is carrying Vite compiles anything prefixed for the client straight into the bundle, where it is readable by anyone who opens the page. Every publish is read and anything sensitive is named in plain language. - A committed .env file, a .git directory, a private key, or an API key left in a JavaScript chunk. - It runs after the site is live and never blocks a publish. - Included on the free plan. See how the security check works. ### A domain, and a URL that survives the next release Documentation earns its links slowly, so the address has to outlive the build that created it. Publishing a new version keeps the address, and from Pro the address can be one you own. - The URL does not change when you republish, so external links and search results keep resolving. - Certificates are issued and renewed automatically on both the Droply address and yours. - Free sites are served noindex. Search visibility starts on Starter, which matters more for docs than for a prototype. ## What the free plan includes Everything below is on the free plan, with no card and no trial to run out, which is enough to put a built Vue app or documentation site at a real address today. - 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. ## Compared with Static.app Static.app publishes the same kind of per-framework page, and neither product builds your project for you. These are the rows that differ for somebody holding a Vue or Nuxt build folder. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits a month, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter, or $60 a year. Static.app: $5 a month or $60 a year for Starter: 2 sites, 500 MB, custom domain included. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its own documentation states a loose .html file must be zipped first. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: Not offered. - **Single-page app fallback.** Droply: A switch in the site settings, free on every plan, applied with no redeploy. Static.app: Not documented as a per-site setting. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted for upload and must be zipped first. Both products publish finished output rather than running your build, so the rows below compare what each one accepts and what it costs, not build speed. Product plans can change. ## When Droply is the wrong choice Nuxt is the reason this section matters more on a Vue page than on most. It is a server framework that can also generate a static site, and the two modes are genuinely different products. If your project depends on the server half, publishing the generated half will look like it worked and then behave incorrectly. - Your Nuxt app uses server routes, anything under server/, or server middleware. Those do not come across when you generate. - You need data fetched per request rather than at build time. Generated pages carry the data as it was when you built them. - You want incremental or on-demand regeneration. That is a server feature, so it needs a host that runs Node. - 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. ## Frequently asked questions ### How do I host a Vue app? Build the project and upload the folder it produced. A Vite-based Vue app writes to dist. Drag that folder or a ZIP of it in, pick a name, and the app is live on an HTTPS address in seconds. ### Is Vue hosting free here? Yes. The free plan gives you 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included and no card required. ### Can I host a Nuxt app? Yes, as a generated static site. Run npx nuxi generate instead of the usual build and upload .output/public. Server routes do not come across; the Nuxt guide is specific about what does. ### Which folder do I upload for VitePress? The nested one: docs/.vitepress/dist, not the docs folder that holds your Markdown. VuePress follows the same shape at docs/.vuepress/dist. ### Why does my Vue app 404 when I refresh a route? Vue Router in history mode serves those paths in the browser, so the host is being asked for a file that does not exist. Turn on the Single-page app switch in the site settings and unknown paths are served index.html instead. ### Does Droply run the Vue build for me? No. We publish finished files and never run your dependencies. Build locally or in the CI you already have, then upload the output folder. ### Can I host a Vue site on my own domain? Yes, from Pro at $15 a month. Point a domain you own at the site and it is served from your address, with the certificate issued and renewed for you. ### What happens to the URL when I publish a new version? It stays the same. Each upload is a new version and publishing repoints the same address, so documentation links keep working. Rollback to an earlier version is one click from Pro. ### Can I password-protect a Vue documentation site? Yes, from Starter. The password is checked at the edge before any file is served, so the pages and their assets are both covered rather than just the front page. ### Will a published Vue site show up in Google? Only on a paid plan. Free sites are served with a noindex header on purpose, because free subdomains on a shared domain are the raw material for spam farms. Indexing starts on Starter. ## Related - [React Hosting](https://droply.host/react-hosting) - [Astro Hosting](https://droply.host/astro-hosting) - [Static Website Hosting](https://droply.host/static-website-hosting) --- Source: https://droply.host/angular-hosting # Angular hosting for an app you have already built Angular hosting without a pipeline: run ng build, upload the browser folder inside dist, and the app is live on its own HTTPS address in seconds. The nesting is the part people get wrong, and it is the part this page is about. ## What is Angular hosting? Angular hosting means serving the compiled output of an Angular build. Angular compiles ahead of time, so by the time the build finishes there is no Angular left to run on a server: what remains is HTML, JavaScript bundles and assets that a static host serves as files. The one thing that trips people up is the shape of the output directory. Angular 17 and later write the browser bundle to dist//browser, one level deeper than older versions did, and dist itself contains no index.html at all. Uploading dist therefore produces a site with nothing to serve, which reads as a hosting problem and is not one. The second thing worth knowing before you build is whether server-side rendering is switched on. If your project uses @angular/ssr, the build also emits a server bundle alongside the browser one. Only the browser folder can be published here. The Angular deploy guide carries the exact command and the full path. ## How it works 1. **Run ng build.** Build the project the way you already do. Nothing in angular.json has to change for the result to be publishable here. 2. **Open dist and go one level deeper.** Angular writes the publishable files to the browser folder inside your project folder in dist. That is the folder to upload, and dist itself is not. 3. **Publish and share the link.** Drag the folder in, pick a name, and the app is live on HTTPS in seconds. Republishing keeps the same address. ## What you get ### The folder, spelled out This is the whole Angular deployment problem, and most guides on the web still describe the pre-17 layout. Getting it right takes ten seconds and getting it wrong looks exactly like a broken host. - Upload dist//browser, where the project name is the one in angular.json. - Do not upload dist. It has no index.html in it, so the publish produces a site with no page to serve. - If SSR is enabled, the build also writes a server bundle. Only the browser folder is publishable here. - The Angular deploy guide carries the command and the path, and stays in step with the message a failed upload shows. ### Angular Router paths that do not 404 The Angular router owns paths like /reports/2026 in the browser. Requested directly, a static host looks for a file at that path and answers 404 before the app has loaded. This is expected behaviour, not a misconfiguration, and it has a one-switch fix. - Turn on the Single-page app switch in the site settings and unknown paths are served the root index.html, so the router resolves them. - Free on every plan, applied without redeploying. - Hash routing also works with no switch at all, if that is what the project already uses. ### What ends up inside the bundle Angular environment files are compiled into the bundle at build time, which makes a production environment file with a real key in it a published secret. Every deploy is read and anything sensitive is named. - An API key in environment.prod.ts, a committed .env, a .git directory, or a private key. - It runs after the site is live, reports in plain language, and never blocks a publish. - Included on the free plan. See how the security check works. ### A domain and a password when it stops being a demo An Angular app is often an internal tool before it is a public one, so the two things it needs first are a private address and then a real one. - Password protection from Starter, checked at the edge before any file is served. - A custom domain from Pro at $15 a month, with certificates handled automatically. - Free sites are served noindex, so an internal build will not turn up in a search result. Indexing starts on Starter. ## What the free plan includes Everything below is on the free plan, with no card and no trial to run out, which is enough to put a built Angular app at a real address today. - 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. ## Compared with Static.app Static.app publishes the same kind of per-framework page, and neither product builds your project. These are the rows that differ for somebody holding an Angular browser folder. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits a month, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter, or $60 a year. Static.app: $5 a month or $60 a year for Starter: 2 sites, 500 MB, custom domain included. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its own documentation states a loose .html file must be zipped first. - **Single-page app fallback.** Droply: A switch in the site settings, free on every plan, applied with no redeploy. Static.app: Not documented as a per-site setting. - **Password protection.** Droply: From Starter, checked at the edge before any file is served. Static.app: Not listed on its pricing page as a per-site option. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted for upload and must be zipped first. Both products publish finished output rather than running your build, so the rows below compare what each one accepts and what it costs, not build speed. Product plans can change. ## When Droply is the wrong choice Angular is often chosen for applications that talk to something, and the something is what decides whether this is the right host. A static host serves the client half perfectly and provides no server half at all. - Your app uses Angular Universal or @angular/ssr to render on the server. Only the browser build can be published here. - Your app needs an API, a database or an authentication service that you were expecting the host to provide. Bring your own; we serve files. - You want the build to run on push. There is no Git integration and no build step 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. ## Frequently asked questions ### How do I host an Angular app? Run ng build, then upload the browser folder inside dist/. Drag it in or upload a ZIP of it, pick a name, and the app is live on HTTPS in seconds. ### Which folder do I upload after ng build? The browser folder inside dist/, not dist itself. Angular 17 and later nest it one level deeper than older versions, and dist has no index.html in it. ### Is Angular hosting free here? Yes. The free plan gives you 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included and no card. ### Why does my Angular app 404 when I open a route directly? Because that path exists only inside the router, and the host was asked for a file that is not there. Turn on the Single-page app switch in the site settings and unknown paths are served index.html instead. It is free on every plan. ### Can I host an Angular Universal app? Only the browser half. Universal renders pages on a server per request, and there is no server here, so the SSR build cannot run. The browser bundle can be published and behaves as a normal single-page app. ### Does Droply run ng build for me? No. We publish finished files and never run your dependencies. Build locally or in the CI you already have, then upload the output folder. ### Can I put an Angular app behind a password? Yes, from Starter. The password is checked at the edge before any file is served, so the JavaScript bundles are covered as well as the pages. ### Can I use my own domain? Yes, from Pro at $15 a month. Point a domain you own at the site and it is served from your address, with HTTPS issued and renewed automatically. ### What happens when I upload a new build? It becomes a new version at the same address, so shared links keep working. From Pro you can roll back to a previous version in one click. ### How big can an Angular build be? The free plan allows 25 MB per upload and 25 MB of storage overall. A typical production Angular bundle fits comfortably; the pricing page lists the limits for every tier. ## Related - [React Hosting](https://droply.host/react-hosting) - [Vue Hosting](https://droply.host/vue-hosting) - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip) --- Source: https://droply.host/nextjs-hosting # Next.js hosting for a statically exported site Next.js hosting for the static half: add output export, build, and upload the out folder to get a live HTTPS address in seconds. Server rendering, API routes and middleware do not survive the export, and this page says so before you upload anything. ## What is Next.js static hosting? Next.js static hosting means publishing the output of a Next.js static export: every page rendered once at build time into plain HTML, rather than assembled on a server for each visitor. It is a real and supported Next.js mode, and it is the only mode a static host can serve. Next.js renders on a server by default, which is why "can I host Next.js on a static host" has a conditional answer rather than a yes. Adding output: "export" to next.config.js changes that: the build writes finished pages into out, and that folder is an ordinary static site. What the export drops is the part worth reading twice, because nothing here can configure around it. API routes, server actions, middleware, on-demand revalidation and dynamic image optimisation all run on a server, and after an export there is no server. If your app depends on any of them, it needs a host that runs Node, and that is a real answer rather than a limitation of this product. If it does not, the export is genuinely finished output and behaves like any other static site: fast, cacheable and cheap to serve. The Next.js deploy guide carries the exact config change and the build command. ## How it works 1. **Turn the export on.** Add output export to next.config.js. This is the switch that tells Next.js to finish the pages at build time instead of rendering them per request. 2. **Build and open out.** Run the build. The finished site appears in out, not in .next, which holds build artefacts rather than a publishable site. 3. **Upload out.** Drag the folder or a ZIP of it in. The site is live on HTTPS in seconds and republishing keeps the same address. ## What you get ### The two things to change, and nothing else A Next.js static export is a short list, and most failed attempts come from missing one item on it rather than from anything structural. - Add output: "export" to next.config.js. Without it the build produces a server bundle and there is nothing to upload. - Upload out, not .next. The second one holds build artefacts, not a site. - If you use next/image, the export needs the optimizer disabled or a custom loader, because the default one is a server feature. - The Next.js deploy guide carries the command, and the Nextra guide covers documentation sites built on top of it. ### What the export leaves behind Stated plainly, because a host that lets you discover this after three uploads has wasted your afternoon. None of the following works after an export, on any static host. - API routes and route handlers, server actions, and middleware. - Incremental static regeneration and on-demand revalidation. - Dynamic image optimisation through the built-in loader. - Anything reading cookies or headers at request time to decide what to render. ### One address, every export Each upload becomes an immutable version and publishing swaps which one the address points at, so a rebuild is a publish rather than a migration. - The URL does not change, so links, bookmarks and QR codes keep working. - A visitor mid-load never sees half the old export and half the new one. - Rollback to a previous export is one click from Pro. ### A domain, without the platform The usual reason to export in the first place is to stop paying for a runtime the site does not use. From Pro the exported site is served from a domain you own. - Certificates issued and renewed automatically, on the Droply address and on yours. - Step-by-step DNS guides for the common registrars. - Free sites are served noindex. Search visibility starts on Starter, which a public marketing site will need. ## What the free plan includes Everything below is on the free plan, with no card and no trial to run out, which is enough to put a Next.js static export at a real address today. - 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. ## Compared with Static.app Static.app publishes the same kind of per-framework page, and neither product runs a Next.js server. These are the rows that differ once you are holding an exported out folder. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits a month, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter, or $60 a year. Static.app: $5 a month or $60 a year for Starter: 2 sites, 500 MB, custom domain included. - **Server rendering or API routes.** Droply: No. Static export only, and the page says so before you upload. Static.app: No. Both products serve files rather than running Node. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its own documentation states a loose .html file must be zipped first. - **Rollback to a previous export.** Droply: One click from Pro, with every version kept. Static.app: Backups are offered as a separate feature rather than a per-publish version history. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted for upload and must be zipped first. Both products publish finished output rather than running your build, so the rows below compare what each one accepts and what it costs, not build speed. Product plans can change. ## When Droply is the wrong choice This is the page in the cluster most likely to end with "go somewhere else", and that is the point of it. A Next.js app that uses the framework for what makes it distinctive is not a static site, and exporting it will either fail at build time or quietly drop behaviour you needed. - You use API routes, route handlers, server actions or middleware. Export them and they are simply gone. - You rely on incremental static regeneration to refresh pages after the build. Regeneration needs a running server. - You need per-request personalisation, cookie-aware rendering or authenticated server pages. - 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. ## Frequently asked questions ### Can I host a Next.js site on a static host? Yes, if you export it. Add output: "export" to next.config.js and build; the finished site lands in out and is an ordinary static site. Server features do not survive the export. ### Which folder do I upload for Next.js? The out folder that the export creates, not .next. The .next directory holds build artefacts and is not a publishable site. ### What stops working after a Next.js static export? API routes and route handlers, server actions, middleware, incremental static regeneration, on-demand revalidation, and dynamic image optimisation. All of them run on a server, and an exported site does not have one. ### Is Next.js hosting free here? Yes for the static export. The free plan gives you 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included and no card. ### Does next/image work in a static export? Not with the default loader, because optimisation happens on a server. Disable optimisation or configure a custom loader before you build, or images will fail during the export rather than after it. ### Can I host a Nextra documentation site? Yes. Nextra is a Next.js site, so it needs the same export switch plus unoptimized images, and it lands in out as well. The Nextra deploy guide has both config keys. ### Does Droply run next build for me? No. We publish finished files and never run your dependencies. Build locally or in the CI you already have, then upload the exported folder. ### Do dynamic routes work after an export? Only the ones that were generated at build time. A route whose parameters are known when you build is exported as a real page; one that expects to be resolved per request has nothing behind it. ### Can I use my own domain? Yes, from Pro at $15 a month, with the certificate issued and renewed automatically. The DNS guides cover the common registrars. ### What happens to the URL when I publish a new export? Nothing. Each upload is a new version at the same address, so shared links keep working, and rollback to a previous export is one click from Pro. ## Related - [React Hosting](https://droply.host/react-hosting) - [Astro Hosting](https://droply.host/astro-hosting) - [Host an AI-Generated Website](https://droply.host/host-ai-generated-website) --- Source: https://droply.host/astro-hosting # Astro hosting for a site that is already static Astro hosting with nothing to configure: Astro builds to plain HTML by default, so you run the build, upload dist, and the site is live on its own HTTPS address in seconds. The only thing that changes that is an adapter you added on purpose. ## What is Astro hosting? Astro hosting means serving the output of an Astro build, which by default is a folder of finished HTML pages with almost no JavaScript attached. Astro renders components at build time and ships interactive islands only where you asked for them, so what you upload is a site rather than an application. That makes Astro the easiest case in this cluster. There is no export switch to remember and no adapter to install: the default output mode already produces exactly what a static host serves, and the folder is dist. The one way it stops being true is an adapter. Adding an SSR adapter, for node or for a specific platform, changes the build so that it emits a server instead of finished pages, and at that point there is nothing static to upload. That is a deliberate choice somebody made in astro.config, so the fix is knowing whether it was made. The Astro deploy guide covers both cases. ## How it works 1. **Build the site.** Run the build you already run. A default Astro project needs no adapter and no extra configuration to produce publishable output. 2. **Upload dist.** Drag the dist folder or a ZIP of it in. Your pages, assets and any island scripts keep the paths the build gave them. 3. **Share the address.** The site is live on HTTPS in seconds, and republishing a new build keeps the same address. ## What you get ### Nothing to configure, which is the feature Most framework hosting pages exist because the framework needs coaxing into producing static output. Astro does not, so this page is mostly about the two ways a project stops being static. - A default Astro build writes finished pages to dist and needs no adapter. - An SSR adapter in astro.config changes that: the build emits a server, and there is nothing to upload. - Hybrid rendering has the same effect for the routes marked server-rendered. - The Astro deploy guide carries the command and the folder, and stays in step with the message a failed upload shows. ### Real pages, so real 404s Astro generates a file per route, which means the host can answer for each path properly instead of guessing. That is a genuine difference from a single-page app and it is worth not undoing. - Leave the Single-page app switch OFF. Astro sites have real files, and a fallback would serve the home page in place of a missing one. - A custom 404 page in your build is served as the 404, so a wrong link looks like your site rather than like a host. - Every page is separately cacheable, which is most of why an Astro site feels fast. ### The check that reads what you published Content sites get built from repositories, and repositories carry things that should not be public. Every publish is read and anything sensitive is named in plain language. - A committed .env file, a .git directory, a private key, or an API key left in a client-side script. - It runs after the site is live, never blocks a publish, and reports in sentences rather than as a score. - Included on the free plan. See how the security check works. ### A domain and an address that outlives the rebuild A content site accumulates inbound links, so the address has to be stable across every republish. It is, and from Pro it can be your own. - Republishing keeps the URL, so external links and search results keep resolving. - Certificates issued and renewed automatically on both the Droply address and yours. - Free sites are served noindex. Search visibility starts on Starter, which a content site will want from the beginning. ## What the free plan includes Everything below is on the free plan, with no card and no trial to run out, which is enough to put a built Astro site at a real address today. - 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. ## Compared with Static.app Static.app publishes the same kind of per-framework page, and neither product builds your project. These are the rows that differ for somebody holding an Astro dist folder. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits a month, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter, or $60 a year. Static.app: $5 a month or $60 a year for Starter: 2 sites, 500 MB, custom domain included. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its own documentation states a loose .html file must be zipped first. - **Custom 404 page from your build.** Droply: Served as the 404, because the site keeps its real file structure. Static.app: Not documented as a per-site setting. - **Rollback to a previous build.** Droply: One click from Pro, with every version kept. Static.app: Backups are offered as a separate feature rather than a per-publish version history. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted for upload and must be zipped first. Both products publish finished output rather than running your build, so the rows below compare what each one accepts and what it costs, not build speed. Product plans can change. ## When Droply is the wrong choice Astro is unusually honest about what it is doing, so the wrong-choice list here is short and specific. It is almost always about an adapter that somebody added, sometimes without noticing what it changed. - Your astro.config has an SSR adapter. The build then produces a server bundle, and there is nothing static in it to upload. - You use hybrid rendering with routes marked server-rendered. Those routes have no file behind them after the build. - You are using Astro Actions or server endpoints for form handling. Those need a runtime that this host does not provide. - 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. ## Frequently asked questions ### How do I host an Astro site? Run the build and upload the dist folder it creates. A default Astro project is static already, so there is no adapter to install and no export switch to set. Drag the folder in and it is live on HTTPS in seconds. ### Is Astro hosting free here? Yes. The free plan gives you 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included and no card required. ### Which folder does Astro build to? dist, in the project root. That folder holds finished HTML pages and their assets, and it is the one to upload. The Astro deploy guide has the command. ### Does Astro need an adapter to be hosted here? No, and adding one is what breaks it. Adapters exist to target a server runtime. The default static output is what a static host serves, so a project with no adapter is the easy case. ### Can I host an Astro site that uses server-side rendering? Not the server-rendered part. An SSR or hybrid build emits a server rather than finished pages, so those routes cannot be published here. Static routes in a hybrid build still are. ### Should I turn on the Single-page app switch for Astro? No. Astro generates a real file per route, so the host can answer each path correctly on its own. The switch exists for client-routed apps and would replace your 404 page with the home page. ### Does Droply run the Astro build for me? No. We publish finished files and never run your dependencies. Build locally or in the CI you already have, then upload dist. ### Will my Astro blog show up in Google? Only on a paid plan. Free sites are served with a noindex header on purpose, because free subdomains on a shared domain are the raw material for spam farms. Indexing starts on Starter. ### Can I use my own domain for an Astro site? Yes, from Pro at $15 a month. Point a domain you own at the site and it is served from your address, with HTTPS handled for you. ### What happens when I publish a new build? It becomes a new version at the same address, so inbound links and search results keep resolving. From Pro you can roll back to a previous build in one click. ## Related - [Vue Hosting](https://droply.host/vue-hosting) - [Next.js Hosting](https://droply.host/nextjs-hosting) - [Static Website Hosting](https://droply.host/static-website-hosting) --- Source: https://droply.host/pdf-to-link # Turn a PDF into a shareable link Go from PDF to link in one upload: drop the file and get a clean HTTPS address for it in seconds. Nothing to install, no viewer wrapped around it, and the same link keeps working after you replace the file. ## What does it mean to turn a PDF into a link? It means putting the file at a public web address, so that opening the URL opens the document. The alternative most people are used to, attaching the file or sharing it out of a cloud drive, gives the recipient a copy of the file or a viewer around it. A hosted link gives them the document itself, at an address you chose, that you can change the contents of later. The practical difference shows up in three places. Attachments get stripped by mail filters or bounce for size, and every recipient ends up with a separate copy that is out of date the moment you fix a typo. A drive link opens inside that drive's interface, sometimes behind an access request, and its URL is an opaque file identifier rather than anything readable. A hosted link is a normal web address that works in any browser, on any device, with nothing installed. The property that does the most work is that the address is separate from the file. Replace the PDF and the address is unchanged, which means a link in a printed brochure, an email signature, a QR code or a job application keeps pointing at the current version rather than at whatever you uploaded first. If you would rather people read the document in the page instead of in their PDF reader, see publishing a PDF as a web page. ## How it works 1. **Upload the PDF.** Drag the file onto the page. There is nothing to install, no template to complete and no conversion step in between. 2. **Pick the address.** Choose the subdomain so the link reads like the document. It is live over HTTPS in seconds, ready to send, post or embed. 3. **Replace the file, keep the link.** Upload a corrected version and it is published at the same address, so everyone who already has the link sees the new document. ## What you get ### It opens the document, not a viewer around it The link resolves to your PDF at your address. There is no branded shell, no sign-in prompt and no request-access screen between the reader and the file. - Opens in the browser built-in PDF reader on desktop and mobile. - The reader can still download or print it; nothing is locked. - No account needed by whoever you send it to. ### One address, many revisions Documents get corrected. Because the address belongs to the site rather than to a file, a correction does not invalidate anything you already sent. - Upload the new PDF and it replaces what the address serves. - Printed material, QR codes and email signatures keep resolving. - From Pro, returning to a previous revision is one click. ### Control over who reads it Some documents are meant to be public and some are meant to be reachable only by the people you sent them to. Both are supported explicitly rather than by obscurity. - Password protection from Starter, checked at the edge before the file is served. - Expiring links from Starter: six hours, a day, a week, a month, or a date. - Free sites are served noindex, so a document does not turn up in search results. ### Your own domain, when the link is the brand A price list sent by a company reads differently at a shared subdomain than at that company's address. - Connect a domain you own from Pro, $15 a month. - Certificates are issued and renewed for you, on your domain as well as ours. - DNS guides for the common registrars. ## What the free plan includes Everything below is on the free plan, with no card and nothing to claim after you publish. - 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. - PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. Paid tiers raise every limit. - A downloadable QR code for the link, so it can go on something printed. ## Compared with Google Drive link Almost nobody arrives here choosing between static hosts. The real comparison is with the drive link you would otherwise paste, so these rows describe how the two behave rather than what anyone charges. - **What the address looks like.** Droply: A subdomain you choose, so the link can read like the document. Google Drive link: An opaque file identifier you cannot choose. - **What opens.** Droply: The PDF itself, in the browser reader. Google Drive link: The drive viewer, wrapped in its own interface. - **Recipient needs an account.** Droply: No. Google Drive link: Not on an anyone-with-the-link share. On a restricted one, yes. - **Replacing the file.** Droply: Upload a new version; the address is unchanged. Google Drive link: Manage versions, then Upload new version, keeps the link. Uploading it as a new file does not. - **Your own domain.** Droply: From Pro, $15 a month. Google Drive link: Not available for a share link. - **Password on the document.** Droply: From Starter, one shared password checked at the edge. Google Drive link: No shared password. Access is per Google account, so everyone you want in needs one. - **Expiring access.** Droply: From Starter: 6 hours, a day, a week, a month, or a date you pick. Google Drive link: An expiry date can be set per person, and only on work or school accounts. It is not available on an anyone-with-the-link share. - **Search engines.** Droply: Free sites are noindex; indexing from Starter if you want the document found. Google Drive link: Not designed to be indexed. Google Drive rows checked 8 September 2026 against Google's own Drive help pages: managing versions (Manage versions, then Upload new version; a version may be deleted after 30 days or once there are 100 newer ones unless you choose Keep forever), sharing and expiration (an expiry date is set per person, under the options for work or school accounts, not on an anyone-with-the-link share), and the You need access screen a person sees without permission. The rows describe how each approach behaves rather than what anyone charges. Product behaviour can change. ## When Droply is the wrong choice Hosting a PDF is a publishing step. It does not manage the document, and there are cases where a drive or a document platform is the better answer. - Several people need to edit the source document and see each other's changes. That is a collaboration tool, not a hosted file. - You need per-person access control, revocation and a log of who opened it. One shared password is the level of control available here. - The document is confidential in a regulated sense. A hosted URL is reachable by anyone who has it unless you add a password. - 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. ## Frequently asked questions ### How do I turn a PDF into a link? Drop the PDF on the uploader, pick a name for the address and publish. The file is live at its own HTTPS link in seconds, with nothing to install at either end. ### Is hosting a PDF free? Yes. The free plan publishes 1 PDF to its own HTTPS link, with no card. PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. Paid tiers raise it along with storage. ### How large can the PDF be? PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. The pricing page lists the limit for every tier, and paid tiers raise it substantially. ### Is the link secure? It is served over HTTPS with a valid certificate, so the connection is encrypted and the browser shows a padlock. Anyone with the address can open it unless you add password protection, which is available from Starter. ### Can I update the PDF and keep the same link? Yes. Upload the corrected file and it is published at the same address, so everyone who already has the link sees the new version without you resending anything. ### Can I use my own domain? Yes, from Pro at $15 a month. Point a domain you own at the site and the PDF is served from your address instead of a Droply subdomain. ### Can I stop people finding the PDF in Google? Free sites are served with a noindex header, so they are not listed. On paid plans indexing is allowed, so if a document must stay out of search either keep it on a free site or add a password. ### Can the link expire automatically? Yes, from Starter. Set it to lapse after six hours, a day, a week, a month, or on a date you choose. It flips to an expired page rather than breaking, and you can restore it. ### Do people need an account to open it? No. They open a normal web address in any browser. An account is only needed by the person publishing the file. ### Can I get a QR code for the PDF? Yes. Publish the PDF first, then download a QR code for its address from your dashboard. QR codes are included on every plan, including the free one. See PDF to QR code for the whole flow. ## Related - [PDF to Website](https://droply.host/pdf-to-website) - [PDF to QR Code](https://droply.host/pdf-to-qr-code) - [Resume to Link](https://droply.host/resume-to-link) --- Source: https://droply.host/pdf-to-website # Turn a PDF into a website page Turn a PDF into a website page at its own address, where it opens in the browser page by page, with no download step in the way. Useful when the document is the content and you want people reading it rather than filing it. ## Can a PDF be a website? It can behave like one. Publishing a PDF at its own address means a visitor opens a URL and reads the document in their browser, scrolling through it the way they would scroll a page. What it does not do is convert your document into HTML: the pages are still PDF pages, laid out exactly as you designed them. That distinction decides whether this is the right tool. If the value of the document is its layout, a brochure, a menu, a report with charts, a zine, a set of plans, then keeping it as a PDF is the point, and the browser reader is a perfectly good reading surface. If the value is the text, and you want it to reflow on a phone, be selectable by a screen reader and be indexed properly, then the document should be rebuilt as HTML. Neither answer is universally right. There is a middle path worth knowing about. If you want an actual web page but do not want to hand-write one, the AI page builder writes and publishes a real HTML page from a description, and a hand-built page can be uploaded as a single HTML file. If you only want the address and do not care about the reading experience, PDF to link is the simpler page. ## How it works 1. **Upload the PDF.** Drop the file and pick a name. Nothing is converted, re-flowed or rebuilt: the document you uploaded is the document people read. 2. **It opens in the browser.** The address opens the document in the browser reader, so a visitor scrolls through it on the page instead of downloading and opening a separate application. 3. **Share one address.** Send the link, put it in a listing or behind a QR code. Replace the file later and the address keeps pointing at the current version. ## What you get ### Reading starts immediately The gap between a link and a read is where most documents are lost. Opening in place removes the download, the file manager and the second application. - Uses the browser built-in PDF reader, on desktop and mobile. - Zoom, search and page navigation are the ones the reader already knows. - A download is still one action away for anyone who wants the file. ### The layout survives Converting a designed document to HTML is where typography, columns and figure placement go wrong. Nothing is converted here. - Fonts, columns, tables and images are exactly as you exported them. - Nothing is re-flowed, re-compressed or reordered. - What you proofed is what a reader sees. ### Revisions do not break the link A published document is usually version two of something. The address belongs to the site, not to the file you first uploaded. - Upload a corrected PDF and it replaces what the address serves. - Existing links, printed references and QR codes keep working. - From Pro, returning to an earlier revision is one click. ### Decide who gets to read it Publishing does not have to mean publishing to everyone, and the controls are explicit rather than relying on an unguessable address. - Password protection from Starter, enforced before any file is served. - Expiring links from Starter for anything time-limited. - Free sites are noindex; search visibility starts on Starter. ## What the free plan includes The free plan publishes one document with no card. It is worth checking the upload limit before you start. - 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. - PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. - A downloadable QR code for the link, so it can go on something printed. ## Compared with Google Drive link The realistic alternative is pasting a drive link and hoping the recipient gets through to the document. These rows are about the reading experience rather than about price. - **What the reader sees first.** Droply: The document, in the browser reader. Google Drive link: The drive viewer and its interface around the document. - **Address.** Droply: A subdomain you choose, or your own domain from Pro. Google Drive link: An opaque file identifier. - **Risk of an access screen.** Droply: None. The link is public unless you add a password. Google Drive link: A restricted share shows a You need access screen with a Request access button instead of the file. - **Replacing the file.** Droply: Upload a new version; the address is unchanged. Google Drive link: Manage versions, then Upload new version, keeps the link. Uploading it as a new file does not. - **Password on the document.** Droply: From Starter, one shared password checked at the edge. Google Drive link: No shared password. Access is per Google account, so everyone you want in needs one. - **Search visibility if you want it.** Droply: Indexable from Starter; free sites are noindex. Google Drive link: Not designed to be indexed. - **QR code for print.** Droply: Generated for the address, included on every plan, including the free one. Google Drive link: Needs a separate QR tool pointed at the drive URL. - **Old versions.** Droply: Kept per upload; restoring one is a click from Pro. Google Drive link: Kept, but a version may be deleted after 30 days or once there are 100 newer ones unless you choose Keep forever. Google Drive rows checked 8 September 2026 against Google's own Drive help pages: managing versions (Manage versions, then Upload new version; a version may be deleted after 30 days or once there are 100 newer ones unless you choose Keep forever), sharing and expiration (an expiry date is set per person, under the options for work or school accounts, not on an anyone-with-the-link share), and the You need access screen a person sees without permission. The rows describe how each approach behaves rather than what anyone charges. Product behaviour can change. ## When Droply is the wrong choice A published PDF is a document at an address, and there are readers for whom that is the wrong format no matter how convenient it is to publish. - The content must reflow on a phone and be fully accessible to screen readers. Rebuild it as HTML instead; a PDF is a fixed layout by design. - You want the text to rank in search for its own keywords. An HTML page competes far better than a PDF does. - You need analytics on which pages of the document were read. Only whether the address was opened is measurable here, from Pro. - 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. ## Frequently asked questions ### How does a PDF become a website? The file is published at its own address and opens in the browser when someone visits it. They read it page by page on the page itself, so it behaves like a website even though it is still a PDF. ### Is the PDF converted into HTML? No. The document is served as it is, which is why the layout, fonts and figures are preserved exactly. If you need reflowing text and full accessibility, the document should be rebuilt as HTML rather than published as a PDF. ### Do visitors have to download the file? No. It opens in the browser built-in reader, so reading starts immediately. Downloading is still available to anyone who wants a local copy. ### Does it work on phones? Yes. The link opens in any modern mobile browser and the document is readable with the usual pinch and scroll. Nothing is installed. ### Can I update the document without changing the link? Yes. Upload the new file and it is published at the same address, so existing links, printed references and QR codes keep pointing at the current version. ### How large can the PDF be? PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. Paid tiers raise every limit; the pricing page lists them. ### Can I use my own domain? Yes, from Pro at $15 a month. The document is then served from your address with the certificate handled for you. ### Will the PDF show up in search results? Not on the free plan, which is served noindex on purpose. Indexing is allowed from Starter, though an HTML page will generally rank better for the same content than a PDF will. ### Can I keep it private? Yes, from Starter. The password is checked at the edge before the file is served. You can also set the link to expire from Starter. ## Related - [PDF to Link](https://droply.host/pdf-to-link) - [Portfolio to Link](https://droply.host/portfolio-to-link) - [PDF to QR Code](https://droply.host/pdf-to-qr-code) --- Source: https://droply.host/pdf-to-qr-code # Turn a PDF into a QR code Getting from a PDF to a QR code is two steps: publish the PDF to a live address, then download a QR code for that address from your dashboard. Because the code points at the address rather than at the file, replacing the document never means reprinting anything. ## How does a QR code for a PDF work? A QR code is a printed encoding of a short piece of text, and for this purpose that text is a web address. It cannot contain a PDF, so the file has to live at an address first; the code then simply carries that address, and a phone camera turns it back into a link. This is why the order matters, and why any tool that offers to "convert a PDF into a QR code" in one step is really doing the same two things: it hosts the file somewhere, then encodes that URL. The part worth caring about is which address ends up inside the code, because once the code is printed, that address is fixed forever. A code pointing at an address you control is a code you can redirect by replacing the document. A code pointing at a third-party URL is a dependency on that service continuing to exist and continuing to serve that link for free. That is the whole argument for publishing the PDF at your own site first: the address becomes yours, and from Pro it can be on your own domain. ## How it works 1. **Publish the PDF.** Upload the document and publish it to an HTTPS address. That address, not the file, is what the QR code will encode. 2. **Download the QR code.** Open the site in your dashboard and download its QR code as an image. QR codes are included on every plan, including the free one. 3. **Print it anywhere.** Put the code on a flyer, a sign, a label or packaging. Anyone scanning it lands on the current version of the document. ## What you get ### The code outlives the document The expensive part of a QR code is the print run, so the code has to survive every revision of what it points at. Encoding an address you control is what makes that true. - Replace the PDF and every printed code keeps working. - No re-generating, re-approving or reprinting when a price or a date changes. - From Pro, you can go back to a previous document without touching the code. ### A code you can actually print A QR code that fails at small sizes or on a matte stock is worse than no code, because the failure happens in front of a customer. - Downloaded as a clean image that scales up for posters and signage. - Generated for the site address, so the code stays valid as long as the site does. - Included on every plan, including the free one; the pricing page shows what else comes with each tier. ### Your own domain behind the code Some scanners and some phones show the destination before opening it. What it reads matters when the code is on your packaging. - Connect a domain you own from Pro, $15 a month. - HTTPS is on either way, so a preview never shows an insecure warning. - DNS guides for the common registrars. ### Control what a scan reaches A printed code is scannable by anyone who walks past it, which is occasionally not what you want. - Password protection from Starter if the document is for a specific audience. - Expiring links from Starter for a seasonal or event-bound document. - Free sites are noindex, so the document is reachable by code but not listed in search. ## What the free plan includes Publishing the document is free. What the free plan gives you, in full: - 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. - A downloadable QR code for the link, so it can go on something printed. - PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. ## Compared with Drive link plus a QR generator The usual path is to upload the PDF to a drive and paste that link into a free QR generator. It works, and these are the places it costs you later. - **What the code encodes.** Droply: An address you own and control. Drive link plus a QR generator: A drive URL, or the generator's own redirect address. - **Changing the document after printing.** Droply: Upload a new PDF; every printed code still works. Drive link plus a QR generator: Only if you use Manage versions to replace the file in place. A fresh upload mints a new link and orphans the code. - **Dependency on a third party.** Droply: One account, one address; from Pro it is your own domain. Drive link plus a QR generator: Two services, and a generator that uses its own redirect can put the code behind a paywall or retire it. - **What a scanner preview shows.** Droply: Your subdomain, or your domain. Drive link plus a QR generator: A drive identifier, or the generator's domain. - **Password on the document.** Droply: From Starter, one shared password checked at the edge. Drive link plus a QR generator: No shared password. Access is per Google account, so everyone you want in needs one. - **Expiring the destination.** Droply: From Starter, with an expired page rather than a broken link. Drive link plus a QR generator: Drive expiry is per person and work-or-school only; a free static QR code cannot expire at all. - **Cost.** Droply: Publishing the PDF is free; QR codes are included on every plan, including the free one. Drive link plus a QR generator: Often free, sometimes with a tracked-code upsell. - **Tools that have to keep working.** Droply: One. Drive link plus a QR generator: Two. Google Drive rows checked 8 September 2026 against Google's own Drive help pages: managing versions (Manage versions, then Upload new version; a version may be deleted after 30 days or once there are 100 newer ones unless you choose Keep forever), sharing and expiration (an expiry date is set per person, under the options for work or school accounts, not on an anyone-with-the-link share), and the You need access screen a person sees without permission. The rows describe how each approach behaves rather than what anyone charges. Product behaviour can change. ## When Droply is the wrong choice This gives you one code for one address. If the requirement is more sophisticated than that, use a dedicated QR platform and point it here. - You need scan analytics: how many, when, and roughly where. Only site visits are measurable here, from Pro. - You want many codes, each retargetable to a different destination later, managed as a campaign. - You need branded or logo-embedded codes with custom colours and error-correction tuning. - 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. ## Frequently asked questions ### How do I make a QR code for a PDF? Publish the PDF to a live address first, then open the site in your dashboard and download its QR code. Publishing the document is free, and QR codes are included on every plan, including the free one. ### Why can't the QR code contain the PDF itself? A QR code encodes a short piece of text, not a file. Any tool that appears to do it in one step is hosting the file somewhere and then encoding that address, which is exactly the two steps described here. ### Where do I find the QR code? In your dashboard, on the site you published, after the PDF is live. It downloads as an image you can place in any design tool. ### If I update the PDF, does the QR code still work? Yes, and that is the reason for doing it this way. The code points at the address, not at a specific file, so uploading a replacement leaves every printed code valid. ### Can I print the QR code large? Yes. It downloads as a clean image that scales up for posters, signage and packaging without becoming blurry. ### Is the linked PDF secure? The address is served over HTTPS with a valid certificate. If the document should not be readable by everyone who scans the code, add password protection from Starter. ### Can the destination expire? Yes, from Starter. The link can lapse after six hours, a day, a week, a month, or on a date, and it shows an expired page rather than an error. You can restore it later. ### Can the code point at my own domain? Yes, from Pro at $15 a month. That also changes what a scanner shows in its preview, which matters when the code is on your own packaging. ### Can I track how many people scanned it? Not scans specifically. Visitor analytics from Pro tell you how often the address was opened, which is a close proxy but does not distinguish a scan from a click. ## Related - [QR Code Menu](https://droply.host/qr-code-menu) - [PDF to Link](https://droply.host/pdf-to-link) - [PDF to Website](https://droply.host/pdf-to-website) --- Source: https://droply.host/resume-to-link # How to create a link for your resume To create a link for your resume, upload it as a PDF, pick a name, and get one clean link for job applications, LinkedIn and email. Update the file later and the address stays the same, so every application you already sent shows the current version. ## What is a resume link, and why do applications ask for one? A resume link is a web address that opens your resume in a browser, with no download and no login. Applications and profiles ask for one because a link cannot arrive corrupted, cannot be blocked by an attachment filter, opens the same way on every device, and can be updated without anyone resending anything. It also removes a small but real risk. A PDF attachment passes through mail servers and applicant tracking systems that may strip it, rename it, flatten it or refuse it on size. A link is a URL in a form field: it either resolves or it does not, and you can check that yourself before you paste it. The part people underestimate is the update. Most job searches involve improving the resume several times, and every improvement makes every application already sent slightly out of date. When the address is fixed and the file behind it is not, a fix on Tuesday reaches an application sent last Thursday. That only works if the address never changes when you upload a new file, which is the behaviour this is built around. ## How it works 1. **Upload your resume PDF.** Drop the same PDF you already send. A ZIP of an HTML resume site works too. Nothing is reformatted: the link opens the exact file you uploaded. 2. **Pick a name for the link.** Choose the subdomain, usually your name, and publish. That short HTTPS address is the resume link you paste into applications and your profile. 3. **Share it, then keep it current.** Paste one link everywhere. When you improve the resume, re-upload it and the address stays the same, so applications already sent show the new version. ## What you get ### The link survives every edit This is the feature that matters most in a job search, and it is the one a file-sharing link usually gets wrong. - Re-upload the improved resume and it is published at the same address. - Applications sent weeks ago now show the current version. - From Pro, an earlier version can be restored if you preferred it. ### It opens like a document, not like a download A recruiter opening your link should be reading within a second, on whatever device is in their hand. - Opens in the browser reader on desktop and mobile. - No account, no sign-in, no access request between them and the file. - They can still download or print it. ### An address that reads like you The link is going into a form a person will look at. A readable subdomain is worth the ten seconds it takes to choose. - Pick the subdomain yourself, subject to availability. - From Pro, use a domain you own instead. - HTTPS from the first publish, so no browser warning appears. ### Public by default, private if you need it A resume link is meant to be openable, but a job search is not always something you want indexed. - Free sites are served noindex, so the document does not turn up in a search for your name. - Password protection from Starter if you want it gated. - You can unpublish at any time, and from Starter it can lapse on a date you choose. ## What the free plan includes Everything a resume link needs is on the free plan, with no card. A normal resume PDF is comfortably inside the limit. - 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. - PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. Either way it is far above a typical resume. ## Compared with Google Drive link Most people paste a Drive link, and it usually works. These are the differences a recruiter actually experiences. - **What the recruiter sees.** Droply: Your resume, in the browser reader. Google Drive link: The drive viewer wrapped around your resume. - **What the address reads like.** Droply: A subdomain you choose, usually your name. Google Drive link: A long opaque file identifier. - **Risk of an access screen.** Droply: None. The link is public unless you add a password. Google Drive link: A restricted share shows a You need access screen with a Request access button instead of the file. - **Updating the resume.** Droply: Upload the new file; the link is unchanged. Google Drive link: Manage versions, then Upload new version, keeps it. Uploading a new file does not. - **Keeping it out of search.** Droply: Free sites are served noindex. Google Drive link: Not designed to be indexed. - **Password on the document.** Droply: From Starter, one shared password checked at the edge. Google Drive link: No shared password. Access is per Google account, so everyone you want in needs one. - **Your own domain.** Droply: From Pro, $15 a month. Google Drive link: Not available. - **Cost for this use.** Droply: Free on the free plan. Google Drive link: Free within the drive storage allowance. Google Drive rows checked 8 September 2026 against Google's own Drive help pages: managing versions (Manage versions, then Upload new version; a version may be deleted after 30 days or once there are 100 newer ones unless you choose Keep forever), sharing and expiration (an expiry date is set per person, under the options for work or school accounts, not on an anyone-with-the-link share), and the You need access screen a person sees without permission. The rows describe how each approach behaves rather than what anyone charges. Product behaviour can change. ## When Droply is the wrong choice A resume link solves distribution, not the job search. Some things it is not. - You want a personal site with an about page, projects and writing. Upload that as a static site instead, or start from publishing a portfolio. - You want to know exactly who opened it and when. Analytics from Pro report visits, not identities. - Your resume contains a home address or a phone number you do not want public. Remove it, or gate the link with a password. - 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. ## Frequently asked questions ### How do I create a link for my resume? Three steps. Upload your resume as a PDF, or a ZIP of an HTML resume, pick a name for the link, and publish. You get a clean HTTPS address in seconds, and it keeps opening the latest file you upload. ### What is a resume link or CV URL? A web address that opens your resume directly in a browser, with no download and no login. Applications and profiles ask for one because a link never arrives corrupted, works on every device, and can be updated without resending anything. ### Is it free to create a resume link? Yes. The free plan publishes your resume at an HTTPS address with no card. PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. Either way that is far above a normal resume. ### Can I update my resume and keep the same link? Yes. Upload the new file and it is published in place. The address does not change, so recruiters who already have it see the current version the next time they open it. ### Should I just share a Google Drive link instead? You can, and many people do. The difference is what the recruiter sees: a drive link opens a viewer and may show a request-access screen if a permission is wrong, while a hosted link opens the document itself at an address that reads like your name. ### Will my resume show up when someone searches my name? Not on the free plan. Free sites are served with a noindex header, so search engines do not list them. If you want it findable, indexing is available from Starter. ### Can I keep my resume link private? Published links are public by default, which is normally what a resume link is for. Password protection is available from Starter, and you can unpublish at any time. ### Can I use an HTML resume instead of a PDF? Yes. Upload the .html file, or a ZIP of the folder if it has its own stylesheet and images, and it is served as a real web page. See HTML hosting for how the assets are handled. ### Can I use my own domain for the resume link? Yes, from Pro at $15 a month. Point a domain you own at the site and the resume is served from your address. ### What name should I use for the link? Your name is the usual choice, because it is what a recruiter reads before clicking. The subdomain is yours to pick, subject to availability, and from Pro the whole thing can move to a domain you own using the DNS guides. ## Related - [PDF to Link](https://droply.host/pdf-to-link) - [Portfolio to Link](https://droply.host/portfolio-to-link) - [PDF to QR Code](https://droply.host/pdf-to-qr-code) --- Source: https://droply.host/portfolio-to-link # Publish your portfolio to a link Go from portfolio to link without a host, a repository or a build step you have to keep working. Upload a static site, an HTML file or a ZIP and it is live at an HTTPS address in seconds. ## What does publishing a portfolio actually involve? Getting a folder of finished files onto a server that will serve them at a public address over HTTPS. That is all a portfolio site is once it has been built: HTML pages, a stylesheet, some scripts, and a lot of images. Everything else that gets attached to the phrase "publishing a site" is either a build step you run once or a deployment pipeline you do not need for something that changes four times a year. Which means the practical question is where your portfolio currently is. If it came out of a site builder or a design tool, you already have an export, usually a ZIP, and that is the upload. If you built it with a framework, run its build and upload the output folder; the deploy guides name the command and folder for 23 of them. If it is a set of images and a PDF case study, those publish directly too. The thing worth optimising is not the publish, it is the images. A portfolio is mostly photography or screenshots, and an uncompressed export can be several times the size of a well-exported one with no visible difference. That matters here because the free plan gives you 25 MB of storage, which is generous for a compressed portfolio and tight for an uncompressed one. ## How it works 1. **Upload the portfolio.** Drop a ZIP of your static site, a folder, or a single HTML file. The files are served exactly as you built them, with nothing recompressed or rearranged. 2. **Live in seconds.** No server to configure, no repository to connect and no build to run. The site is on its own HTTPS address as soon as the upload finishes. 3. **Move it to your domain.** From Pro the same site is served from a domain you own, with the certificate issued and renewed for you. ## What you get ### Whatever your portfolio was exported as Portfolios come out of a dozen different tools in a dozen different shapes. All of the common ones are accepted directly. - A ZIP or a folder from a site builder or design tool export. - A single HTML page, if that is genuinely all it is. - The build output of a framework project. See the deploy guides. - Images, video and PDF case studies alongside the site, 96 extensions in total. ### An address that is yours to keep A portfolio is a long-lived link. It goes on business cards, CVs, profile bios and applications, and it needs to still resolve in two years. - The free plan needs no card, and nothing has to be claimed after you publish. - From Pro at $15 a month, use a domain you own. - Certificates handled automatically on both. ### Updating it does not mean re-sharing it New work goes in, old work comes out, and nobody needs to be told about a new URL. - Upload a new export and it replaces what the address serves. - Up to 15 publishes a day on the free plan. - From Pro, an earlier version is one click away. ### Findable, or not, on purpose A portfolio usually wants to be found, and a work-in-progress usually does not. The default is the safe one. - Free sites are served noindex; indexing starts on Starter. - Visitor analytics from Pro, so you can tell whether an application link was opened. - Password protection from Starter for work that is not public yet. ## What the free plan includes A working portfolio runs on the free plan indefinitely. Search visibility is the one thing a portfolio usually wants that starts on a paid tier. - 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. ## Compared with Cloudflare Drop Cloudflare Drop launched in July 2026 and made drag a folder, get a URL free at a very large host. It is a good way to look at something quickly. These are the rows that matter for a portfolio, which is a link you keep. - **Is the link yours straight away?.** Droply: Yes. Publishing needs an account, so there is nothing to claim afterwards. Cloudflare Drop: No. The preview stays live for 60 minutes, then the deployment and its throwaway account both disappear unless claimed. - **Account needed to start.** Droply: Yes, before anything is published. Cloudflare Drop: No, but yes to keep the result. - **Single HTML file.** Droply: Accepted on its own. Cloudflare Drop: Documented as a folder or a zip. - **PDF and document hosting.** Droply: First class, with in-browser viewers and 96 accepted file types. Cloudflare Drop: Not a product feature. Static assets only: HTML, CSS, JavaScript, images and fonts. - **Per-file size and file count.** Droply: 25 MB per upload on free, higher on paid tiers. Cloudflare Drop: 25 MiB per file and 1,000 files per upload. - **Custom domain.** Droply: From Pro, $15 a month. Cloudflare Drop: Available once claimed into a free Cloudflare account, as a Cloudflare Pages project. - **Password protection.** Droply: From Starter, enforced at the edge. Cloudflare Drop: Sites are public by default; no password option is documented for Drop. - **Security check on deploy.** Droply: Every publish, every plan. Cloudflare Drop: Not offered. Cloudflare Drop details checked 8 September 2026 against Cloudflare's July 8, 2026 launch and the limits published with it: a 60-minute preview, 1,000 files per upload, 25 MiB per file, static assets only, and a claim into a free Cloudflare account to keep the site and add a custom domain. Product features can change. ## When Droply is the wrong choice This publishes a portfolio you already have. It is not a portfolio builder, and there are cases where you want one. - You do not have a site yet and do not want to build one. A portfolio platform with templates and an editor will get you further faster. - You want clients to be able to comment on individual pieces, or to buy prints. That needs an application, not static files. - The portfolio is mostly video at original quality. Bandwidth allowances apply, and the pricing page lists them per tier. - 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. ## Frequently asked questions ### How do I publish my portfolio? Export it as static files, zip them, and drop the archive on the uploader. It is served as a live site at its own HTTPS address in seconds, with no server or build step on our side. ### What can I upload? A ZIP of an exported site, a whole folder, or a single HTML file. Images, video and PDF case studies work alongside the site, 96 file extensions in total. ### Does it work with site builders and frameworks? Yes, as long as you upload the static export. A builder gives you a ZIP; a framework gives you an output folder after its build. The deploy guides name the command and folder for 23 frameworks. ### Is publishing a portfolio free? Yes: 1 site, 25 MB of storage and 5,000 visits a month, with no card. Note that free sites are served noindex, so a portfolio you want found needs a paid tier. ### Will my portfolio be found in Google? Only on a paid plan. Free sites carry a noindex header on purpose, to keep free subdomains worthless to spam farms. Indexing is enabled from Starter. ### Can I use my own domain? Yes, from Pro at $15 a month. Point a domain you own at the site and it is served from your address with HTTPS handled for you. ### How do I update my portfolio? Upload the new export and it is published at the same address, so the link on your CV and your profiles keeps working. From Pro you can also return to an earlier version. ### Is 25 MB enough for an image-heavy portfolio? For a well-compressed one, usually yes. Uncompressed exports from a design tool can be several times larger than they need to be with no visible difference, so it is worth exporting properly before you decide you need more storage. ### Can I keep part of it private? Password protection applies to a whole site, from Starter. For work that is not public yet, publish it as a separate site with its own password rather than trying to hide a page inside a public one. ## Related - [Resume to Link](https://droply.host/resume-to-link) - [Static Website Hosting](https://droply.host/static-website-hosting) - [Client Website Preview](https://droply.host/client-website-preview) --- Source: https://droply.host/qr-code-menu # Create a QR code menu A QR code menu is two things: your menu published as a PDF or a web page, and a QR code on the tables that points at it. Because the code points at an address you control, changing a price means uploading a file rather than reprinting every table card. ## What makes a QR code menu work in practice? One thing: the code has to point at an address you control, not at a file. A QR code cannot be edited after it is printed, so whatever address goes inside it is the address for the life of the table card. If that address serves whatever menu you last uploaded, prices can change on a Tuesday and nothing on the floor has to be touched. This is where the common setup quietly fails. Uploading the menu to a cloud drive and generating a code from that link works until the day someone uploads a new menu as a new file, which creates a new link and orphans every code in the room. It also fails if the free code generator you used routes through its own redirect and later decides that redirect is a paid feature. The other decision is PDF or web page. A PDF is faster to publish if you already have a designed menu, and it looks exactly like the printed one. A web page reads better on a phone, because a PDF made for A4 needs pinching and scrolling on a small screen. Both publish the same way and both get a code, so the honest answer is to use whichever you already have, and revisit it if guests complain about zooming. Publishing a PDF as a web page covers the first route. ## How it works 1. **Publish the menu.** Upload it as a PDF or as a web page and publish to an HTTPS address guests can open on any phone, with no app. 2. **Download the QR code.** Open the site in your dashboard and download its QR code as an image ready for table cards, windows and boards. Included on every plan, including the free one. 3. **Change the menu, not the cards.** Upload the new menu and every printed code keeps working, because the code encodes the address rather than the file. ## What you get ### Prices change without a reprint This is the entire economic case for a QR menu, and it only holds if the address behind the code is stable. - Upload a new menu and every printed code points at it immediately. - No re-generating, re-laminating or replacing table cards. - From Pro, you can put yesterday's menu back in one click. ### Guests need nothing but a camera A menu that requires an app, an account or a cookie banner is a menu people give up on and ask a member of staff about instead. - Modern phone cameras read QR codes natively; no app to install. - The menu opens in the phone browser over HTTPS, so no security warning appears. - No sign-in and no account, for guests or for staff. ### A code that prints properly A code is scanned in bad light, at an angle, on a laminated card. It has to be a clean image at the size you actually print. - Downloads as an image that scales up for table cards, windows and A-boards. - Generated for the site address, so it stays valid as long as the site does. - Included on every plan, including the free one, and publishing the menu itself is free. ### Your own address on the code Some phones show the destination before opening it, and a guest reading your venue name there is a small but real difference. - Connect a domain you own from Pro, $15 a month. - Or pick a readable subdomain for free. - DNS guides for the common registrars. ## What the free plan includes Hosting the menu is free. What the free plan gives a venue, in full: - 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. - A downloadable QR code for the link, so it can go on something printed. ## Compared with Drive link plus a QR generator Most venues upload the menu to a cloud drive and paste that link into a free QR generator. It costs nothing on day one. These are the places it costs something later. - **What the code encodes.** Droply: An address you own and control. Drive link plus a QR generator: A drive URL, or the generator's own redirect. - **Changing the menu after printing.** Droply: Upload a new file; every printed code still works. Drive link plus a QR generator: Only if you use Manage versions to replace the file in place. A fresh upload mints a new link. - **What a guest sees on opening.** Droply: The menu. Drive link plus a QR generator: The drive viewer, and a You need access screen if the share is restricted. - **Dependency on a third party.** Droply: One account, one address. Drive link plus a QR generator: Two services, either of which can change terms. - **Menu as a web page rather than a PDF.** Droply: Both supported the same way, both get a code. Drive link plus a QR generator: A drive is built around files, not pages. - **Cost.** Droply: Free to publish, and QR codes are included on every plan, including the free one. Drive link plus a QR generator: Usually free, with a tracked-code upsell. - **Rolling back a bad menu upload.** Droply: From Pro, one click. Drive link plus a QR generator: Restore a previous version, if it has not passed the 30-day or 100-version cutoff. - **Tools that have to keep working.** Droply: One. Drive link plus a QR generator: Two. Google Drive rows checked 8 September 2026 against Google's own Drive help pages: managing versions (Manage versions, then Upload new version; a version may be deleted after 30 days or once there are 100 newer ones unless you choose Keep forever), sharing and expiration (an expiry date is set per person, under the options for work or school accounts, not on an anyone-with-the-link share), and the You need access screen a person sees without permission. The rows describe how each approach behaves rather than what anyone charges. Product behaviour can change. ## When Droply is the wrong choice This publishes a menu and gives you a code for it. A venue that needs more than that should buy a system built for venues. - You want guests to order and pay from the menu. That is a point-of-sale integration, not a hosted document. - You need per-table codes so the kitchen knows where an order came from. Every table would need its own address here, which is not what this is for. - You want the menu to show live stock, sold-out items or allergen filtering. That needs an application behind it. - 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. ## Frequently asked questions ### How do I make a QR code menu? Publish the menu as a PDF or a web page to a live address, then open your dashboard and download the QR code for it. Print the code on your table cards. QR codes are included on every plan, including the free one. ### Can I update the menu without reprinting the codes? Yes, and it is the main reason to do it this way. The code points at the address, not at one file, so uploading a new menu leaves every printed code working. ### Where do I get the QR code? From your dashboard, on the site, after the menu is published. It downloads as an image ready to place in a design or print file. ### Do guests need an app to scan it? No. Modern phone cameras read QR codes natively, so a guest points the camera and taps the link. The menu opens in their browser with nothing installed. ### Should I use a PDF or a web page? A PDF is quickest if you already have a designed menu and looks exactly like the printed one. A web page reads better on a phone, because an A4 PDF needs pinching and scrolling. Both publish the same way and both get a code. ### Is it free? Publishing the menu is free, with no card. QR codes are included on every plan, including the free one, and the pricing page lists what each tier adds beyond that. ### Is the menu link secure? It is served over HTTPS with a valid certificate, so no phone shows a warning after a scan. A menu is normally meant to be public, but password protection is available from Starter if you need it. ### Can I have a different menu for lunch and dinner? Publish them as separate sites with separate codes, or publish one document containing both. There is no time-based switching built in. ### Can I tell how many people scanned the code? Not scans specifically, but visitor analytics from Pro report how often the menu address was opened, which is close enough for most venues. ## Related - [PDF to QR Code](https://droply.host/pdf-to-qr-code) - [PDF to Website](https://droply.host/pdf-to-website) - [PDF to Link](https://droply.host/pdf-to-link) # Hosting AI tool output --- Source: https://droply.host/v0-hosting # v0 hosting: put what v0 built at your own address v0 generates Next.js with React, TypeScript, Tailwind and shadcn/ui. That is a project, not a page, so one build has to happen before a static host can serve it. This page covers the export, the static-export setting Next.js needs, and the two things that break first. ## What v0 outputs A Next.js project. v0 builds applications with Next.js, React, TypeScript, Tailwind CSS and shadcn/ui, so what you export is source code with a package.json and a dependency list, not a page a browser can open. That matters more here than with most generators, because Next.js is a framework with a server in it. Its default build produces a server application, and a static host has nothing to run it with. The fix is a setting rather than a rewrite: Next.js has a static export mode that renders every page to plain HTML at build time and writes the result to an out folder. Set it, build, upload that folder, done. The Next.js deploy guide has the exact configuration line. There is one case where none of this applies. If you asked v0 for a single component and it gave you one file that imports nothing but React, save it as a .jsx and upload that on its own. It is transformed in the visitor browser at the published address, with no build and nothing installed. The moment a shadcn/ui import appears in the file, that path is closed and you are back to building the project, because those components live in your project rather than on a public CDN. ## Which of the two paths you are on Open what you exported. The answer is visible in about five seconds and everything else on this page follows from it. ### One file, no build You copied a single component out of v0 and it imports nothing but React. Save it as a .jsx or .tsx file and upload it. - React, the JSX runtime and a Tailwind runtime are served from our own edge, so the file runs as it is. - Nothing is installed and nothing you upload runs on our servers. We serve static files. - A @/components/ui/... import means this path is closed: those are shadcn/ui files that live in the project. - The single-file runtime is described in full here, including what it declines to do. ### A project, one build first You exported the whole thing and there is a package.json in it. Run the static export once, then upload the folder it writes. - Set output: 'export' in next.config.js, then run npm install and npm run build. - Upload the out folder, as a folder or zipped. Not the project folder, and not .next. - Route handlers, server actions and anything under app/api do not survive a static export. Next.js will tell you which ones at build time. - Full command and configuration in the Next.js deploy guide. ## Getting the code out of v0 v0 documents two ways off the platform. The GitHub route is the one its own docs describe in detail, and it is the one to use if the download ever gives you a repository containing only a README. 1. **Open the project in v0.** Not a single message in a chat: the project, so you get the whole file tree rather than the block that is currently on screen. 2. **Download the ZIP, or sync to GitHub.** Open the project menu and choose Download ZIP; the browser offers a Save As dialog where it supports one. v0 also has a bi-directional GitHub integration, which is the better route if you intend to keep changing the project in both places. 3. **Install and check it runs.** Run npm install, then npm run dev. If it does not run locally it will not run as a static build either, and finding that out now is cheaper. 4. **Switch Next.js to static export.** Add output: 'export' to next.config.js. Next.js then refuses to build any route it cannot render ahead of time, which is the fastest way to discover what in the generated app was server-side. 5. **Build, then upload the out folder.** Run npm run build and drop the out folder here. Pick a name and the page is live over HTTPS. Source: Stack from v0's own FAQ documentation at v0.app/docs/faqs, read 8 September 2026, which states that v0 builds with Next.js, React, TypeScript, Tailwind CSS and shadcn/ui, that you can export the code to work locally, and that it offers bi-directional GitHub integration. The Download ZIP label and its location are from v0's own changelog, also read 8 September 2026: the entry of 28 August 2026 states that Download ZIP shows a native Save As dialog where the browser supports it, and the entry of 19 June 2026 states that view-only members can download a chat's code as a ZIP from the project menu. Menu labels can change. ## What breaks, and why Four failures cover almost every v0 upload that does not work first time. The first two are specific to what v0 generates; the rest are true of any generated project. ### The build fails on a route that uses a server feature Why: v0 scaffolds Next.js applications, and Next.js applications often contain route handlers, server actions or dynamic rendering. A static export has no server to run any of it, so the build stops and names the route. Fix: Either delete the server-side route if it was scaffolding you never used, or accept that this part of the app is not static. Only the static half can be published here. The Next.js guide covers which features survive an export. ### A single .jsx you copied out of v0 renders blank or names a missing package Why: The component imports shadcn/ui, lucide-react or another package. Those are not fetched from a public CDN on your visitors' behalf, because that would run third-party code in their browser and hand that CDN their IP address. Fix: The live page lists the missing packages by name rather than rendering a blank screen. Export the whole project and build it instead: the imports resolve at build time, which is where they were meant to resolve. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Publishing a generated build costs nothing, which matters here more than elsewhere: most v0 projects are shown once and then regenerated. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has the deepest content in this category and a page for v0 of its own. The rows below are the ones its own pricing and documentation make checkable. - **A Next.js static export.** Droply: Upload the out folder as a folder or a ZIP. Static.app: Accepted as a ZIP of built output. - **Runs the build for you.** Droply: No. You build once locally and upload the result. Static.app: No. - **Client-side routing.** Droply: One free Single-page app switch, applied to the live site with no redeploy. Static.app: Not documented as a per-site setting. - **Password protection.** Droply: From Starter, enforced at the edge. Static.app: Not listed on any of its plans. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice Much of what v0 generates is a real application, and calling it a website does not make it static. Recognizing that before you upload is cheaper than discovering it afterwards. - Your v0 app uses server actions, route handlers or a database. Those need a runtime; the static export drops them and the features that depended on them stop working. - You want the project rebuilt every time you regenerate it in v0. There is no Git integration and no CI here: each version is a build you run and an upload you make. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### Can I host a v0 project without Vercel? Yes. Export the code, set Next.js to static export, run the build, and upload the out folder here. The result is a normal static site on an HTTPS address, with no account on the original platform involved. ### Does v0 give me the code? Yes. Download ZIP from the project menu gives you the files directly, and a bi-directional GitHub integration keeps a repository in sync with the project if you would rather work that way. Both are documented by v0 itself. ### What does v0 actually generate? Next.js applications built with React, TypeScript, Tailwind CSS and shadcn/ui, per v0's own documentation. That is a project with a package.json, not a single page. ### Do I have to run a build? For a project, yes, once, on your machine. For a single component file that imports nothing but React, no: save it as .jsx and upload it, and it is transformed in the visitor browser at the published address. ### Which folder do I upload? The out folder that a static Next.js export produces. Not the project folder and not .next. The Next.js deploy guide names the configuration line that produces it. ### Why does every page except the home page 404? Because the routes are resolved by JavaScript in the browser, and a static host asked for a path it has no file for answers 404 first. Turn on the Single-page app switch in the site settings and unknown paths are served the root index.html instead. It is free and applies without a redeploy. ### Will my shadcn/ui components work? Yes, after a build. They are source files inside your project, so the build compiles them in. They do not work in the single-file path, because there is no project for them to be compiled from. ### Can the published site call an API? Only an API that already exists somewhere else and allows browser requests under its own CORS rules. There is no server here, so anything v0 scaffolded under app/api does not run. ## Other AI tools - [bolt.new hosting](https://droply.host/bolt-new-hosting) - [Lovable hosting](https://droply.host/lovable-hosting) - [Cursor hosting](https://droply.host/cursor-hosting) --- Source: https://droply.host/bolt-new-hosting # bolt.new hosting: publish the build, keep the link bolt.new builds inside a browser sandbox, so the project is real but it lives somewhere you do not control. Getting it onto your own address means taking the code out, running its build once, and uploading the folder that comes out. This page covers all three. ## What bolt.new outputs A complete JavaScript project. bolt.new documents that it focuses on JavaScript-based web technologies, with Node.js on the backend and any JavaScript framework on the frontend, so what you get is source code and a package.json rather than a finished page. The part worth understanding is where that project has been living. bolt.new runs a development environment in the browser tab, which is why the preview appears instantly and why the terminal in the interface works. That environment is not a host: it is a workspace. When you close it, the preview URL is not a place your customers can visit for the next three years. Publishing means moving the built output somewhere that only serves files, which is what this is. Which build command applies depends on what bolt scaffolded for your prompt. Its own documentation does not name a default framework, so read the project rather than guessing: a vite.config.ts means npm run build into dist, a next.config.js means a Next.js build and a static-export setting, and an astro.config.mjs means Astro into dist. There is a guide per framework naming the exact command and folder for 23 of them. ## Which of the two paths you are on Almost every bolt.new project is on the second path. The first exists because sometimes you asked for one page and got one page. ### One file, no build The project is a single self-contained index.html with its CSS and JavaScript inline. Upload it and you are finished. - A self-contained .html page publishes exactly as written. - A single .jsx or .tsx that imports nothing but React works the same way, transformed in the visitor browser. - If the file references ./style.css or /src/main.js, it is not self-contained and you are on the other path. - Not sure? The HTML tester renders pasted markup so you can see what is missing before you upload. ### A project, one build first There is a package.json and a src folder. Install the dependencies, run the build, and upload the folder it writes. - Run npm install, then npm run build. - Vite writes to dist, which is what most bolt projects produce. - Upload that folder, or zip its contents with index.html at the top level. - Command and folder per framework in the deploy guides. ## Getting the code out of bolt.new bolt.new documents two routes out: a direct download, and a GitHub repository kept in sync. The download is fewer steps; the repository is worth it if you plan to keep editing in both places. 1. **Open the project you want to publish.** Use Code view to see the actual file tree rather than the preview. What is in that tree is what you are about to build. 2. **Export and download the project.** Click the project title in the top left of the screen, then Export, then Download. You get a zip. The alternative is connecting a GitHub repository, which bolt.new also documents and which keeps syncing after you leave. 3. **Unzip it and install.** Unzip the download, open a terminal in that folder and run npm install && npm run dev, which is what bolt.new's own instructions tell you to run. This is the first time the dependencies exist on your machine rather than in the browser sandbox. 4. **Read the config file to learn the build.** A vite.config.ts means Vite. A next.config.js means Next.js and a static export setting. Match it to the guide for that framework instead of assuming. 5. **Build, then upload the output folder.** Run npm run build and drop the folder it produced, usually dist. Pick a name and the site is live over HTTPS. Source: All of the above from bolt.new's own help centre at support.bolt.new, read 8 September 2026. The supported-technologies article states that Bolt focuses on JavaScript-based web technologies with Node.js for the backend and any JavaScript framework on the frontend. The projects-and-files article gives the download steps verbatim: open your project, click the project title in the top left, then Export, then Download, unzip the downloaded file, and run npm install && npm run dev; it also states the download is a zip so you can work on it outside Bolt in your own editor. The Git integration article describes connecting a GitHub repository to back up a project, sync commits automatically and work across branches. Interfaces can change. ## What breaks, and why The two below are specific to a project that grew up in a browser sandbox. The rest are true of any generated build. ### It worked in the bolt preview and the uploaded version is blank Why: The preview was running a dev server, which resolves imports on the fly and serves source files directly. A static host has no dev server. If you uploaded src or the project root instead of the build output, the browser is being handed TypeScript and bare module imports it cannot execute. Fix: Upload the folder the build wrote, usually dist. If you are not sure the build ran, check that the folder contains an index.html and an assets folder of hashed filenames. ### The app expects a backend that bolt was running for it Why: bolt.new supports Node.js on the backend, so a generated project can contain server code that ran happily in the sandbox. None of it runs on a static host, and the symptom is usually a form that posts into nothing or a fetch that 404s. Fix: The front end can still be published here. The backend has to live somewhere that executes code, and the page has to call it over HTTPS with CORS allowed. If the whole app is backend, this is the wrong kind of host and the honest answer is to say so. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Getting a bolt project onto a permanent address costs nothing, and the free plan is a plan rather than a trial that turns into an invoice. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a bolt.new page of its own, which makes the comparison checkable rather than rhetorical. These rows come from its published pricing and documentation. - **Build output as a folder.** Droply: Uploaded directly, no ZIP required. Static.app: Accepted as a ZIP of built output. - **Runs npm install for you.** Droply: No. You build once locally and upload the result. Static.app: No. - **Client-side routing.** Droply: One free Single-page app switch, applied to the live site with no redeploy. Static.app: Not documented as a per-site setting. - **Framework build guides.** Droply: 23, each naming the command and the output folder. Static.app: Nine framework pages. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice bolt.new will happily generate an application with a server in it, and that half of the project cannot be published on a static host by anyone. - The project has a Node.js backend, an auth flow or a database. Only the front end can be served here. - You cannot run the build locally. Nothing here builds it for you, and uploading source produces a page that is broken rather than one that is merely unstyled. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I host a bolt.new project? Export and download the project as a zip, unzip it, run npm install and npm run build, then upload the folder the build produced, usually dist. The site is live at an HTTPS address in seconds. ### Can I download my bolt.new project? Yes. Click the project title in the top left, then Export, then Download. Its own documentation describes this as downloading a zip so you can work on the project outside Bolt in your own code editor. ### Which folder do I upload? The one the build wrote. For a Vite project that is dist. Not src, and not the project root. If what you uploaded contains a package.json, you uploaded the wrong thing. ### Do I need to run the build myself? Yes, once, on your own machine. There is no build step here by design: nothing you upload is executed on our infrastructure, which is also why a published site cannot be made to run npm on your behalf. ### Why does every route except the home page 404? Because the router runs in the browser and a static host answers with a file or a 404 before your JavaScript loads. Turn on the Single-page app switch in the site settings; unknown paths are then served the root index.html. It is free and needs no redeploy. ### What about the backend bolt generated? It does not run here. This host serves files and executes nothing. The front end publishes fine and can call an API hosted elsewhere, provided that API allows browser requests. ### Can I keep the same link when I rebuild? Yes. The address belongs to the site, not to the upload, so republishing keeps it. From Pro you can also restore an earlier version when a rebuild makes things worse. ### What if I do not know which framework bolt used? Read the config file at the root of the project. vite.config.ts is Vite, next.config.js is Next.js, astro.config.mjs is Astro. The deploy guides then name the command and folder for it. ## Other AI tools - [Lovable hosting](https://droply.host/lovable-hosting) - [v0 hosting](https://droply.host/v0-hosting) - [Replit hosting](https://droply.host/replit-hosting) --- Source: https://droply.host/lovable-hosting # Lovable hosting: your own link for a Lovable build Lovable projects are Vite and React, they build with npm run build, and they write to dist. Lovable documents all three itself. What its docs do not cover is the setting a client-routed build needs on a static host, and that is the part this page exists for. ## What Lovable outputs A Vite and React project. Lovable's own deployment documentation states that its projects are built with Vite and React, that the build command is npm run build, that the output directory is dist, and that Node 22 is recommended. The same documentation says something more useful than any of those numbers: Lovable projects use client-side routing, with React Router and BrowserRouter. That single sentence predicts the most common complaint about hosting a Lovable build anywhere. The home page works, and every other route returns 404, because the routes are decided by JavaScript after the page loads and a static host answers the request before that happens. There is a free switch for it here and it is described further down. One more line from those docs is worth reading before you build rather than after: environment variables prefixed with VITE_ are embedded at build time, not runtime. That means whatever value was set when you ran the build is now inside the JavaScript you are about to publish, readable by anyone who opens the page. It is why the deploy-time security check on this side reads what you published and names any key it finds. ## Which of the two paths you are on For Lovable it is almost always the second. The first is here for the rare single-page export that has nothing around it. ### One file, no build You have a single self-contained HTML page, or a single React component file that imports nothing but React. - Drop the .html and it publishes exactly as written. - A lone .jsx or .tsx is transformed in the visitor browser, with React served from our own edge. - Any import of shadcn/ui, an icon set or a router closes this path. - The single-file runtime in full, including what it declines to render. ### A project, one build first The normal Lovable case. Sync the code out, install, build, and upload the dist folder. - Run npm install, then npm run build. Node 22 is what Lovable recommends. - Upload dist, as a folder or zipped with index.html at the top level. - Turn on the Single-page app switch afterwards, or every route but the first will 404. - Build details in the Vite deploy guide. ## Getting the code out of Lovable Lovable documents Git sync as the way to hold your own copy of the code: a GitHub or GitLab repository kept in two-way sync with the project. 1. **Connect Git sync.** Lovable documents syncing a project with GitHub or GitLab, keeping the code in your own repository with automatic two-way sync. That repository is the copy you build from. 2. **Clone the repository locally.** Run git clone, then npm install inside the folder. Node 22 is the version Lovable's deployment documentation recommends. 3. **Set any VITE_ variables before building.** Lovable documents that VITE_ variables are embedded at build time, not runtime. Setting one after the build has no effect, and any value you do set becomes part of the published JavaScript. 4. **Run the build.** Run npm run build. The documented output directory is dist. 5. **Upload dist and turn on the SPA switch.** Drop the dist folder here, then open the site settings and enable Single-page app. That is what makes React Router's routes resolve instead of 404. Source: Stack, build command, output directory, Node version, client-side routing and the VITE_ build-time behaviour are all from Lovable's own documentation at docs.lovable.dev, read 8 September 2026: the external deployment and hosting guide states the build command npm run build, output directory dist, Node 22 recommended, that Lovable projects use client-side routing with React Router and BrowserRouter, and that VITE_ variables are embedded at build time rather than runtime. Git sync behaviour is from its Git sync overview. Documentation can change. ## What breaks, and why The first one below is close to universal for Lovable, because it follows directly from what Lovable documents about its own projects. ### A Supabase project the app cannot reach any more Why: Lovable projects are commonly wired to Supabase, and the connection lives in build-time environment variables. Publish a build made with the wrong ones, or none, and the front end loads while every data call fails. Fix: Set the VITE_ variables before running the build, not after, then rebuild. Remember that whatever you set is readable in the published JavaScript: use the anon key that is designed to be public, never a service role key. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Publishing a Lovable build costs nothing, including the switch that makes its routing work, which is the one thing a free plan elsewhere tends not to give you. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a Lovable page of its own. These rows are the ones its published pricing and documentation make checkable. - **Client-side routing (React Router).** Droply: One free Single-page app switch, applied live with no redeploy. Static.app: Not documented as a per-site setting. - **The dist folder.** Droply: Uploaded directly as a folder, no ZIP required. Static.app: Accepted as a ZIP of built output. - **Custom domain.** Droply: From Pro, $15 a month. Static.app: Included in the $5 entry tier. - **Password protection.** Droply: From Starter, enforced at the edge. Static.app: Not listed on any of its plans. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice A Lovable app is often a real application with a backend attached, and the half that talks to a database is not something any static host can serve. - Your app depends on Supabase functions, server-side auth or anything that runs code. The front end publishes; that part does not. - You want the site rebuilt automatically whenever you prompt Lovable again. There is no Git integration and no CI here: each version is a build you run and an upload you make. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I host a Lovable site outside Lovable? Sync the project to GitHub or GitLab, clone it, run npm install and npm run build, then upload the dist folder here and turn on the Single-page app switch. Lovable documents the first three steps itself. ### What is the Lovable build command and output folder? npm run build, writing to dist, with Node 22 recommended. Those are Lovable's own documented values, not an assumption about Vite projects in general. ### Why do my Lovable routes 404 after publishing? Because Lovable projects use client-side routing with React Router and BrowserRouter, which its documentation states. A static host answers /about with a file or a 404 before your JavaScript runs. Turn on the Single-page app switch in the site settings and unknown paths are served the root index.html instead. ### Does the Single-page app switch cost anything? No. It is available on every plan including free, it is applied to the live site without a redeploy, and it is off by default because a multi-page site should return real 404s. ### What happens to my Supabase connection? Nothing about it changes, but the values have to be right at build time. Lovable documents that VITE_ variables are embedded at build time rather than runtime, so a build made without them ships without them. ### Is it safe to publish a build with my Supabase key in it? Only the anon key, which is designed to be public and to be governed by your row level security rules. A service role key in front-end code is readable by anyone who opens the page, and the deploy-time security check will name it if it finds one. ### Can I use my own domain? Yes, from Pro at $15 a month. The certificate is issued and renewed for you. On the free plan the site is served on a subdomain over HTTPS. ### Do I keep the same link when I rebuild? Yes. The address belongs to the site, so republishing keeps it and any link you already sent shows the current version. From Pro you can restore an earlier build. ## Other AI tools - [bolt.new hosting](https://droply.host/bolt-new-hosting) - [v0 hosting](https://droply.host/v0-hosting) - [Replit hosting](https://droply.host/replit-hosting) --- Source: https://droply.host/replit-hosting # Replit hosting: move the static output off the platform Replit is a workspace with its own deployments attached. If what you built is a static front end, you do not need the platform to keep serving it. Download the project as a zip, build it, and the output lives at your own address instead. ## What Replit outputs Whatever you built in it. Replit is a development workspace rather than a generator with one house stack, so the answer depends on your project: a single HTML page, a Vite front end, a Node server, or all three in one folder. That makes the first step a reading exercise rather than a build. Open the file tree and look for a package.json. If there is none and there is an index.html at the root, you are holding a finished static site and can upload it as it is. If there is one, read the scripts block: a build script means there is a build to run and an output folder to find. If there is a server file that listens on a port, that part of the project is not static and no file host will run it. The reason to move a static front end off the platform at all is what a workspace is for. It is an environment that keeps a session alive so you can work; a host is a thing that answers requests for the next three years without you thinking about it. Once the front end is built, it needs the second thing, and the second thing is cheaper and simpler than the first. ## Which of the two paths you are on Look for a package.json. That is the whole test, and it takes a few seconds. ### Already static, no build An index.html at the root with its CSS, JavaScript and images alongside it. Nothing to compile. - Zip the contents of the folder, with index.html at the top level of the archive. - Or upload the folder directly. Both are accepted. - A single self-contained .html page can be dropped on its own with nothing around it. - A single .jsx or .tsx works too, transformed in the visitor browser with no build. ### A project, one build first There is a package.json with a build script. Install, build, and upload the folder it writes. - Run npm install, then npm run build. - Vite writes to dist; other frameworks differ. Check the guide for yours. - Upload that folder, not the project root and not node_modules. - A server file that listens on a port does not run here. Only the built front end does. ## Getting the code out of Replit Replit documents a direct download, and a fallback for when a large project times out. Both are worth knowing before you need the second one. 1. **Open the project.** Open the workspace containing the files you want, not a fork or a template preview. 2. **Download as zip.** Replit documents selecting the three-dot menu at the top of the file tree and choosing Download as zip. Large projects can take a moment. 3. **If the download fails, zip it in the Shell.** Replit's documented fallback is to open a Shell, run zip -r project.zip ., then download project.zip from the file tree. 4. **Unzip and read the project.** No package.json and an index.html at the root means it is already static. A build script means one build to run first. 5. **Build if you need to, then upload.** Run the build, then drop the output folder here. Pick a name and it is live over HTTPS, at an address that does not depend on a workspace staying awake. Source: Download steps quoted from Replit's own documentation at docs.replit.com/help/projects-and-files, read 8 September 2026, which states: select the three-dot menu at the top of the file tree and choose Download as zip, and that if the download fails you can open a Shell and run zip -r project.zip . then download project.zip from the file tree. Interfaces can change. ## What breaks, and why A zip of a whole workspace is a different animal from a zip of a build, and the two failures below both come from that. ### The upload is enormous, or times out Why: A workspace zip contains node_modules, a .git history and every file you ever created in it. That is frequently hundreds of megabytes of things a visitor will never request. Fix: Upload the build output, not the workspace. If the project is already static, zip only the files the site needs: the HTML, the CSS, the JavaScript and the images. ### The app worked in Replit and does nothing here Why: Replit was running a server for it. If the project has a file that listens on a port, that is the half that made it work, and a static host runs no code at all. Fix: Publish the built front end here and host the server somewhere that executes code. If the project is mostly server, this is the wrong kind of host and it is better to know now. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Moving a finished front end off a workspace costs nothing here, and the free plan is a plan rather than a trial with a deadline. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a Replit page of its own. These rows come from its published pricing and documentation. - **A workspace ZIP.** Droply: Accepted, extracted in a sandbox, with the real bytes checked rather than the file names. Static.app: ZIP upload is the documented path. - **Upload a folder instead.** Droply: Yes, no archive required. Static.app: ZIP is the documented path. - **Client-side routing.** Droply: One free Single-page app switch, applied live with no redeploy. Static.app: Not documented as a per-site setting. - **Expiring links.** Droply: From Starter: six hours, a week, or a date you pick. Static.app: Not listed on any of its plans. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice Plenty of Replit projects are servers wearing a front end, and moving one here would publish the half that does not do the work. - The project listens on a port, holds a database or handles logins. None of that runs on a static host. - You want the workspace and the published site to stay in sync automatically. There is no Git integration here: each publish is an upload you make. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I download a project from Replit? Replit documents selecting the three-dot menu at the top of the file tree and choosing Download as zip. If that fails on a large project, its documented fallback is to open a Shell, run zip -r project.zip . and download the archive from the file tree. ### Can I host a Replit project somewhere else? The static part, yes. Download the project, run its build if it has one, and upload the output folder. Anything that listens on a port stays behind, because a static host runs no code. ### Do I upload the whole zip Replit gave me? Usually not. That archive contains node_modules and the git history, which no visitor will ever request. Upload the build output, or just the files the site actually needs. ### How do I know whether my project needs a build? Look for a package.json. No package.json and an index.html at the root means it is already static. A build script inside it means one build to run, and the deploy guides name the output folder for each framework. ### Why does every route except the home page 404? Because the routing happens in the browser and a static host answers with a file or a 404 first. Turn on the Single-page app switch in the site settings; unknown paths are then served the root index.html. It is free and applies without a redeploy. ### Does the published site stay up if I stop using Replit? Yes. Once the files are here they are served independently of anything on the original platform. That is the reason to move a finished front end at all. ### What happens to the secrets in my workspace? They should not travel with the upload. The deploy-time security check reads what you published and names a .env, a private key or an API key if it finds one, on every plan including free. ### Can I put the site on my own domain? Yes, from Pro at $15 a month, with the certificate issued and renewed for you. The free plan serves the site on a subdomain over HTTPS. ## Other AI tools - [bolt.new hosting](https://droply.host/bolt-new-hosting) - [Cursor hosting](https://droply.host/cursor-hosting) - [Lovable hosting](https://droply.host/lovable-hosting) --- Source: https://droply.host/chatgpt-hosting # ChatGPT hosting: turn the page it wrote into a real link ChatGPT usually answers with one self-contained HTML file. That is the easiest thing there is to publish: save it as index.html, drop it here, and it is live over HTTPS in seconds. No build, no ZIP, no account on anything else. ## What ChatGPT outputs A block of code in the conversation, and in the common case that block is one complete HTML page with its CSS and JavaScript written inline. A browser can already render it, which means publishing it is a copy rather than a conversion. The second most common shape is a React component: a function, some JSX, probably Tailwind classes. That normally needs a build, because browsers do not understand JSX. Here it does not. Save it as a .jsx or .tsx file and upload it on its own, and it is transformed in the visitor browser using React and a JSX runtime served from our own edge. Nothing is installed and nothing you upload runs on our servers. The third shape is the one to watch for. If the answer spans several files, or the code imports from ./components/Header or from a package you have never installed, it is a project rather than a page, and it needs its build run before any static host can serve it. The framework deploy guides name the command and output folder for 23 frameworks, and the difference is worth checking before you upload rather than after. ## Which of the two paths you are on Read the top of the code block. Imports decide this, and they decide it in about three seconds. ### One file, no build The usual case for a chat answer. Everything the page needs is in the block on screen. - Save the HTML as index.html and upload it. That file name is what makes it the page people land on. - A React component with no imports beyond React: save it as .jsx and upload that instead. - Tailwind classes are fine on both paths; a Tailwind runtime is served from our own edge. - Want to see it render first? The HTML tester takes pasted markup directly. ### Several files, one build first The answer described a project, or the code imports from other files you would have to create. - Create the project locally, install what it imports, and run its build. - Upload the folder the build produced, as a folder or zipped. - Guides for 23 frameworks, each naming the command and the folder. - Packages other than React are not fetched from a public CDN for your visitors, so this path is not optional when they appear. ## Getting the code out of ChatGPT Nothing here needs an export feature. The reliable route is the one that has always worked: copy the block, save it as a file, upload the file. 1. **Copy the code block.** Use the copy control on the block rather than selecting the text by hand, which tends to collect the surrounding prose along with it. 2. **Or download it from canvas.** When the code is in a canvas rather than a chat message, use the Download button in the top-right corner. A code canvas detects the language and saves the file with that language's extension, so an HTML canvas comes out as a .html file with nothing else to do. 3. **Save it as index.html.** Any text editor does this. The name matters: index.html is the file served at the root of the address, so a page named anything else will not be the one visitors see first. 4. **Check it opens locally.** Double-click the file. If it looks right in your own browser with no server running, it is self-contained and it will look right published. 5. **Upload it and pick a name.** Drop the file here, choose the subdomain, and the page is live over HTTPS. Re-upload later and the address does not change. Source: Canvas behaviour from OpenAI's own help centre, read 8 September 2026: its canvas article states that the Download button is in the top-right corner of the canvas and that a code canvas detects the language and exports it with the appropriate file extension, and its article on writing and code blocks states that code is placed in a block you can read, copy, edit, preview or run. The help centre refuses automated requests, so those articles were read through their published text rather than fetched directly; a human re-checking them should open them in a browser. Menu labels can change. ## What breaks, and why Chat-written pages fail in a small number of ways, and the first two below account for most of them. ### The page is live but completely unstyled Why: The markup references style.css or ./assets/app.js, files that existed in the conversation's imagination and nowhere else. You uploaded the HTML on its own, so those requests 404. Fix: Either ask for a single self-contained file with the CSS and JavaScript inline, or create the referenced files and upload the whole folder so the relative paths resolve. ### Nothing loads, and the file is called page.html or code.html Why: The file served at the root of an address is index.html. A single file with another name is published, but nobody visiting the address will be shown it. Fix: Rename the file to index.html and upload again. Same site, same address, one publish. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Publishing a page from a chat costs nothing, which is the right price for something you may replace in ten minutes. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a ChatGPT page of its own, and its documentation states its own constraints clearly, which makes this table checkable rather than rhetorical. - **A single file from a chat.** Droply: Dropped as it is, with nothing around it. Static.app: Must be zipped first, per its own Claude page. - **A React component from a chat.** Droply: Save as .jsx and upload; it runs at the published address. Static.app: Needs a self-contained HTML version first, per its own Claude page. - **Expiring links.** Droply: From Starter: six hours, a week, or a date you pick. Static.app: Not listed on any of its plans. - **Password protection.** Droply: From Starter, enforced at the edge. Static.app: Not listed on any of its plans. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice A chat will happily describe an application, and describing one is not the same as producing something a file host can serve. - The answer includes a server, an API route or a database schema. Only the static half can be published here. - The code imports packages you would have to install. They are not fetched from a public CDN for your visitors, so this needs a real build first. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I publish HTML that ChatGPT wrote? Copy the code block, save it as index.html, and upload the file. It is live over HTTPS in seconds. There is no build step and no archive to make. ### Can I paste the code instead of uploading a file? The upload takes a file, so save the markup first; any text editor does it in a few seconds. If you want to see how it renders before committing to it, the HTML tester takes pasted code directly. ### What if ChatGPT gave me a React component? Save it as a .jsx or .tsx file and upload that. It is transformed in the visitor browser at the published address, with React and a JSX runtime served from our own edge. No build and no npm install. ### Why does my page have no styling? The markup is referring to a CSS file that does not exist alongside it. Either ask for one self-contained file with the styles inline, or create the referenced files and upload the whole folder. ### Does the file have to be called index.html? For a single file, yes, if you want it served at the address itself. Any other name is published but is not the page a visitor sees when they open the link. ### What about packages the code imports? React and the JSX runtime are provided. Anything else is not fetched from a public CDN on your visitors' behalf, because that would run third-party code in their browser and leak their IP address to it. The live page names what is missing, and the fix is to build the project locally. ### Can the published page call an API? Only one that already exists somewhere else and allows requests from a browser under its own CORS rules. There is no server here and nothing you upload is executed on our infrastructure. ### Is there a key in my page I should worry about? Possibly, and the deploy-time security check will name it. Chat-written code is where hard-coded keys appear most often, and anything in front-end code is readable by whoever opens the page. ## Other AI tools - [Gemini hosting](https://droply.host/gemini-hosting) - [v0 hosting](https://droply.host/v0-hosting) - [Codex hosting](https://droply.host/codex-hosting) --- Source: https://droply.host/gemini-hosting # Gemini hosting: from Canvas to a link you own Gemini Canvas previews the web page it wrote, and its documented export options go to Docs, Slides and Colab. There is no documented HTML download, so the route out is Copy code, save the file, upload it. That takes about a minute and the result is yours. ## What Gemini outputs Code inside Canvas, with a preview beside it. Google's own Canvas documentation describes generating and previewing HTML and React code for web app prototypes, and asking for changes to see the preview update. What that documentation does not describe is a way to download the result as an HTML file. The export options it names go to Google's own tools: Export to Docs, Export to Slides, and Export to Colab for Python. For code the documented action is Copy code. So the honest route out of Canvas is a copy and a paste into a text editor, which takes about a minute and produces a file you own outright rather than a preview that lives inside a chat. Once that file exists the rest is ordinary. A self-contained HTML page publishes as it is. A React component saved as a .jsx file publishes without a build, transformed in the visitor browser using React and a JSX runtime served from our own edge. If the answer spanned several files or imported packages you would have to install, it is a project rather than a page, and it needs its build run first. ## Which of the two paths you are on The Canvas preview does not tell you this; the top of the code does. Read the imports. ### One file, no build A complete HTML page, or a React component that imports nothing but React. Either is a single file and a single upload. - Save the HTML as index.html. That name is what makes it the page the address serves. - Save a component as .jsx or .tsx and upload it on its own. - Tailwind classes work on both paths; a Tailwind runtime is served from our own edge. - The HTML tester renders pasted markup, which is a quick way to confirm the copy came out whole. ### Several files, one build first Canvas described a project, or the code imports from files and packages that are not in the block. - Create the project locally, install what it imports, and run its build. - Upload the folder the build produced, as a folder or zipped. - Guides for 23 frameworks, each naming the command and the folder. - Packages beyond React are not fetched from a public CDN for your visitors, so this path is not optional once they appear. ## Getting the code out of Gemini Canvas Google documents Copy code as the action for code in Canvas, and its documented exports go to Docs, Slides and Colab. These steps use the copy route, because it is the one the documentation actually describes for web code. 1. **Open the Canvas with your page in it.** Canvas is where the code and its preview sit side by side. The preview is not a hosted page; it is a rendering inside the product. 2. **Copy the code.** Google documents opening More at the top of the Canvas panel and choosing Copy code. Share and export options live under Share & export at the top right, and go to Docs, Slides or Colab rather than to a file. 3. **Paste it into a text editor and save as index.html.** The file name is not cosmetic. index.html is the file served at the root of the address; a page saved under any other name will not be the one visitors land on. 4. **Open the file locally to check the copy is whole.** A copy that stopped short is the most common problem with this route, and it shows up immediately: the page opens half-rendered or the console reports an unclosed tag. 5. **Upload it and pick a name.** Drop the file here, choose the subdomain, and the page is live over HTTPS at an address that does not depend on a Gemini share link. Source: Canvas behaviour from Google's own documentation at support.google.com/gemini/answer/16047321, read 8 September 2026, which documents Copy code at the top of the Canvas panel, Share & export at the top right with Export to Docs and Export to Slides, Export to Colab for Python, and generating and previewing HTML and React web app prototypes. That article documents no direct HTML file download. Product interfaces can change. ## What breaks, and why Because the route out of Canvas is a copy rather than a download, the first failure below is specific to this tool and worth checking before anything else. ### The published page is cut off halfway down Why: The copy did not take the whole document. This happens when text is selected by hand in the Canvas panel instead of using the documented Copy code action, and it is invisible until the page renders. Fix: Copy again with Copy code, then open the saved file locally before uploading. A page that ends mid-tag in your own browser will end mid-tag at the address too. ### It looked right in the Canvas preview and is broken once published Why: The preview renders inside Google's own environment, which is not the same as a plain browser opening a plain file. Anything the preview supplied for the code, rather than the code supplying for itself, is missing once the file stands alone. Fix: Open the saved file directly in your browser before uploading. What you see there is what the published address will serve, with no environment around it. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Turning a Canvas preview into a real address costs nothing, and the free plan is a plan rather than a trial with a countdown. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a Gemini page of its own. These rows come from what its published pricing and its own documentation state. - **A single file copied out of a chat.** Droply: Dropped as it is, with nothing around it. Static.app: Must be zipped first, per its own Claude page. - **A React component from a chat.** Droply: Save as .jsx and upload; it runs at the published address. Static.app: Needs a self-contained HTML version first, per its own Claude page. - **Import from a URL.** Droply: Site import copies up to 40 pages and 600 assets from any site you point it at. Static.app: Import from URL takes claude.ai and claude.site links. - **Expiring links.** Droply: From Starter: six hours, a week, or a date you pick. Static.app: Not listed on any of its plans. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice Canvas can describe an application as easily as it can write a page, and the two do not publish the same way. - The prototype needs a login, a database or anything that runs on a server. Only the static half of it can be published here. - The code imports packages you would have to install. They are not fetched from a public CDN for your visitors, so a real build has to happen first. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I publish a page Gemini made in Canvas? Copy the code out of Canvas, paste it into a text editor, save it as index.html, and upload the file. It is live over HTTPS in seconds with no build step. ### Can I download my Gemini Canvas page as an HTML file? Google's Canvas documentation does not describe one. It documents Copy code for code, and exports to Docs, Slides and Colab. So the route out is a copy and a save, which takes about a minute. ### Is the Canvas share link the same as hosting? No. A share link points into Google's product. A published page is a file at your own address, served over HTTPS, that anyone can open without an account. ### What if Gemini gave me a React component? Save it as a .jsx or .tsx file and upload that. It is transformed in the visitor browser at the published address, with React and a JSX runtime served from our own edge. No build and nothing installed. ### Why is my published page cut off? The copy did not take the whole document, which happens when the text is selected by hand rather than copied with the documented action. Copy it again and open the saved file locally before uploading. ### Does the file have to be called index.html? For a single file, yes, if you want it served at the address itself. Any other name is published but is not the page a visitor sees when they open the link. ### What about packages the code imports? React and the JSX runtime are provided. Anything else is not fetched from a public CDN on your visitors' behalf, because that would run third-party code in their browser and leak their IP address to it. The live page names what is missing. ### Can the page call an API? Only one that already exists elsewhere and allows browser requests under its own CORS rules. There is no server here, and any key written into the page is readable by anyone who opens it. ## Other AI tools - [ChatGPT hosting](https://droply.host/chatgpt-hosting) - [v0 hosting](https://droply.host/v0-hosting) - [Lovable hosting](https://droply.host/lovable-hosting) --- Source: https://droply.host/cursor-hosting # Cursor hosting: you built it, now put it somewhere Cursor is an editor, so there is no export step and no Cursor-shaped output. What you have is a project on your own machine. Build it, upload the folder that appears, and it is live at an HTTPS address without you configuring a deploy for it. ## What Cursor outputs Your project. Cursor is a code editor with an agent in it, not a generator with a house stack, so there is nothing Cursor-shaped about the result. Whatever framework you chose is the framework you have, and its build is the build that matters. That makes this page shorter in one respect and more useful in another. There is no export menu to describe, because the code never left your machine. What is worth writing down is the part people actually get wrong: which folder to upload. A build writes its output somewhere specific, and uploading the project folder instead produces a page that is broken rather than merely unstyled, because the browser is handed TypeScript and bare module imports it cannot execute. The other half of the answer is which projects cannot be published as files at all. If the agent scaffolded a Next.js app with route handlers, a Remix app, or anything with a server in it, only the static half can be served here. That is not a limitation of the upload; it is what static hosting is. The export guide lists which frameworks can be switched to a static build and how. ## Which of the two paths you are on Open the project. The presence of a build script is the whole question. ### Already static, no build A folder of HTML, CSS, JavaScript and images, with an index.html at the root. Plenty of things built in an editor are exactly this. - Upload the folder directly, or zip its contents with index.html at the top level. - A single self-contained page can be dropped on its own with nothing around it. - A single .jsx or .tsx works too, transformed in the visitor browser with no build. - Up to 25 MB per upload on the free plan, 25 MB across the account. ### A project, build it first There is a package.json with a build script. Run it, then upload the folder it wrote, not the one you ran it in. - Vite, Astro and Vue write to dist. - Create React App and Docusaurus write to build. - Next.js with a static export writes to out; Gatsby writes to public. - The deploy guides name the exact command and folder for 23 frameworks. ## From a Cursor project to a live address There is no export step, because there is nothing to export from. These are the five things between a finished project and a URL. 1. **Confirm the project is static.** Look for server code: route handlers, an API folder, anything that listens on a port. If the app needs it at runtime, that half cannot be published as files by anyone. 2. **Run the build.** Run npm install if you have not, then npm run build. Cursor's terminal is as good a place as any to do it. 3. **Find the output folder.** It is the folder the build just created, not the one you ran the command in. If it contains a package.json, it is the wrong folder. 4. **Upload it.** Drop the folder here, or zip its contents with index.html at the top level. Pick a name and the site is live over HTTPS. 5. **Turn on the SPA switch if the app routes in the browser.** React Router, Vue Router and their equivalents need unknown paths served the root index.html. The Single-page app switch in the site settings does that, on every plan, without a redeploy. Source: This page makes no claim about Cursor's menus, because publishing a project built in an editor does not involve any. The build commands and output folders above are the ones this site documents per framework in its own deploy guides, which read their advice from the same detector the upload pipeline uses, so a guide and a failed deploy cannot contradict each other. The one claim about Cursor itself, that it uses Open VSX rather than the Visual Studio Marketplace and that not every Marketplace extension is listed there, is from Cursor's own extensions documentation at cursor.com/docs/configuration/extensions. All read 8 September 2026. ## What breaks, and why Two of these are specific to publishing a project you built yourself rather than one a generator handed you. ### The uploaded site shows a directory listing, or raw code Why: You uploaded the project folder instead of the build output. The browser is being handed src/main.tsx and a package.json, neither of which is a web page. Fix: Run the build, then upload the folder it created. If what you uploaded contains a package.json, it is the wrong folder. The export guide lists the output folder per framework. ### It works on localhost and 404s everywhere once published Why: Your dev server rewrites unknown paths to the app automatically. A static host does not, because a multi-page site should return real 404s. So the routing that worked in development stops working the moment it is a set of files. Fix: Turn on the Single-page app switch in the site settings. It applies to the live site with no redeploy and costs nothing on any plan. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Nothing about publishing a build costs anything until you want a domain on it, which is the order those things should happen in. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a Cursor page of its own. These rows come from its published pricing and its own documentation. - **Upload a build folder.** Droply: Yes, directly, no archive required. Static.app: ZIP is the documented path. - **Public API and editor extension.** Droply: Both. The VS Code extension signs in with email and works on every plan; raw API tokens are a paid feature. Static.app: An API is listed among its features. - **Client-side routing.** Droply: One free Single-page app switch, applied live with no redeploy. Static.app: Not documented as a per-site setting. - **Rollback to an earlier build.** Droply: From Pro, one click. Static.app: Backups are listed as a feature page. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice Somebody working in Cursor is more likely than most readers to be building the kind of application this cannot host, so it is worth being blunt about it. - The app has API routes, server-side rendering on every request, or a database. Only the static half of it can be served here. - You want a deploy on every push. There is no Git integration and no CI: this is a place to put a build, not a pipeline to run one. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I deploy a project I built in Cursor? Run its build, then upload the folder the build produced. There is no repository to connect and no configuration to write; the upload is the deploy, and the site is live over HTTPS in seconds. ### Does Cursor have an export or deploy feature I should use instead? Cursor is an editor, so what you have is an ordinary project. This page makes no claim about its menus, because publishing a project built in an editor does not involve any. ### Which folder do I upload? The one the build wrote. Vite, Astro and Vue write to dist; Create React App and Docusaurus write to build; a static Next.js export writes to out; Gatsby writes to public. If the folder contains a package.json, it is the wrong one. ### Why does my app 404 on every route except the first? Because the router runs in the browser and a static host answers with a file or a 404 before your JavaScript loads. Turn on the Single-page app switch in the site settings; unknown paths are then served the root index.html. It is free and applies with no redeploy. ### Can I publish without opening a browser? Yes. There is a public API and a VS Code extension that signs in with your email and works on every plan including free. Raw API tokens are a paid feature; the extension sign-in is not. ### Does the VS Code extension work inside Cursor? Not from Cursor's extension search. Cursor documents that it uses the Open VSX registry rather than the Visual Studio Marketplace, and that not every Marketplace extension is listed on Open VSX; ours is published to the Marketplace. Uploading in the browser works from any editor, and the public API works from Cursor's terminal. ### What if my project needs a server? Then that part cannot be published here, and no static host can run it. The front end can still be served, and it can call an API hosted elsewhere provided that API allows browser requests. ### Can I roll back a bad build? From Pro, yes, in one click. Every publish is kept as its own version and the address points at whichever one is current. ## Other AI tools - [Codex hosting](https://droply.host/codex-hosting) - [v0 hosting](https://droply.host/v0-hosting) - [Replit hosting](https://droply.host/replit-hosting) --- Source: https://droply.host/codex-hosting # Codex hosting: publish what the agent built Codex works on a repository. A cloud task ends in a pull request, and the CLI and IDE extension change files on your own machine. Either way what you end up with is a branch, so publishing means building that branch and uploading the folder it produces. ## What Codex outputs Changes to a repository. OpenAI documents Codex as running in the cloud, in an open-source CLI, and in an IDE extension for VS Code, Cursor and other VS Code forks, with a cloud task ending in a pull request when the work is ready. So there is no artifact to download and no export flow to follow. What exists after a task is a branch, or a set of edits in your working tree. Publishing is therefore the ordinary thing: check out the branch, run the project's build, and upload the folder the build wrote. The agent is not really part of that question, which is why this page spends its time on the folder rather than on the agent. The part that is specific to an agent is worth stating plainly. A cloud task can touch a build configuration, a base path, or an environment file without your noticing, because you reviewed the feature rather than the plumbing. So the first publish after a Codex task deserves the same review as a merge: look at what the build produced, not only at what the diff said. ## Which of the two paths you are on Once the branch is checked out, this is the same question every project answers. ### Already static, no build The repository is a folder of HTML, CSS, JavaScript and images with an index.html at the root. No compilation involved. - Upload the folder directly, or zip its contents with index.html at the top level. - Exclude .git and any .env: neither belongs at a public address. - A single self-contained page can be dropped on its own. - Up to 25 MB per upload on the free plan, 25 MB across the account. ### A project, build the branch first There is a build script. Check out the branch, install, build, and upload what the build wrote. - Run git checkout on the branch, then npm install and npm run build. - Build the branch you actually want live, not whatever was last checked out. - Upload the output folder, not the repository root and not node_modules. - The deploy guides name the command and folder for 23 frameworks. ## From a Codex task to a live address Codex leaves you a branch rather than a build, so these steps start where its documentation stops. 1. **Get the branch onto your machine.** A cloud task can open a pull request when the work is ready; the CLI and IDE extension change files locally. Either way, check out the branch you want to publish. 2. **Read the diff for build and config changes.** Look specifically at package.json, the framework config and any .env file. Those are the changes a feature review tends to skim, and they are the ones that decide what the build produces. 3. **Install and build.** Run npm install, then npm run build. If the build fails here, it would have failed in a pipeline too, and finding out on your own machine is faster. 4. **Upload the output folder.** Drop the folder the build wrote. Not the repository, not node_modules, and never the .git folder. 5. **Check the published page against the task.** Open the live address and confirm the thing you asked for is on it. This is the review step a pull request cannot do for you. Source: Codex surfaces and outputs from OpenAI's own material, read 8 September 2026: the Codex upgrades announcement at openai.com states that the Codex CLI is open source and that the IDE extension brings the agent into VS Code, Cursor and other VS Code forks, and the Codex cloud documentation at developers.openai.com describes choosing an environment, describing the result you want, watching the task logs or letting it run in the background, asking for follow-up changes, and opening a pull request when the work is ready. Product surfaces can change. ## What breaks, and why The two below are the ones that come specifically from publishing a branch an agent wrote. ### The .git folder went up with the site Why: You uploaded the repository rather than the build output, and .git came with it. That directory contains your full history, which at a public address is readable by anyone who guesses the path. Fix: Upload the build output instead. The deploy-time security check flags a published .git folder explicitly, on every plan, because this is the mistake with the worst consequences. ### The build behaves differently from the task description Why: The agent changed something under the feature: a base path, a build script, an environment variable. The pull request was reviewed for what it was asked to do, and the plumbing went through unread. Fix: Diff the config files before building, and open the published page rather than trusting the diff. A page at an address is the only review that catches this class of change. ### Every route except the home page returns a 404 Why: The app routes in the browser, so /about exists only once JavaScript has run. A static host asked for /about looks for a file at that path, does not find one, and answers 404 before your code loads. Fix: Turn on the Single-page app switch in the site settings. Unknown paths are then served the root index.html and the client router takes over. Free on every plan, applied without a redeploy, and off by default because a multi-page site wants real 404s. ### The API keys the tool wrote into the code are now public Why: AI tools fill in the value they can see, and a key in front-end code is readable by anyone who opens the page. No host can fix that: a published page is public by definition. Fix: The deploy-time security check names the key it found. Rotate it, then move the call behind something that can hold a secret. Every plan, free included, and it never blocks the publish. ## What the free plan includes Publishing a branch to look at it costs nothing, which is what makes it worth doing for a change you are not sure about yet. - 1 live site on a real free plan, not a trial of a paid one, with HTTPS 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. - Up to 15 publishes a day, which is the number that matters when you are regenerating. - The Single-page app switch, so a client-routed build works without paying for anything. - The deploy-time security check, which 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. ## How this compares with the other host built for AI output Static.app has a Codex page of its own. These rows come from its published pricing and its own documentation. - **Upload a build folder.** Droply: Yes, directly, no archive required. Static.app: ZIP is the documented path. - **Expiring links for a review.** Droply: From Starter: six hours, a week, or a date you pick. Static.app: Not listed on any of its plans. - **Password protection.** Droply: From Starter, enforced at the edge. Static.app: Not listed on any of its plans. - **Rollback to an earlier build.** Droply: From Pro, one click. Static.app: Backups are listed as a feature page. - **Loose .html file accepted.** Droply: Yes, dropped on its own with nothing around it. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx without a build.** Droply: Yes. It is transformed in the visitor browser at the published address. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version first. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Security check on every publish.** Droply: Every plan, free included: leaked keys, a stray .env, a committed .git folder. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask the model for a self-contained HTML version, and that Import from URL takes claude.ai and claude.site links. Product plans can change. ## When Droply is the wrong choice Codex is used on real applications more often than on brochure sites, and most real applications are not static. - The branch changes an API, a server-rendered route or a database migration. None of that can be shown at a static address. - You want every pull request published automatically. There is no Git integration and no CI here: a publish is an upload or an API call you make. - The generated app has a database, a login screen or server actions. Those need a runtime; only the static half of it can be published here. - You want a build to run here, on upload or on every push. There is no build step and no Git integration: you build locally and bring the output. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### How do I publish what Codex built? Check out the branch, run the project build, and upload the folder the build produced. Codex leaves a branch rather than a finished site, so the publish starts where its own workflow ends. ### Where does Codex put the code? In your repository. OpenAI documents cloud tasks that open a pull request when the work is ready, plus an open-source CLI and an IDE extension for VS Code, Cursor and other VS Code forks, both of which change files locally. ### Which folder do I upload? The one the build wrote, never the repository root. Vite, Astro and Vue write to dist; Create React App and Docusaurus write to build; a static Next.js export writes to out; Gatsby writes to public. ### Can I publish a pull request for review? Yes, and it is one of the better uses of this. Build the branch, publish it, and share the link. From Starter you can set it to expire so the review link cleans itself up. ### What if I accidentally upload the whole repository? The deploy-time security check flags a published .git folder explicitly, because a public git history is the worst version of this mistake. Delete the site or republish with only the build output. ### Can I deploy from a script instead of a browser? Yes, through the public API, which is a paid feature, or the VS Code extension, which signs in with email and works on every plan including free. ### Why does the app 404 on every route but the first? Because the routing happens in the browser and a static host answers with a file or a 404 first. Turn on the Single-page app switch in the site settings; unknown paths are then served the root index.html, free on any plan and with no redeploy. ### What if the branch adds a server-side feature? That part cannot be published here. Only static files are served and nothing you upload is executed on our infrastructure. The front end can still go up and call an API hosted elsewhere. ### Is it free? Yes for 1 site: HTTPS, 25 MB of storage, 5,000 visits a month, no card. Custom domains start on Pro at $15 a month. ## Other AI tools - [Cursor hosting](https://droply.host/cursor-hosting) - [ChatGPT hosting](https://droply.host/chatgpt-hosting) - [v0 hosting](https://droply.host/v0-hosting) # Who it is for --- Source: https://droply.host/use-cases # Droply use cases, by audience and by artifact\ \ Two ways in. The audience guides start from the work somebody does and end at the file they need to publish. The workflow guides start from the file itself.\ \ ## By audience\ \ ### Make, test and launch\ \ Finished creative and technical work that needs to run in a real browser, not sit inside a handoff thread.\ \ - [Website Hosting for Designers](https://droply.host/for/designers): Portfolios, case studies, coded concepts and client previews that open as the finished work rather than as a download.\ - [Static Hosting for Developers](https://droply.host/for/developers): Built demos, prototypes, docs and reports at a stable URL, without creating a deployment pipeline for every short-lived project.\ - [Landing Page Hosting for Marketing Teams](https://droply.host/for/marketing): Campaign pages, media kits, one pagers and sales collateral that can go live without waiting for an engineering release.\ \ ### People, places and teams\ \ Pages and documents that move through messages, applications, listings and review rounds.\ \ - [Website Hosting for Real Estate Agents](https://droply.host/for/real-estate): Property pages, brochures, floor plans and photo sets behind one link that still works after the listing details change.\ - [Website Hosting for Recruiting Teams](https://droply.host/for/recruiting): Job pages, hiring packs, offer guides and onboarding resources that can be corrected behind the address already sent.\ \ ### Teaching and coursework\ \ Lessons, class resources and student projects that should open from one ordinary link on any device.\ \ - [Website Hosting for Educators](https://droply.host/for/educators): Lessons, readings, slides and class resources that open from one link without turning the learning material into a software project.\ - [Web Hosting for Students](https://droply.host/for/students): Coursework, portfolios, resumes and built web projects at a link an instructor or hiring manager can open in a normal browser.\ \ ### Run without a web team\ \ Menus, one-page sites, invitations and files for a small business that has work to do and no server to maintain.\ \ - [Website Hosting for Small Business](https://droply.host/for/small-business): Simple sites, menus, price lists, invitations and files for a business that needs a link rather than another technical system.\ \ ## By artifact\ \ ### Host a site\ \ - [Static Website Hosting](https://droply.host/static-website-hosting): Free static website hosting in seconds. Upload a ZIP or a folder of your finished site, get a secure public URL, and skip Git, server and build setup.\ - [HTML Hosting](https://droply.host/html-hosting): HTML hosting in seconds: upload an HTML file or a finished static site, get a secure public URL, and skip server, Git and build configuration.\ - [HTML to URL](https://droply.host/html-to-url): HTML to URL in seconds: save the markup as index.html, upload one file or a ZIP, and share a secure link that you can update in place afterwards.\ - [Host a Static Site from ZIP](https://droply.host/host-static-site-from-zip): Host a static site from a ZIP file in seconds. Upload your built HTML, CSS, JavaScript and assets together and get a secure public URL, with no pipeline.\ - [Static Hosting for Freelancers](https://droply.host/static-hosting-for-freelancers): Static hosting for freelancers: share finished client sites, prototypes and files from one clean secure link, with no Git, server or build setup.\ - [Client Website Preview](https://droply.host/client-website-preview): Create a client website preview link in seconds. Upload the build, send clients one secure URL, and replace it in place as their feedback arrives.\ - [Host an AI-Generated Website](https://droply.host/host-ai-generated-website): Host an AI-generated website in seconds. A single HTML or React file runs with no build; a full project needs one build first, and this page says which.\ - [Publish a Claude Artifact](https://droply.host/publish-claude-artifact): Publish a Claude artifact as a real website: upload the one .jsx, .tsx or HTML file and it runs at a secure HTTPS link in seconds. No build, no server.\ \ ### Host a framework project\ \ - [React Hosting](https://droply.host/react-hosting): React hosting in seconds: upload the build folder your bundler produced and get a secure public URL, with no Git remote and no deploy pipeline to set up.\ - [Vue Hosting](https://droply.host/vue-hosting): Vue hosting in seconds: upload the folder your Vue, Nuxt or VitePress build produced and get a secure public URL, with no Git remote or pipeline to set up.\ - [Angular Hosting](https://droply.host/angular-hosting): Angular hosting in seconds: upload the browser folder your ng build produced and get a secure public URL, with no Git remote or deploy pipeline to set up.\ - [Next.js Hosting](https://droply.host/nextjs-hosting): Next.js hosting for a static export: add output export, build, and upload the out folder for a secure public URL. An honest list of what the export loses.\ - [Astro Hosting](https://droply.host/astro-hosting): Astro hosting in seconds: run the build, upload the dist folder, and get a secure public URL with no adapter, no Git remote and no pipeline to configure.\ \ ### Share a document\ \ - [PDF to Link](https://droply.host/pdf-to-link): PDF to link in seconds: upload the file, get a clean shareable HTTPS address, and keep the same link working after you replace the document.\ - [PDF to Website](https://droply.host/pdf-to-website): PDF to website in one upload: the document gets its own URL and opens in the browser page by page, with no download step and free SSL on every link.\ - [PDF to QR Code](https://droply.host/pdf-to-qr-code): PDF to QR code in two steps: publish the file to a live HTTPS link, then download its QR code. Print it on flyers or signs and update the document later.\ - [Resume to Link](https://droply.host/resume-to-link): How to create a link for your resume in seconds: upload the PDF, pick a name, and get a clean HTTPS URL for applications, LinkedIn and email. Free plan.\ - [Portfolio to Link](https://droply.host/portfolio-to-link): Publish your portfolio to a link in seconds. Upload a static site, HTML or a ZIP and get a clean HTTPS URL with free SSL, no host or build step needed.\ - [QR Code Menu](https://droply.host/qr-code-menu): Create a QR code menu for a restaurant or cafe: host the menu as a PDF or a web page, get a QR code for the tables, and change prices without reprinting.\ --- Source: https://droply.host/for/designers # Website hosting for designers who want the work to open\ \ Publish a portfolio, coded concept, case study or client preview as a real page. Send one HTTPS link, update the work behind it, and let people judge the thing itself instead of an attachment.\ \ ## What designers actually send\ \ Website hosting for designers is a place to put finished visual work where a client, recruiter or collaborator can open it in the browser. The useful unit is not a hosting account. It is the portfolio, case study, prototype or review page that needs one dependable address.\ \ A design handoff often starts in one tool and ends somewhere else. The source may live in Figma, the case study may be exported as HTML, and the client may only need a PDF. Hosting is the last step that makes those artifacts easy to open. A portfolio link can present the finished collection, while a client website preview lets a reviewer click the real build on their own screen.\ \ That distinction matters for coded work. A screenshot proves how one frame looked on one machine. A hosted build proves whether the menu opens, the type loads, the layout fits a phone and the links go where they should. If all you have is raw markup, the HTML to URL flow can publish pasted code without making a file first. If assets sit beside the page, upload the folder or ZIP intact.\ \ - **Portfolio.** A selected body of work with enough context for a client, hiring manager or collaborator to understand your role.\ - **Case study.** A project narrative with the problem, the decisions, the result and the images that support it.\ - **Client preview.** The current HTML build at a stable review address, replaced as feedback turns into revisions.\ - **Coded concept.** A motion study, interaction idea or small interface that has to be clicked rather than described.\ - **Presentation or PDF.** A deck, proposal, style guide or design rationale that should open without a request-access screen.\ - **Asset collection.** Images, media and supporting pages kept together under one project address instead of scattered across a message.\ \ ## Four design workflows, one last step\ \ The file changes with the discipline. The handoff problem is the same: somebody outside your machine needs to see the current version.\ \ - **Freelance designers.** Turn selected work into a portfolio link that opens directly and can keep the same address after an edit.\ - **Web designers.** Put the built pages behind a client preview link so feedback is based on the real responsive result.\ - **Product designers.** Publish a coded interaction or use the HTML paste flow when an experiment exists as markup rather than a project.\ - **Studios and agencies.** Keep previews separate by client and update each one without changing the review link already in the project record.\ \ ## What you get\ \ ### A browser is the review surface\ \ The reviewer sees the delivered page on the device they actually use. That reveals responsive behavior, font loading, motion and link states that a still image cannot carry.\ \ - A single HTML file can be uploaded on its own, with no ZIP when it is self-contained.\ - A built multi-page site keeps its relative CSS, image, font and script paths.\ - PDFs and images open as first-class files when a website would add no value.\ \ ### The review link survives revisions\ \ Design work changes after it is shared. Each upload is a new deployment behind the same address, so the thread, ticket and calendar invite do not become a trail of obsolete links.\ \ - Publish up to 15 times a day on the free plan.\ - Rollback starts on Pro when a previous version needs to come back.\ - The deploy-time security check runs on every version, including free ones.\ \ ### Control the unfinished work\ \ A preview can be shareable without being ready for search. Free sites are noindex, and paid controls cover the cases where an address should be limited to the people in the review.\ \ - Password protection starts on Starter and covers the page plus its assets.\ - Expiring links start on Starter for a review that should close on schedule.\ - A custom domain starts on Pro, with the certificate handled for you.\ \ ### Use the format the work already has\ \ There is no reason to rebuild a PDF as a site or flatten an interactive page into a PDF. Choose the artifact that communicates the work and host that artifact directly.\ \ - Use PDF to link for proposals, decks and style guides.\ - Use ZIP hosting for a built site with asset folders.\ - Use HTML hosting for a page you already exported.\ \ ## What the free plan includes\ \ The free plan is enough to put one current portfolio or review page online without entering a card.\ \ - 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.\ - The same address after an update, so a reviewer does not need a replacement link.\ \ ## Use each link for the job it is good at\ \ Figma is the better place to inspect source design, leave comments and collaborate on frames. A hosted link is the better handoff when the deliverable is already HTML, a static site or a document and the reader should see that result without the editor around it.\ \ - **What opens.** Droply: The finished HTML, static site, PDF or image you published. Shared Figma link: A Figma file or prototype, governed by that file's sharing permissions.\ - **Comments and source inspection.** Droply: No built-in design comments or layer inspection. Shared Figma link: View access can include inspection and commenting, which is better for collaborative design review.\ - **Prototype-only handoff.** Droply: The hosted output is already the whole thing being shared. Shared Figma link: Prototype-only links are documented as a paid-plan feature; Starter viewers can still open the source file from presentation view.\ - **Password.** Droply: Available from Starter, checked before any file is served. Shared Figma link: Available on Figma paid plans for files and prototypes.\ - **Link expiry.** Droply: Available from Starter, with preset durations or a date. Shared Figma link: Figma documents link expiration for Enterprise plans.\ - **Best fit.** Droply: A finished artifact that should look and behave like the deliverable. Shared Figma link: Design collaboration, comments, permissions and prototype presentation.\ \ Figma rows checked 8 September 2026 against Figma's file and prototype sharing guide and its password protection guide. Product plans and sharing controls can change.\ \ ## When Droply is the wrong choice\ \ Use the design tool, client portal or development platform when the work still needs the capabilities of that tool. Hosting is the presentation and delivery layer, not a replacement for the place where the work is made.\ \ - You need clients to comment on frames, inspect layers or branch the source design. Keep that review in Figma or the design system.\ - You need a server-backed form, account area, product database or checkout. A static page can link to those services, but cannot provide them itself.\ - You want the platform to turn a Figma file into production HTML automatically. Upload an export or a finished build; Droply does not generate code from a design file.\ - 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.\ \ ## Frequently asked questions\ \ ### What is the best website hosting for a designer portfolio? Use hosting that accepts the format you already made and gives it a stable HTTPS address. A static HTML portfolio can be uploaded as a file or ZIP here, while a PDF portfolio can use the portfolio link flow without being rebuilt as a site. ### Can I host a single HTML portfolio without a ZIP? Yes. A self-contained .html file can be dropped on its own. If the page refers to separate images, styles or fonts, upload the folder or a ZIP so those relative paths remain intact. ### Can I share a design with a client before it is finished? Yes. Publish the current build and send the link as a client preview. Free sites are noindex, and password protection is available from Starter when the address itself is not enough control. ### Does the link change when I upload a revision? No. A replacement creates a new deployment behind the same site address. The client can refresh the link already in the thread and see the current version. ### Can I use my own portfolio domain? Yes, from Pro. Point the domain at the provided target, complete verification, and the certificate is issued and renewed automatically. ### Can I password protect a design presentation? Yes, from Starter. The password gate runs before the page and any supporting files are served, so copying an image or script address does not bypass it. ### Should I replace my Figma link with a hosted link? Only when you are sharing the finished result. Keep Figma for comments, source inspection and prototype collaboration; use a hosted link when the recipient should open the exported site, page or document itself. ### Can Droply turn my Figma file into a website? No. Export or build the website first, then publish the finished output. If another tool gave you HTML code, paste the HTML and publish that instead. ### Will my free portfolio appear in Google? No. Free sites are served noindex by design. Search indexing starts on Starter, which is the right tier to consider when organic discovery is part of the portfolio's job. ### What happens if I publish a private key or .env file by mistake? Every deployment receives a security check that warns about a published .env file, .git folder, private key or API key pattern. Treat a warning as an incident and rotate any exposed secret; the check cannot make a public secret safe again.\ \ ## Other audiences\ \ - [Static Hosting for Developers](https://droply.host/for/developers)\ - [Landing Page Hosting for Marketing Teams](https://droply.host/for/marketing)\ - [Website Hosting for Small Business](https://droply.host/for/small-business) --- Source: https://droply.host/for/developers # Static hosting for developers with a finished build\ \ Put a prototype, docs build, demo or generated report online without adding a repository integration to a project that may only need one review round. Build locally, upload the output, share the URL.\ \ ## What developers actually send\ \ Static hosting for developers serves files that are already ready for a browser: HTML, CSS, JavaScript, images, fonts and media. It is the last mile for a built demo or document, not a build service and not an application server.\ \ The artifact is often smaller than the infrastructure normally used to publish it. A proof of concept may need a URL for an afternoon. A docs build may need to survive a release review. A generated coverage report may need to be opened by somebody outside the local network. In those cases a browser preview link answers the requirement without teaching the project a new CI provider.\ \ The boundary is the build output. Vite usually produces dist; Create React App usually produces build; a static Next.js export produces out. The framework guides keep those commands and folders together. If an AI tool gave you one self-contained React component, single-file React hosting can run .jsx or .tsx in the browser, but a component importing third-party packages still needs its project build.\ \ - **Prototype.** A working interaction for a product conversation, with enough fidelity to click rather than explain.\ - **Built application demo.** The static output of Vite, React, Vue, Astro or another framework after the local build succeeds.\ - **Documentation.** A generated docs site, reference or release guide that should be readable without cloning the repository.\ - **Test or coverage report.** An HTML report produced by a tool, preserved as its own reviewable artifact.\ - **Code experiment.** A single HTML, JSX or TSX file that has no server dependency and needs a public browser.\ - **Static export.** The browser-ready version of a project whose source repository is not itself deployable as static files.\ \ ## Small deployment jobs that do not need a platform\ \ The common thread is not the framework. It is that the output is complete and the next person needs a URL.\ \ - **Prototype builders.** Share a working browser preview in a ticket or call instead of recording a video of localhost.\ - **Frontend developers.** Publish the built ZIP or folder after the framework has produced static output.\ - **AI-assisted builders.** Put a generated page online through AI output hosting, with the no-build path only when the file is actually self-contained.\ - **Docs maintainers.** Use the framework guide hub to find the output folder, then publish the generated site as one immutable deployment.\ \ ## What you get\ \ ### A strict static boundary\ \ The server sends the files you built and never executes user code. That boundary keeps the visitor path small and makes a failed upload explainable: either the output is present or the project still needs a runtime.\ \ - HTML, CSS, browser JavaScript, images, fonts and media are served as files.\ - PHP, Node servers, API routes and server actions do not run.\ - A client-side app can call an existing API when that API allows browser requests.\ \ ### Immutable deploys, stable site address\ \ Each publish creates a separate deployment and then points the site at it. A broken update does not overwrite the previous files, and the public address stays attached to the site rather than to one upload.\ \ - The same URL opens the newest deployment after each publish.\ - Rollback begins on Pro for a one-click return to an earlier deployment.\ - The free plan includes up to 15 publishes a day.\ \ ### A security check at the handoff\ \ Static does not mean harmless. A copied project can still contain credentials, repository metadata or private files, so every deploy is inspected after it goes live and warnings stay attached to that deployment.\ \ - The check looks for a published .env file, .git directory and private-key material.\ - It also flags API-key patterns left in browser JavaScript.\ - A warning is visible on every plan and should trigger secret rotation, not reassurance.\ \ ### A route from local output to a public browser\ \ The project can stay local or live in any source-control system. Publishing does not require a webhook, deploy key or build configuration because those are not part of this workflow.\ \ - Use deploy guides for the exact build command and output directory.\ - Use HTML hosting when the artifact is one page and its assets.\ - Use the HTML tester before publishing pasted or generated markup.\ \ ## What the free plan includes\ \ The free plan covers one demo, docs site or report and enough daily publishes for an active review loop.\ \ - 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.\ - A public API and editor integrations are available when the browser upload is not the right entry point.\ \ ## A screenshot answers a different question\ \ A screenshot is faster when the reviewer only needs to see one state, and it belongs in the ticket beside the explanation. A hosted build earns its extra step when the reviewer needs to click, resize, inspect browser behavior or verify the current revision.\ \ - **Interaction.** Droply: Links, controls, routes and browser JavaScript run in the published build. Screenshot or local preview: A screenshot records pixels and a local preview only opens on a machine that can reach it.\ - **Responsive review.** Droply: The same URL opens on the reviewer's phone, tablet or desktop. Screenshot or local preview: A screenshot records one viewport; a localhost URL is not normally public.\ - **Revision path.** Droply: Publish the next build behind the same site address. Screenshot or local preview: Send another image, recording or temporary tunnel address.\ - **Browser debugging.** Droply: The reviewer can reproduce real network, console and layout behavior. Screenshot or local preview: A still image has no runtime to inspect.\ - **Context in the ticket.** Droply: The ticket holds a link to the current external artifact. Screenshot or local preview: A screenshot is visible inline and may be better for one exact state.\ - **Setup.** Droply: Build, upload and name the site. Screenshot or local preview: A screenshot takes one capture; a local preview needs no publish at all.\ \ Workflow rows checked 8 September 2026 against MDN's file URL reference. This compares observable browser behavior, not a vendor plan. A screenshot remains the better artifact when one fixed state is the whole subject.\ \ ## When Droply is the wrong choice\ \ Use a developer deployment platform when the project needs the platform to build, run or coordinate the application. This route is intentionally narrower: finished static output goes in, files come back out.\ \ - You want a preview for every pull request, a build on every commit or branch-aware environments. Use a Git-connected platform.\ - You need server rendering, API routes, middleware, queues, databases or long-running processes. Those need an application host.\ - You are sharing one visual state and the reviewer should see it inline in a ticket. A screenshot is quicker and clearer.\ - 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.\ \ ## Frequently asked questions\ \ ### What should a developer upload to static hosting? Upload the build output, not the source project. For Vite that is commonly dist, for Create React App it is build, and for a static Next.js export it is out; the framework guides give the current command and folder per framework. ### Can I upload a React, Vue or Astro project? Yes after it has been built into static output. Upload the finished folder or ZIP. A single self-contained .jsx or .tsx file can run without a build, but imports from npm packages still require the project build. ### Does Droply run npm install or npm run build? No. Builds never run on the server. Run the command locally or in your existing pipeline and upload only what the browser should receive. ### Can I host a Next.js app? Only as a static export. Routes that require a Node server, server actions, middleware or runtime rendering do not work here and need an application platform. ### Can a static site call my API? Yes. Browser JavaScript can call an API hosted elsewhere when that API permits the origin through CORS and handles authentication safely. Do not put a private API secret into the published JavaScript. ### Will the preview URL change after a new build? No. Re-publish to the same site and the address stays fixed while the deployment behind it changes. Rollback to an earlier deployment starts on Pro. ### Can I keep a prototype out of search results? Free sites are served noindex. If the content also needs an access gate, password protection starts on Starter, and expiring links start on Starter. ### Is there an API for publishing a build? Yes. The API reference covers token authentication and deployment endpoints. The Chrome, VS Code, ChatGPT and Zapier integrations cover other entry points. ### What does the deploy security check find? It warns about exposed .env and .git paths, private-key material and API-key patterns in published JavaScript. If a real secret was public, remove it and rotate it; taking the page down does not revoke a credential somebody may already have copied. ### When should I use GitHub Pages, Netlify or Vercel instead? Use them when their repository builds, pull-request previews or server runtimes are part of the job. The comparison hub sets out those tradeoffs with dated sources rather than pretending one static workflow fits every project.\ \ ## Other audiences\ \ - [Website Hosting for Designers](https://droply.host/for/designers)\ - [Landing Page Hosting for Marketing Teams](https://droply.host/for/marketing)\ - [Web Hosting for Students](https://droply.host/for/students) --- Source: https://droply.host/for/marketing # Landing page hosting for marketing teams moving today\ \ Put a campaign page, one pager, event invite, media kit or sales leave-behind on its own link without joining an engineering release. Publish the finished file, send it, and update it in place.\ \ ## What marketing teams actually send\ \ Landing page hosting for marketing teams turns an approved campaign artifact into a browser link without making the team own a server or repository workflow. It is useful when the page or document is already finished and distribution is the remaining job.\ \ The artifact changes with the channel. Paid media may need a focused HTML landing page. Sales may need a one-page PDF that opens cleanly on a phone. An event team may need an invitation and a QR code. The shortest route is to host the format that already passed review: paste HTML into a URL, publish a PDF as a link, or turn a menu or handout into a QR destination.\ \ This does not remove the need for analytics strategy, forms, consent or a campaign system of record. It removes the release dependency for a static asset. If the page includes a form, it can post to an existing service; email capture provided by Droply starts on Business. If it needs account-aware personalization or server-side decisions, it belongs on the application stack instead.\ \ - **Campaign landing page.** A focused static page for one audience, offer and next action.\ - **One pager.** A product, service or account brief that opens in a browser instead of waiting in an attachment tray.\ - **Media kit.** Logos, approved descriptions, images and contact details gathered at one current address.\ - **Event page.** The agenda, venue, speakers, registration link and practical details a guest checks from a phone.\ - **Sales leave-behind.** A post-call page or PDF that a buyer can reopen and forward without finding the original thread.\ - **Promotion or menu.** A time-bound offer, price sheet or QR destination that needs to change without reprinting the code.\ \ ## Where a static link removes a handoff\ \ The page is most useful at the point where approved material is waiting for another team to make it public.\ \ - **Campaign marketers.** Publish approved code through HTML to URL or upload the built campaign folder.\ - **Sales teams.** Give a deck or one pager a direct PDF link that can be updated after it is sent.\ - **Event and field teams.** Point print material at a PDF QR code or live information page.\ - **AI-assisted teams.** Publish a generated page through AI website hosting, building first when the output is a full project.\ \ ## What you get\ \ ### A short path from approval to distribution\ \ Static assets do not need a release train when they are not part of the main application. The uploader and paste flow put the approved result online without requiring access to a production repository.\ \ - A loose .html file is accepted without a ZIP when it carries everything it needs.\ - A folder or ZIP keeps images, fonts, CSS and scripts in their relative paths.\ - Raw HTML from a writer or AI tool can use the paste flow.\ \ ### One destination for the life of the campaign\ \ A printed QR code and a sent email cannot be recalled. Updating the deployment behind the address lets the campaign page change without invalidating the distribution that already happened.\ \ - Every re-publish keeps the same site address.\ - Rollback begins on Pro if an approved version has to return.\ - Expiring links begin on Starter when the campaign should close automatically.\ \ ### Controls for the point after launch\ \ A public page needs more than a URL when it becomes part of a campaign. Paid tiers add the controls that make the address useful beyond a one-off share.\ \ - Visitor analytics start on Pro.\ - Email capture starts on Business.\ - Custom domains start on Pro, with automatic HTTPS.\ \ ### A check before more traffic finds the mistake\ \ Campaign folders are often copied from staging work. The deploy inspection looks for files and credential patterns that should not have crossed into a public package.\ \ - Every plan receives the check, including free.\ - Warnings cover .env files, .git folders, private keys and API-key patterns.\ - The check reports the risk; a leaked credential still has to be rotated by its owner.\ \ ## What the free plan includes\ \ The free plan covers one campaign page or document with a real HTTPS address and no card.\ \ - 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.\ - The link keeps its address through copy fixes, image swaps and other re-publishes.\ \ ## Email can deliver a file, but it cannot become the page\ \ An attachment is the right choice when the recipient needs the source file and the message is the context. A hosted link is better when the browser experience, a stable destination and future updates are part of the campaign.\ \ - **First open.** Droply: The link opens the published page or document over HTTPS. Email attachment: The recipient opens or downloads a file from the message.\ - **After an edit.** Droply: Publish the corrected asset at the same address. Email attachment: Send a replacement attachment and explain which version is current.\ - **Interactive HTML.** Droply: HTML runs as a browser page with its links and scripts. Email attachment: Mail systems treat HTML files as attachments and may block risky executable formats.\ - **File size.** Droply: The limit is plan-based; the free upload ceiling is 25 MB. Email attachment: Personal Gmail accounts allow up to 25 MB total, then Gmail substitutes a Drive link.\ - **Campaign address.** Droply: A site subdomain, or a custom domain from Pro. Email attachment: The file remains part of an email or shared-drive flow.\ - **Best fit.** Droply: A page or collateral destination that needs to open, change and be forwarded. Email attachment: A source file the named recipient should download, edit or archive.\ \ Email rows checked 8 September 2026 against Google's Gmail attachment guide, which documents the 25 MB personal-account limit, Drive-link fallback and blocked executable file types. Mail providers differ, and product limits can change.\ \ ## When Droply is the wrong choice\ \ Keep the page on the main product stack when it needs that stack to make decisions, hold customer data or coordinate a release. A static campaign page is a distribution artifact, not a second application.\ \ - You need server-side personalization, authenticated account data, a cart or a database-backed form workflow.\ - The asset must inherit the main site's release process, experiments and consent tooling. Publish it with the main site.\ - The recipient needs to edit the source document. Send the attachment or collaboration link instead of a read-only published result.\ - 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.\ \ ## Frequently asked questions\ \ ### Can a marketing team publish a landing page without Git? Yes, when the page is already static output. Upload the HTML or ZIP, or paste the HTML code, choose the address and publish without a repository integration. ### Can I upload a page made by an AI tool? Yes. A single HTML file and a self-contained .jsx or .tsx file can take the direct path. A full Vite, Next.js or other project needs to be built first; the AI hosting guide explains the boundary. ### Can I change campaign copy without changing the URL? Yes. Re-publish the corrected files to the same site. Ads, messages and QR codes that already carry the address continue to reach the newest deployment. ### Can I use our campaign domain? Yes, from Pro. Connect the domain, complete ownership verification and the HTTPS certificate is issued and renewed automatically. ### Does a landing page include analytics? Visitor analytics start on Pro. The free plan still counts usage against its 5,000 monthly visit allowance, but it does not provide the paid analytics view. ### Can the page collect email addresses? Email capture starts on Business. If the page already posts to another form service, that client-side form can continue to call it as long as the service allows the published origin. ### Can I make a campaign link expire? Yes, from Starter. Choose a preset duration or a date, which is useful for embargoed material, event handouts and offers that should stop resolving after the campaign. ### Should I send a PDF or build a landing page? Use the format that does the job. A PDF link preserves a signed-off document and is quick to share; HTML is better when responsive layout, navigation or browser interaction matters. ### Will a free campaign page appear in search? No. Free sites are served noindex. Indexing begins on Starter, which should be a deliberate choice for a campaign page rather than an accidental side effect. ### What should not be put in the uploaded campaign folder? Do not include source repositories, .env files, private keys or secrets in browser JavaScript. The deploy security check warns about common exposures, but any credential that reached a public URL should be rotated.\ \ ## Other audiences\ \ - [Website Hosting for Designers](https://droply.host/for/designers)\ - [Static Hosting for Developers](https://droply.host/for/developers)\ - [Website Hosting for Small Business](https://droply.host/for/small-business) --- Source: https://droply.host/for/real-estate # Website hosting for real estate agents with a listing to share\ \ Give a property page, brochure, floor plan or photo set one address that opens from a text or QR code. Correct the details behind the same link instead of sending a new attachment after every change.\ \ ## What real estate teams actually send\ \ Website hosting for real estate agents puts a finished property page or document at a browser address that buyers, sellers and colleagues can open without an account. It is a delivery layer for listing material, not a listing database, CRM or transaction system.\ \ The same property often exists in several formats because each channel has a different constraint. A detailed HTML page works in a browser. A signed-off brochure keeps its layout as a PDF. A floor plan may need its own direct link. Use PDF to link for a brochure, PDF to QR code for print, and a static site upload when the listing is already a page or folder.\ \ The value of one hosted address shows up when details change. A price adjustment, open-house time or corrected measurement should not start another round of messages with another attachment. Re-publish at the same URL and the buyer who opens the earlier text sees the current material. This does not synchronize with an MLS or CRM; it keeps one independently published artifact current.\ \ - **Property page.** A responsive listing with the key facts, photographs, location context and next action.\ - **PDF brochure.** The designed leave-behind for a buyer, seller meeting, email follow-up or open house.\ - **Floor plan.** A drawing or PDF that opens on its own when room layout matters more than the rest of the listing.\ - **Photo set.** A selected collection that can be viewed from a phone without unpacking a ZIP or requesting drive access.\ - **Open-house page.** The address, hours, property facts and contact route behind the code printed on a sign or handout.\ - **Listing presentation.** A seller-facing proposal or market overview shared before or after a meeting.\ \ ## The property, in the format the moment needs\ \ A buyer opening a text, a visitor scanning a sign and a seller reading a proposal should not all be forced through the same file workflow.\ \ - **Listing agents.** Turn the approved brochure into a direct PDF link for buyer follow-up.\ - **Open-house teams.** Put a QR code in front of a brochure and keep the destination current after printing.\ - **Brokerage marketers.** Publish a finished property microsite through static website hosting.\ - **Commercial teams.** Share plans, prospectuses and related files as a single portfolio-style destination.\ \ ## What you get\ \ ### Publish the artifact you already have\ \ A property does not need to be rebuilt as a website just because it needs a URL. HTML, PDFs and images can each be the destination when that format is the clearest answer for the reader.\ \ - A single HTML file can go online without being wrapped in a ZIP.\ - A site folder or ZIP keeps its own photos, styles, maps and scripts together.\ - PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else.\ \ ### Print one code before every detail is final\ \ A QR code points to the address, not to one frozen deployment. That means the sign or handout can keep working while the page, brochure or schedule behind it changes.\ \ - on every plan, including the free one.\ - The same site URL survives every re-publish.\ - Use the editable QR destination pattern for any printed property handout.\ \ ### Choose public, gated or time-limited\ \ A public listing and a private seller presentation do not have the same audience. Start with a normal link, then use plan controls when the material should be restricted.\ \ - Password protection starts on Starter and covers the page plus its assets.\ - Expiring links start on Starter for an embargo, review window or concluded listing.\ - Free sites are noindex; intentional search visibility starts on Starter.\ \ ### Keep old messages useful\ \ Listing material is forwarded and reopened. Updating the deployment in place reduces the chance that an early recipient keeps circulating a superseded price sheet or schedule.\ \ - Publish up to 15 revisions a day on the free plan.\ - Rollback begins on Pro when a previous version was the correct one.\ - Every deploy receives the security check before more people find an exposed file.\ \ ## What the free plan includes\ \ The free plan is enough for one active listing page or brochure link, with no card and an HTTPS address.\ \ - 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.\ - The address stays the same when the price, photos, schedule or document changes.\ \ ## Drive is for file collaboration; a hosted link is for the handoff\ \ Google Drive is the better choice when colleagues need to edit, comment on or organize source files together. A hosted link is a cleaner public destination when a buyer should open the finished page or brochure without seeing a drive interface or a permission workflow.\ \ - **What the buyer opens.** Droply: The published page, PDF or image at its own HTTPS address. Google Drive link: A Drive file viewer governed by the file's sharing role.\ - **Anyone-with-link access.** Droply: A public link by default; password protection begins on Starter. Google Drive link: Drive supports Anyone with the link, with Viewer, Commenter or Editor roles.\ - **Replacing a PDF.** Droply: Re-publish to the same site address. Google Drive link: Manage versions, then Upload new version, keeps one Drive file link.\ - **Old versions.** Droply: Rollback begins on Pro. Google Drive link: A Drive version may be deleted after 30 days or 100 newer versions unless Keep forever is chosen.\ - **Printed QR destination.** Droply: The QR points at the site address and survives revisions. Google Drive link: A QR can point at the Drive share URL, with Drive permissions still controlling access.\ - **Best fit.** Droply: Buyer-facing finished material, custom presentation and a stable public address. Google Drive link: Internal file storage, commenting, editing and access by Google account.\ \ Google Drive rows checked 8 September 2026 against Google's file-sharing guide and its file-version guide. Sharing roles, version retention and product behavior can change.\ \ ## When Droply is the wrong choice\ \ Use the brokerage, MLS, CRM or transaction platform for the records and workflows it is responsible for. A hosted static page can present approved information, but it cannot become the system that synchronizes or governs the listing.\ \ - You need live MLS synchronization, saved searches, account-specific listings or a database-backed property search.\ - You are handling contracts, identification, financial records or other sensitive transaction documents. Use the approved transaction system, not a public site.\ - Several colleagues need to edit the source brochure together. Keep the working file in Drive or the design tool and publish only the approved result.\ - 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.\ \ ## Frequently asked questions\ \ ### How do I make a real estate listing into a link? Upload the finished HTML page, ZIP, PDF brochure or image, choose the property address and publish. For a document-only workflow, PDF to link gives the brochure a direct browser URL. ### Can I make a QR code for a property brochure? Yes. Publish the brochure, then use PDF to QR code. The printed code points to the stable site address, so a replacement brochure does not require a replacement code. ### Can I change a listing price without changing the link? Yes. Replace the page or document behind the existing site. Anyone opening the earlier text, email or QR code reaches the current deployment. ### Can I use the property address as the subdomain? You can request an available subdomain that follows the naming rules. Avoid putting sensitive client information into a public address, and use a brand or listing reference when the street address should not be exposed. ### Can a seller presentation be password protected? Yes, from Starter. The password is checked before the page and supporting files are served. Do not use a static site for highly sensitive transaction records even with a password. ### Can a listing link expire after the property sells? Yes, from Starter. Choose a duration or date. You can also replace the content with an updated status when keeping the address useful is better than switching it off. ### Will a free property page show in Google? No. Free sites are served noindex. Indexing starts on Starter if search discovery is part of the listing strategy and the content is appropriate for public search. ### Can I connect a brokerage or campaign domain? Yes, from Pro. Verify the domain and point it at the provided target; HTTPS issuance and renewal are handled automatically. ### Does this replace my MLS or real estate website? No. It publishes a static page or file. Use the MLS, CRM and brokerage site for synchronized inventory, lead routing and required records, and use this for a separate finished artifact when that helps. ### Can I host a photo gallery and video? Yes when the gallery is part of static browser-ready files and the upload fits the plan limits. Compress media for phone connections and upload the folder intact so its relative paths keep working.\ \ ## Other audiences\ \ - [Landing Page Hosting for Marketing Teams](https://droply.host/for/marketing)\ - [Website Hosting for Small Business](https://droply.host/for/small-business)\ - [Website Hosting for Designers](https://droply.host/for/designers) --- Source: https://droply.host/for/recruiting # Website hosting for recruiting teams sharing the next step\ \ Publish a job page, hiring pack, offer guide or onboarding resource as one browser link. Send the address once, update the document behind it, and use a password or expiry when the audience is limited.\ \ ## What recruiting teams actually send\ \ Website hosting for recruiting teams gives candidate-facing pages and documents a stable browser address. It works for approved static material that should be easy to open, forward and update, while the ATS and HR systems keep responsibility for applications and personal data.\ \ A recruiting process produces more shareable material than the job description. Candidates receive interview guides, team context, role scorecards, offer explanations and onboarding schedules. A resume link solves the same problem from the candidate side, while a PDF link works for a hiring pack that should keep its layout and open without a drive permission screen.\ \ The access model should follow the material. A public job page is meant to travel. An interview guide may be fine behind a private address. An offer or internal onboarding document may need an approved HR system rather than static hosting at all. Password protection and expiry are useful controls, but they do not change the classification of sensitive personal or employment records.\ \ - **Job page.** The role, team, location, expectations and application route presented at a direct public address.\ - **Hiring pack.** A PDF or page that gives candidates the company context, process, benefits and practical details.\ - **Interview guide.** The schedule, participants, preparation and call links for a specific stage.\ - **Offer guide.** A plain-language companion to the formal offer, with the role context and next steps.\ - **Onboarding page.** The first-week schedule, links, reading and contact points for a new colleague.\ - **Recruiting portfolio.** Employer-brand material, team stories and role families collected for repeated candidate conversations.\ \ ## Candidate communication around the system of record\ \ The ATS owns the application. These are the static pages and documents that help a person understand what happens before and after it.\ \ - **Recruiters.** Publish a role or hiring pack and pair it with the resume-link guidance candidates can use.\ - **People teams.** Share an approved handbook excerpt or onboarding guide through PDF to link.\ - **Employer-brand teams.** Review a finished careers page through a browser preview before it moves to the main site.\ - **Hiring managers.** Turn approved role HTML into a link with HTML to URL, without editing the production site.\ \ ## What you get\ \ ### A candidate opens the material, not the storage system\ \ The hosted address presents the finished page or document directly. That removes a permission step from public candidate communication and gives forwarded links a clear destination.\ \ - HTML pages, built static sites, PDFs and office documents are accepted formats.\ - The link uses HTTPS and opens in a browser on phone or desktop.\ - A custom domain becomes available on Pro for branded recruiting material.\ \ ### The current process stays at the sent address\ \ Interview steps and role details change while outreach is already in motion. Re-publishing behind the same URL means the original message can remain the useful reference.\ \ - The public address stays fixed across deployments.\ - The free plan allows up to 15 publishes a day.\ - Rollback begins on Pro if an older approved version has to return.\ \ ### Access controls for limited material\ \ Not every hiring artifact belongs on an unrestricted public page. Use the available controls for ordinary limited-access material, and keep regulated or sensitive records in the approved HR system.\ \ - Password protection starts on Starter.\ - Expiring links start on Starter.\ - The deploy-time security check runs on every plan and warns about common exposed secrets.\ \ ### Separate presentation from personal data\ \ A static page is well suited to approved information that is the same for every reader. It is not a candidate database, identity system or confidential document vault.\ \ - Keep applications and candidate profiles in the ATS.\ - Use document hosting for approved general material, not personnel records.\ - Use static hosting for careers content that has no server-side workflow.\ \ ## What the free plan includes\ \ The free plan can host one public role page, hiring pack or general onboarding resource without a card.\ \ - 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.\ - The address remains stable while role details, interview instructions or onboarding links are corrected.\ \ ## Use an attachment when the file itself is the handoff\ \ Email is the right place for a formal file that belongs in one named conversation. A hosted page is the better reference for candidate-facing information that changes, gets forwarded or needs to open the same way outside that thread.\ \ - **Candidate experience.** Droply: The address opens the page or document in a browser. Email attachment: The file remains attached to a message and may open in a mail or document viewer.\ - **Correction after sending.** Droply: Re-publish at the same address. Email attachment: Send a follow-up attachment and identify the current version.\ - **Forwarding.** Droply: The forwarded URL still points to the current deployment. Email attachment: The forwarded message carries the version that was attached at that time.\ - **Size.** Droply: The upload limit comes from the plan; free is 25 MB. Email attachment: Personal Gmail accounts allow 25 MB total before replacing the attachment with a Drive link.\ - **Access gate.** Droply: Password protection starts on Starter; expiry starts on Starter. Email attachment: Access follows the message and mail provider; it is not a shared site password.\ - **Best fit.** Droply: General candidate information and resources that need a current reference link. Email attachment: A formal or editable file sent to one named recipient and kept in the message record.\ \ Email rows checked 8 September 2026 against Google's Gmail attachment guide, which documents the 25 MB personal-account limit and Drive-link fallback. Mail-provider limits differ and can change.\ \ ## When Droply is the wrong choice\ \ Keep systems of record and sensitive employment material in the approved recruiting and HR tools. Static hosting is for presentation and distribution of approved files, not for collecting or governing candidate data.\ \ - You need an application form, interview scorecards, candidate status, consent records or automated recruiting workflows. Use the ATS.\ - The file contains identification, bank details, health information, background checks or confidential personnel records. Use the authorized secure system.\ - Several people need to edit and comment on the source document. Keep it in the collaboration tool and publish only the approved candidate-facing version.\ - 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.\ \ ## Frequently asked questions\ \ ### Can I publish a job description as a web page? Yes. Upload static HTML or a built ZIP, or use HTML to URL when you have approved markup. Link the application button to the ATS rather than trying to collect applications in a static page. ### Can a hiring pack be a direct PDF link? Yes. The PDF to link flow publishes the document at an HTTPS address that opens in a browser and can keep the same URL after the PDF is replaced. ### Can I update interview instructions after sending them? Yes. Publish the replacement behind the same site address. Candidates who reopen the original message see the current version instead of the file attached at send time. ### Can a recruiting page be password protected? Yes, from Starter. Use it for ordinary limited-access material, but keep regulated, highly sensitive or candidate-specific records in the authorized ATS or HR system. ### Can an offer guide expire automatically? Yes, from Starter. An expiry can close a supporting page after a date, but the formal offer and acceptance record should remain in the system responsible for them. ### Can I use a careers subdomain or custom domain? A Droply subdomain comes with every site. Custom domains start on Pro, with ownership verification and automatic HTTPS certificate management. ### Will a free job page appear in Google? No. Free sites are noindex. Search indexing starts on Starter; use the main careers platform when structured job distribution and synchronized search visibility are required. ### Does this replace an ATS? No. It hosts static pages and files. The ATS should continue to collect applications, record consent, route candidates and control access to personal information. ### Can a candidate host a resume here too? Yes. The resume to link guide shows how to publish a PDF or HTML resume at an address that can be updated without resending it. ### What does the security check do for a hiring page? It warns about published .env files, .git folders, private-key material and API-key patterns. It does not classify candidate data, so the team remains responsible for keeping personal records out of the upload.\ \ ## Other audiences\ \ - [Landing Page Hosting for Marketing Teams](https://droply.host/for/marketing)\ - [Website Hosting for Educators](https://droply.host/for/educators)\ - [Website Hosting for Small Business](https://droply.host/for/small-business) --- Source: https://droply.host/for/small-business # Website hosting for small business without a web team\ \ Put a simple site, menu, price list, invitation, document or image collection online from the file you already have. No server to configure, and no repository workflow to learn before the link can be shared.\ \ ## What a small business actually sends\ \ Website hosting for small business is the place where a finished page or file becomes reachable from the internet. For a business without a web team, the practical question is whether the existing menu, service page, price list or brochure can become a link without first becoming a software project.\ \ Sometimes the honest answer is one page. A tradesperson may need a service list and phone number. A cafe may need a menu behind a QR code. A consultant may need a portfolio link, while an event organizer may only need a PDF that opens in a browser. Hosting the artifact directly keeps the technical work proportional to the job.\ \ This is not a managed business application. It does not provide inventory, bookings, a shopping cart, user accounts or a database. It serves finished static files and gives them a stable address. The built-in AI page builder can write a simple page from a description, and site import can copy up to 40 pages plus 600 assets from an existing public site, but dynamic systems still belong somewhere that runs them.\ \ - **One-page website.** Services, hours, contact details and a clear next action for a business that does not need an application.\ - **Menu or price list.** A page or PDF that customers can open from a profile, message, counter card or printed QR code.\ - **Brochure or catalog.** An approved document presented at a direct browser address instead of inside a drive folder.\ - **Portfolio or gallery.** Selected work, project photos or examples that help a customer decide whether to make contact.\ - **Invitation or event page.** The time, place, directions and updateable details for one gathering or promotion.\ - **Existing static site.** A finished HTML site copied from another host or uploaded from the files already held by the business.\ \ ## Common jobs that only need a page or file\ \ Choose the shortest workflow that leaves the customer with a clear browser destination.\ \ - **Restaurants and cafes.** Publish a QR code menu that can change without reprinting the code.\ - **Independent professionals.** Share work and services through a portfolio link.\ - **Local service businesses.** Turn a brochure or price sheet into a direct PDF link.\ - **First-time site owners.** Use the AI page builder when there is no existing file to upload.\ \ ## What you get\ \ ### The file is enough to begin\ \ A business should not have to turn a small publishing job into a development workflow. Upload the finished material in the format that already exists and let the address be the deliverable.\ \ - A single HTML file can be uploaded without a ZIP.\ - PDFs, images, office documents and static site folders are first-class uploads.\ - The free plan accepts up to 25 MB per upload and 25 MB across the account.\ \ ### Three ways to get the first page\ \ Use the route that matches the starting point: upload finished files, copy an existing public site, or describe a simple page to the built-in builder.\ \ - Site import copies up to 40 pages and 600 assets from a public address.\ - The AI page builder writes, previews and publishes a static page from a description.\ - The HTML paste flow works when somebody sent code rather than a file.\ \ ### One address for changing information\ \ Hours, prices, menus and event details change after the link reaches customers. Re-publishing behind the same address keeps profiles, messages and printed codes useful.\ \ - Every update keeps the site URL.\ - Rollback starts on Pro when an earlier version needs to return.\ - Expiring links start on Starter for short campaigns or event material.\ \ ### Add control only when the job needs it\ \ Start with a normal hosted address. Paid plans add the controls that matter when the page becomes part of the business rather than a one-off share.\ \ - Custom domains start on Pro, with HTTPS handled automatically.\ - Password protection starts on Starter.\ - Visitor analytics start on Pro, and email capture starts on Business.\ \ ## What the free plan includes\ \ The free plan can keep one simple business page, menu, portfolio or document online without a credit card.\ \ - 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.\ - The site address remains fixed when the business updates its hours, prices, menu or images.\ \ ## Drive keeps working files; hosting presents the finished one\ \ Google Drive is better for organizing files with colleagues and collecting comments on working documents. A hosted link is better when a customer should open the finished page, menu or brochure directly and the address needs to look like a public destination.\ \ - **Customer view.** Droply: The finished page, PDF, image or site opens at its own HTTPS address. Google Drive link: The file opens in a Drive viewer with access governed by sharing roles.\ - **Collaboration.** Droply: No document comments or shared editing. Google Drive link: Viewer, Commenter and Editor roles make Drive better for working on the source file.\ - **Public access.** Droply: Public by default; password protection starts on Starter. Google Drive link: Anyone with the link can open without sign-in when the owner selects that access.\ - **Replacing a file.** Droply: Re-publish and keep the site address. Google Drive link: Manage versions, then Upload new version, keeps the Drive file link.\ - **Business domain.** Droply: Available from Pro, with automatic HTTPS. Google Drive link: The public address remains on Google Drive.\ - **Best fit.** Droply: Customer-facing finished material and a simple public page. Google Drive link: Internal storage, shared editing, comments and source-file organization.\ \ Google Drive rows checked 8 September 2026 against Google's file-sharing guide and its file-version guide. Sharing roles and product behavior can change.\ \ ## When Droply is the wrong choice\ \ Use a full website platform or business system when the site has to run the operation rather than explain it. Static hosting stays useful by keeping its boundary narrow and visible.\ \ - You need ecommerce checkout, inventory, appointment booking, customer accounts or a database. Use a platform built for that workflow.\ - You want to edit every page through a visual content-management system with multiple staff roles. Use a site builder or CMS.\ - You need email, accounting, CRM or file collaboration. Hosting a page does not replace those business tools.\ - 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.\ \ ## Frequently asked questions\ \ ### What kind of small business website can I host? Any finished static site that runs in a browser without server code. That includes one-page service sites, portfolios, menus, event pages and static exports from many builders. ### Can I host only a PDF or image instead of a website? Yes. PDFs, images and office documents are supported directly. Use PDF to link when the document already communicates the information clearly. ### Can I make a website if I do not have a file? Yes. The AI website builder can write and preview a simple static page from a description. You can also paste HTML through HTML to URL. ### Can I copy my existing small business site? Site import can copy up to 40 public pages and 600 assets into a static version. Dynamic forms, account areas, search and server features still need their original services or replacements. ### Can I update prices or opening hours without changing the link? Yes. Re-publish the page, menu or document behind the same site address. Customers using an old message, profile link or QR code reach the current deployment. ### Can I use my own business domain? Yes, from Pro. Verify the domain, point it at the provided target and HTTPS certificates are issued and renewed automatically. ### Can I put a password on a page? Yes, from Starter. It is useful for a client price sheet or draft, but a public menu or service page should normally remain open to the people receiving the link. ### Will the free site appear in Google? No. Free sites are noindex. Search visibility starts on Starter; a business relying on organic search should plan for that tier and for its wider local-search work. ### Does this include online booking or a store? No. Static pages can link to an external booking, payment or store service, but Droply does not run the database or server code those systems require. ### What should I do if the security check finds a secret? Remove the file, publish a clean version and rotate the exposed credential immediately. The check can warn about a public .env file, private key or API-key pattern, but it cannot revoke the secret for you.\ \ ## Other audiences\ \ - [Landing Page Hosting for Marketing Teams](https://droply.host/for/marketing)\ - [Website Hosting for Designers](https://droply.host/for/designers)\ - [Website Hosting for Real Estate Agents](https://droply.host/for/real-estate) --- Source: https://droply.host/for/educators # Website hosting for educators sharing a lesson or resource\ \ Publish a lesson page, reading, slide deck, project gallery or class resource as one browser link. Use the file you already have, replace it behind the same address, and keep student records in the systems meant for them.\ \ ## What educators actually send\ \ Website hosting for educators gives finished learning material a stable browser address. It is suited to the same static resource for every reader, such as a lesson page, reading, slide deck or project gallery, while the LMS remains responsible for enrollment, grades and private student data.\ \ The format should follow the teaching purpose. A responsive HTML page can combine explanation, media and links. A PDF link preserves a reading or handout exactly. A PDF QR code can connect a printed worksheet or classroom display to the current document. A small class site can be uploaded as finished static files when navigation across several pages matters.\ \ The separation from the learning platform is important. A public resource link is good at distribution and poor at identity. It does not know which student opened it, whether the reader is enrolled, what grade they received or whether consent exists for publishing their work. Keep those records in the LMS and publish only material that is appropriate for the audience you choose.\ \ - **Lesson page.** The explanation, examples, links and media for one topic at an address that works on school and personal devices.\ - **Reading or handout.** A PDF or document that should open without a download hunt or drive-access request.\ - **Slide deck.** Class slides or a presentation students can reopen after the session from the link in the course.\ - **Class resource site.** A small static collection of references, schedules, examples and supporting pages.\ - **Project gallery.** Work published with the appropriate permission, presented for a class, exhibition or public audience.\ - **Syllabus or schedule.** A current reference whose dates and links can be corrected without replacing the address in every course message.\ \ ## Resources around the learning platform\ \ The LMS should keep the course records. These links make approved pages and documents easier to reach inside and outside it.\ \ - **Teachers and instructors.** Publish a reading or handout through PDF to link.\ - **Classroom facilitators.** Connect print material to the current file through PDF to QR code.\ - **Course teams.** Put a built resource hub online with static website hosting.\ - **Program and exhibition leads.** Present approved work as a portfolio-style collection.\ \ ## What you get\ \ ### One publishing path for several teaching formats\ \ A course contains pages, readings, images, slides and media. Hosting those formats directly lets each resource keep the shape that makes it useful instead of forcing everything through one editor.\ \ - A single HTML lesson can be uploaded without a ZIP.\ - A built multi-page resource site keeps its relative assets and navigation.\ - PDFs, images, office documents and media can be the published destination.\ \ ### The syllabus link can outlive the typo\ \ Once a URL is copied into an LMS, syllabus, slide deck and message, replacing it everywhere is a larger job than correcting the source. Re-publishing behind the same address keeps those references aligned.\ \ - The site URL remains the same after every deployment.\ - The free plan includes up to 15 publishes a day.\ - Rollback starts on Pro if an older approved version needs to return.\ \ ### Set the audience deliberately\ \ A public lesson and a private draft are different documents. Use the access controls for ordinary limited material, and do not use a static site as a substitute for student-record protections.\ \ - Free sites are noindex, so search engines do not list them.\ - Password protection starts on Starter.\ - Expiring links start on Starter for a time-bound resource or review.\ \ ### Let a printed reference point to the current lesson\ \ A QR code can sit on a worksheet, lab station, poster or exhibit while the page or PDF behind it changes. The physical object stays useful because it points to the stable site address.\ \ - on every plan, including the free one.\ - Use PDF to QR code for a reading or handout.\ - Use the editable QR destination pattern for any frequently updated classroom page.\ \ ## What the free plan includes\ \ The free plan can host one class resource, lesson site or document without a card.\ \ - 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.\ - The resource address remains fixed when you correct the lesson, replace the reading or update the schedule.\ \ ## Drive supports collaboration; hosting presents the lesson\ \ Google Drive is the better place for colleagues and students to comment on or edit a working document. A hosted link is better for an approved resource that should open as the page or file itself, with one public destination and no editing controls around it.\ \ - **Student view.** Droply: The page, PDF or media opens at its own HTTPS address. Google Drive link: The file opens in a Drive viewer governed by Viewer, Commenter or Editor access.\ - **Collaboration.** Droply: No shared document editing or inline comments. Google Drive link: Drive roles make it better for drafting, feedback and collaborative source files.\ - **Anyone-with-link access.** Droply: Public by default, with password protection from Starter. Google Drive link: Anyone with the link can open without sign-in when the owner selects that setting.\ - **Replacing a handout.** Droply: Re-publish behind the same site address. Google Drive link: Manage versions, then Upload new version, preserves the Drive file link.\ - **Old versions.** Droply: Rollback begins on Pro. Google Drive link: A version may be deleted after 30 days or 100 newer versions unless Keep forever is selected.\ - **Best fit.** Droply: Approved resources, static lesson pages and public-facing course material. Google Drive link: Working documents, comments, shared editing and file organization.\ \ Google Drive rows checked 8 September 2026 against Google's file-sharing guide and its file-version guide. Sharing roles, version retention and product behavior can change.\ \ ## When Droply is the wrong choice\ \ Use the LMS, school-approved storage or another authorized system when identity, enrollment, assessment or student records are part of the workflow. Static hosting is for approved content distribution, not course administration.\ \ - You need grades, submissions, attendance, enrollment rules, private discussion or student-level progress. Keep that work in the LMS.\ - The material contains protected student information or work that lacks permission for the chosen audience. Use the institution's approved system.\ - Readers need to comment on and edit the source document together. Use Drive or another collaboration tool, then publish the approved version if needed.\ - 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.\ \ ## Frequently asked questions\ \ ### Can a teacher host a lesson page for free? Yes. The free plan can host one static lesson or resource site with HTTPS and no card. Free sites are noindex, which keeps the page out of search but does not make a public URL private. ### Can I share a PDF reading as a browser link? Yes. Use PDF to link, choose the address and publish. PDFs specifically are capped at 512 KB on the free plan, below the 25 MB limit that applies to everything else. ### Can I put a QR code on a worksheet? Yes. Publish the page or document first, then use PDF to QR code for a handout. Replacing the resource behind the same address keeps the printed code useful. ### Can I update a syllabus without replacing the course link? Yes. Upload the corrected file to the same site. The URL already in the LMS, syllabus and messages continues to open the current deployment. ### Can a class resource be password protected? Yes, from Starter. A shared password is suitable for ordinary limited material, but it is not an identity system and should not be used as a substitute for student-record controls. ### Can a lesson link expire at the end of a course? Yes, from Starter. Set a duration or date for temporary material. A public reference that remains useful after the course may be better left active and updated. ### Can students publish their own projects? Yes when the work is suitable for the chosen audience and institution policy allows it. The separate web hosting for students guide covers projects, portfolios and assignment links. ### Does this replace Google Classroom or an LMS? No. It does not manage enrollment, grades, assignments or private discussion. Use it for a static resource that the LMS links to, not for the course records themselves. ### Can I host interactive teaching material? Yes when the interaction runs entirely in the browser. Anything that needs a server, database, user account or private API belongs on a platform that provides those parts. ### Will the security check find student data? No. It looks for common technical exposures such as .env files, .git folders, private keys and API-key patterns. The educator remains responsible for keeping protected student information out of the upload.\ \ ## Other audiences\ \ - [Web Hosting for Students](https://droply.host/for/students)\ - [Website Hosting for Recruiting Teams](https://droply.host/for/recruiting)\ - [Static Hosting for Developers](https://droply.host/for/developers) --- Source: https://droply.host/for/students # Web hosting for students with a project to submit\ \ Turn an HTML assignment, built class project, portfolio, resume, presentation or research document into one HTTPS link. Submit the browser result, then keep the same address if the work needs a correction.\ \ ## What students actually send\ \ Web hosting for students puts browser-ready coursework and portfolio material on a public address. It is useful when an instructor, teammate or hiring manager needs to open the result without running the source project, installing packages or reaching a local development server.\ \ The submitted artifact depends on the course. A first HTML assignment may be one file and can use single-file HTML hosting. A React or Vite class project needs its built output and the framework guide for the command and output folder. Raw HTML copied from a chat or class exercise can go through HTML to URL without creating a local file first.\ \ Students also publish work that is not a website. A portfolio link can support applications, a resume link can stay current after edits, and a research PDF can open directly in a browser. The free plan keeps one site and does not require a card, but its pages are noindex, so it is suited to direct sharing rather than search discovery.\ \ - **HTML assignment.** A single page or small multi-file site submitted as the browser result rather than as source code alone.\ - **Framework project.** The static dist, build, out or other output folder produced after the project builds successfully.\ - **Portfolio.** Selected class, personal and collaborative work presented for internships, jobs or further study.\ - **Resume.** A PDF or HTML CV at a link that can stay fixed when the document is corrected.\ - **Presentation or research paper.** Slides, a poster, a PDF report or supporting media that should open without a drive-access request.\ - **AI-generated experiment.** HTML, JSX or a built project from an AI tool, checked and understood before it is submitted or shared.\ \ ## The right publishing route for the assignment\ \ Start from the format you have at the deadline. Do not rebuild a finished artifact only to make it fit another uploader.\ \ - **Intro web students.** Publish a first page with HTML hosting or paste it through HTML to URL.\ - **Framework students.** Find the build command and output directory in the framework guide hub.\ - **Internship and job applicants.** Collect work behind a portfolio link and keep the address current.\ - **Graduating students.** Give a current CV its own address with resume to link.\ \ ## What you get\ \ ### Submit the browser result at the level the course expects\ \ A plain HTML assignment should not require a repository deployment, and a framework source tree should not be mistaken for a finished website. The upload path handles both by keeping the static boundary clear.\ \ - A self-contained .html file can be uploaded on its own.\ - A page with relative CSS, images or scripts should be uploaded with those folders intact.\ - A framework project must be built first; the guides identify common output folders.\ \ ### The assignment link survives a correction\ \ A broken path or last-minute typo should not require a new submission address. Re-publish the corrected artifact to the same site and verify it before the deadline.\ \ - The site address remains the same after each deployment.\ - The free plan allows up to 15 publishes a day.\ - Rollback begins on Pro if a later version is worse than the submitted one.\ \ ### Learn the public-file boundary before it becomes an incident\ \ A static build is public browser code. Secrets do not become safe because they are inside JavaScript, and copied project folders often contain files that were never meant for the web.\ \ - Every deployment is checked for a .env file, .git folder and private-key material.\ - API-key patterns in published JavaScript are flagged for review.\ - If a real secret was exposed, remove it and rotate it; a warning cannot revoke it.\ \ ### Keep a portfolio and resume outside the class folder\ \ Coursework can become evidence of what you know when it is presented with context. Host the selected result, explain your contribution and keep personal application material separate from the assignment submission.\ \ - Use portfolio to link for a selected collection of work.\ - Use resume to link for a PDF or HTML CV that will change.\ - Custom domains start on Pro when a professional address is worth adding.\ \ ## What the free plan includes\ \ The free plan can host one active class project, portfolio or resume without a card.\ \ - 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.\ - The same site address remains valid if you fix the project and publish it again.\ \ ## Drive can deliver the files; hosting runs the result\ \ Google Drive is the better handoff when an instructor needs the source ZIP, document comments or a folder of working files. A hosted link is better when the assignment is to open and use the finished website in a browser.\ \ - **What opens.** Droply: The HTML, static site, PDF or portfolio is served as the published result. Google Drive link: A file or folder opens in the Drive viewer and can be downloaded according to permissions.\ - **Running a website.** Droply: HTML, CSS and browser JavaScript run at the site address. Google Drive link: Drive stores and previews files; it is not a static website origin.\ - **Source-file review.** Droply: Only the files you publish are presented. Google Drive link: A shared folder is better when the instructor needs source files and project structure.\ - **Comments and collaboration.** Droply: No document comments or shared editing. Google Drive link: Viewer, Commenter and Editor roles support review of the working file.\ - **Correction.** Droply: Re-publish at the same site address. Google Drive link: Manage versions, then Upload new version, can keep a non-Google file link.\ - **Best fit.** Droply: A browser-ready submission, public portfolio or current direct link. Google Drive link: Source files, folders, comments and collaborative documents.\ \ Google Drive rows checked 8 September 2026 against Google's file-sharing guide and its file-version guide. Sharing roles and product behavior can change. Confirm the required submission format with the instructor.\ \ ## When Droply is the wrong choice\ \ Use the submission system and format the course requires. A public hosted link is not automatically a valid assignment, and it is not a private course space just because nobody has shared the address widely.\ \ - The instructor requires source code, a repository, a ZIP upload or a specific LMS submission. Follow that requirement and treat the hosted link as a supplement.\ - The project needs a database, login, server action or private API key. Use an application host or change the project to a true static export.\ - The work contains private class material, personal data or content you do not have permission to publish. Keep it in the approved school system.\ - 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.\ \ ## Frequently asked questions\ \ ### Is there free web hosting for students? Yes. The free plan hosts one site with HTTPS and no credit card. It is noindex and carries a small badge, so it is designed for direct sharing rather than search visibility. ### How do I submit an HTML assignment as a link? Upload the .html file, choose the address and publish. If it uses separate CSS, images or scripts, upload the whole folder or ZIP; the HTML hosting guide shows the expected structure. ### Can I host a Vite or React class project? Yes after building it. Upload the dist, build or other browser-ready output, not the source tree. Check the framework guides for the exact command and folder. ### Can I publish code from ChatGPT or Claude? Yes when you understand and check the output. A single HTML, JSX or TSX file may take the direct path; a project with package imports needs a build. See AI-generated website hosting. ### Can I fix the project after submitting the URL? Technically yes: re-publishing keeps the same address. Follow the course rules about deadlines and allowed revisions, and do not use same-URL updates to conceal a change the instructor needs recorded. ### Can I use the same account for several class projects? Plan site limits apply. The free plan has 1 site, so archive, replace or upgrade according to the course and whether older projects need to remain available. ### Can I make a student portfolio? Yes. The portfolio guide covers HTML, PDF and image-based work. Add context about your role and do not publish teammates' work without permission. ### Will a free student site appear in Google? No. Free sites are noindex. Search indexing starts on Starter, which may matter later for a public portfolio but is rarely needed for an assignment submitted directly. ### Does Droply grade or collect assignments? No. It only hosts the static files. The LMS, instructor and course rules remain responsible for submission records, grades and access to private material. ### What if the security check finds an API key? Remove it from the browser code and rotate the key immediately if it was real. Client-side JavaScript is public, so a private credential does not belong there even when the repository itself is private.\ \ ## Other audiences\ \ - [Website Hosting for Educators](https://droply.host/for/educators)\ - [Static Hosting for Developers](https://droply.host/for/developers)\ - [Website Hosting for Designers](https://droply.host/for/designers) # Compare --- Source: https://droply.host/alternatives # Droply compared with 10 other static hosts Honest side-by-side comparisons against 10 static site and file hosts. Every claim about a competitor is taken from that competitor's own documentation and carries the date it was read, and every page names, near the top, the readers who should stay where they are. Several of these competitors are cheaper or larger than Droply and the pages say so. ## Upload-and-share hosts The closest products to this one: you bring a finished file or a finished site and they put it on a URL. - [Tiiny Host alternative](https://droply.host/tiiny-host-alternative): The incumbent in this category, and the same drop-a-file idea. Rollback, expiring links, a deploy-time security check and importing a site from its URL are not documented features there, and its entry tier is $9 a month against our $5. - [Static.app alternative](https://droply.host/static-app-alternative): Cheaper than us at the entry tier and strong on content. Its own docs say a loose .html file is not accepted and React artifacts need converting to self-contained HTML first. - [Carrd alternative](https://droply.host/carrd-alternative): A one-page site builder rather than a host: you design in its editor and cannot upload a site you already built. Cheaper than us, and the right answer for a lot of people. ## Drag-and-drop deploys Free front doors to a much larger platform. The drop is quick; what happens to the link afterwards is the part worth reading. - [Netlify Drop alternative](https://droply.host/netlify-drop-alternative): A genuinely good drop tool that can now build your project, redeploy and take a domain. An unclaimed drop is deleted after one hour, and its URL carries a temporary password until you claim it. - [Cloudflare Drop alternative](https://droply.host/cloudflare-drop-alternative): The fastest way to see a folder online, with no account at all. The preview and its throwaway account both disappear after an hour unless you claim them into a Cloudflare account. - [Vercel Drop alternative](https://droply.host/vercel-drop-alternative): Detects and builds your framework project from a drop, which is real. Every drop creates a new project, so an update lands on a new URL rather than the one you already shared. ## Developer platforms Built around a repository and a build. Excellent at that, and a long way round if you already have the finished files. - [GitHub Pages alternative](https://droply.host/github-pages-alternative): Free and hard to beat if your project is already a repository. Its own terms forbid using it to run a business or a SaaS, and a private Pages site requires GitHub Enterprise Cloud. - [Vercel alternative](https://droply.host/vercel-alternative): The right home for a Next.js app with server-side code. Its free Hobby tier is for personal, non-commercial use, and Password Protection is Enterprise or a $150 a month Pro add-on. - [Render alternative](https://droply.host/render-alternative): Free static sites, but only from a connected Git repository, with a build on every push. Hobby includes 5 GB of bandwidth and 500 build minutes, then usage is billed. - [Firebase Hosting alternative](https://droply.host/firebase-hosting-alternative): Free, with 10 GB of storage and a custom domain at no cost. Deploying needs a Firebase project and the CLI, and the free tier caps data transfer at 360 MB a day. --- Source: https://droply.host/tiiny-host-alternative # Tiiny Host alternative with rollback and expiring links Tiiny Host does the core job well and has done it longer than we have: drop a file, get a link. The reasons people look for an alternative are what happens after the drop, and what the tier that fixes it costs. That is what this page is about. ## Who should not switch Moving a live URL is real work and it carries real risk. If any of these describes you, staying put is the better decision and this page has done its job by saying so. - Your Tiiny link works and nothing below describes a problem you actually have. A URL other people already hold is worth more than a feature you will not use. - You rely on Tiiny accepting a .php upload for something that has to run. Droply converts a static .php page to HTML at publish time and never executes it, so anything server-side does not come across. - You are on Solo or above mostly for the five custom domains it allows on one account. Droply prices domains per plan rather than as a pack, so check the pricing page against your domain count first. ## Why people look for a Tiiny Host alternative ### Moving a site means finding the original files There is no documented way to point Tiiny at a site that is already live and have it copied across. Whatever you move has to still exist as a folder or an archive on a machine you own, which is the part that fails: the site is three years old and the laptop it was built on is not. Source: Tiiny Host help center, checked 8 September 2026: no import-from-URL feature is documented. Droply: Site import takes the address of a live site and copies its pages, styles, images and fonts onto a Droply link, up to 40 pages and 600 assets. You need the URL, not the folder, and the original stays exactly where it is. ### A password on one preview costs a whole tier Password protection starts on Solo, $18 a month or $13 a month billed annually. If the only thing you needed was a password on a single client preview, that is what the password costs. Source: Tiiny Host help center, password-protection article, updated 3 September 2026. Droply: Password protection starts on Starter, and the check happens at the edge before any file is served. That means the images, the PDF and the JavaScript bundle are behind it too, not just the front page. ### There is no self-serve way back to the previous version No rollback feature is documented. The recovery path in the help center is contacting support to restore a deleted link, which is a different problem: it gets the address back, not the build you overwrote ten minutes ago. Source: Tiiny Host help center, checked 8 September 2026: no rollback article exists, and the documented recovery route is contacting support about a deleted link. Droply: Every upload becomes an immutable version and publishing points the address at one of them. Rolling back to the previous version is one click from Pro upward, with no ticket and no re-upload. ### Links that should stop working carry on working Expiring links are not a documented feature. A quote, a proof or a salary offer that should have come down after a week stays up until somebody remembers it exists. Source: Tiiny Host help center, checked 8 September 2026: no expiring-links feature is documented. Droply: Auto-expiring links are a setting on the site, from Starter: six hours, a week, or a date you pick. The link stops serving on its own, and publishing to the site again brings it back. ### Nothing reads what you just published No deploy-time security or secret scan is documented. The most common way a static site leaks something is a whole project folder getting zipped instead of the build output, and from the outside that upload looks exactly like a correct one. Source: Tiiny Host help center and product pages, checked 8 September 2026: no deploy-time security or secret scan is documented. Droply: Every publish is read for a committed .env file, a .git directory, a private key, or an API key left in a JavaScript bundle, and the result is written in plain language rather than as a severity score. It is on every plan, free included. See how the check works. ## Droply and Tiiny Host, row by row Both directions. Where Tiiny is equal or ahead, the row says so. - **Free plan.** Droply: 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. Tiiny Host: 1 site, 3 MB per project (0.5 MB for a PDF), 5,000 visits and 5 GB a month. - **Single HTML file, no ZIP.** Droply: Yes, drop the .html on its own. Tiiny Host: Yes, HTML is accepted. - **Single .jsx or .tsx, no build.** Droply: Yes. It is transformed in the visitor browser at the published URL. Tiiny Host: Not offered. - **PDFs and documents.** Droply: Hosted as first-class files, with an in-browser viewer. Tiiny Host: Yes: PDF, image, document, PowerPoint and Excel formats are accepted. - **Security check on every publish.** Droply: Every plan, including free. Tiiny Host: Not documented. - **One-click rollback.** Droply: From Pro. Tiiny Host: Not documented. Support can restore a deleted link. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Tiiny Host: Not documented. - **Password protection.** Droply: From Starter, checked at the edge before any file is served. Tiiny Host: From Solo, $18 a month or $13 a month billed annually. - **Custom domain.** Droply: From Pro, $15 a month. Tiiny Host: From Solo, up to 5 domains per account. - **Import an existing site from its URL.** Droply: Yes, up to 40 pages and 600 assets copied onto a Droply link. Tiiny Host: Not documented. - **Entry paid price, monthly.** Droply: $5 a month for Starter. Tiiny Host: $9 a month for Tiny. Tiiny Host figures come from its own help center, read on 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (2 September 2026), the free-plan link duration article (21 August 2026), the password-protection article (3 September 2026) and the custom-domains guide (7 September 2026). Rows marked "not documented" mean the feature does not appear in that help center on that date, not that we tested and it failed. Product plans can change. ## How to move a site from Tiiny Host Your Tiiny link keeps working throughout. Nothing here needs a support ticket on either side, and the DNS change goes last so there is never a moment where your domain points at nothing. 1. **Download what Tiiny is serving.** Open the project in your Tiiny dashboard and download it. Take the copy Tiiny is serving rather than an older local folder: the live one is the version people are actually looking at. 2. **Or skip the download and paste the address.** Droply Site Importer takes the URL of a site that is already live and copies its pages, styles, images and fonts onto a Droply link, up to 40 pages and 600 assets. It is the faster route when the original folder is long gone. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared This is the clearest section on the page. Paid monthly, Droply is the cheaper of the two; paid annually the two are the same price. List prices only on both sides: Droply runs promotions from time to time and Tiiny attaches a 7-day money-back guarantee to every paid plan, and neither of those is a list price. - **Free.** Droply: 1 site, 25 MB, 5,000 visits a month, no card. Tiiny Host: 1 site, 3 MB per project (0.5 MB for a PDF), 5,000 visits a month. - **Entry paid tier, billed monthly.** Droply: $5 a month for Starter. Tiiny Host: $9 a month for Tiny. - **Entry paid tier, billed yearly.** Droply: $60 a year for Starter. Tiiny Host: $5 a month billed annually, so $60 a year. - **First tier with a custom domain.** Droply: Pro, $15 a month. Tiiny Host: Solo, $18 a month or $13 a month billed annually. - **Top published tier.** Droply: See the pricing page for the full ladder. Tiiny Host: Pro Max, $89 a month or $74 a month billed annually. Tiiny Host prices from its pricing-plans help article, updated 1 September 2026 and read on 8 September 2026. Droply prices are read live from the plans table on this page, so they cannot go stale here. Product plans can change. ## What you get without paying anything If you are on a free Tiiny link today, this is the like-for-like list, including the two lines Tiiny has no equivalent for: the security check and site import. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - Site import, so an existing link can be copied across without finding the original files. ## Frequently asked questions ### Is Droply free? Yes. The free plan is 1 live site with 25 MB of storage, 5,000 visits and 5 GB of traffic a month, HTTPS included, no card. It is a plan in its own right rather than a trial of a paid one. ### Is Droply a good Tiiny Host alternative? It is if the things you want are rollback, expiring links, a security check on every publish, or importing a site straight from its URL, because Tiiny documents none of those, and it is if you pay monthly, where Starter is $5 against $9. It is not if you need PHP to execute or you are already paying for its five-domain allowance. ### Can I import my site from Tiiny Host? Yes. Paste the live Tiiny URL into site import and Droply copies its pages, styles, images and fonts onto a Droply link, up to 40 pages and 600 assets. You do not need the original folder, and your Tiiny link is untouched. ### Will my Tiiny link keep working while I move? Yes. Nothing in the move touches your Tiiny account. Publish on Droply first, check it renders, and only then change the DNS record if you are bringing a custom domain across. ### What does Tiiny Host do that Droply does not? It accepts .php uploads, and its Solo tier allows up to five custom domains on one account. Droply converts a static .php page to HTML at publish time and never runs it, and prices domains per plan rather than as a pack. ### How much is Droply compared with Tiiny Host? Paid monthly, Droply is cheaper: $5 a month for Starter against $9 for Tiny. Paid annually the two match at $60 a year. Custom domains start on Pro here at $15 a month, and on Solo there at $18 a month, which is the row where Tiiny costs more. ### Can I password-protect a site on the free plan? No, on either service. Password protection starts on Starter here and on Solo at Tiiny. The difference is what the password covers: here the check runs at the edge, so assets and documents sit behind it as well as the page. ### Does Droply put a badge on my site like Tiiny does? Yes, on the free plan. A small badge sits in the corner of the page and removing it starts on Starter. Both services do this; neither hides it. ### Can I go back to a previous version after a bad upload? Yes, from Pro. Each upload is kept as its own immutable version and rolling back points the address at an earlier one in a click. Tiiny documents no self-serve equivalent. ## Other comparisons - [Static.app alternative](https://droply.host/static-app-alternative) - [Netlify Drop alternative](https://droply.host/netlify-drop-alternative) - [Carrd alternative](https://droply.host/carrd-alternative) --- Source: https://droply.host/static-app-alternative # Static.app alternative that takes the file you are holding Static.app is a good product and its entry tier is cheaper than ours. The reason people look for an alternative is narrower than price: its own documentation says a loose .html file is not accepted and a React artifact has to be converted first. Both work here as they are. ## Who should not switch Static.app wins on two things that are easy to measure, and if either is what you are optimising for, it is the better buy. - Sites and a domain per dollar. Its Starter tier is $5 a month, or $60 a year, for two sites WITH a custom domain, and Large is $15 a month for thirty. Starter here is $5 a month for one site, and custom domains start on Pro. On that row Static.app wins and this page is not going to pretend otherwise. - It ships a macOS desktop app, listed on its free tier. Droply is browser, API, a Chrome extension and a VS Code extension, with no native desktop app. - You always ZIP your uploads anyway and never touch React. Then the two frictions this page is built on do not apply to you, and the comparison comes down to price. ## Why people look for a Static.app alternative ### A loose .html file is not accepted Its own Claude hosting page says a loose .html file is not accepted for upload and has to be zipped first. That is a real step: an AI tool or a text editor hands you one file, and the next thing you do is open an archive utility. Source: Static.app Claude hosting page, read 8 September 2026. Droply: Drop the .html on its own. It becomes the page at the root of the site, with no archive, no folder and no index.html rename. The same is true of a PDF, an image or an office document. ### A React artifact needs converting before it can go up The same page says React-based artifacts need an extra step: ask Claude for a self-contained HTML version first. That is a round trip through the model, and the version you publish is then not the version you reviewed. Source: Static.app Claude hosting page, read 8 September 2026. Droply: A single .jsx or .tsx file is published as it is and transformed in the visitor browser at the URL. Nothing regenerates it and nothing rewrites it, so what you read is what a visitor gets. See publishing a Claude artifact. ### The free column and the trial are the same column Its pricing page lists a $0 tier with 1 website and 50 MB, and lists "7-Day Trial" among that tier's own features, while its copy elsewhere says the first 7 days are free with no credit card. Read that page yourself before you plan around the $0 column. Source: Static.app pricing page, read 8 September 2026. We are quoting an ambiguity on their page rather than resolving it for them. Droply: The free plan is a plan rather than a trial of a paid one: 1 site, 25 MB, 5,000 visits and 5 GB a month. There is no seventh day and no card on file to start charging. ### No password protection on any listed plan Password protection does not appear on any tier of its pricing page. For a client preview or an internal document that is the difference between a link you can send and a link you cannot. Source: Static.app pricing page, read 8 September 2026: no password or access-control feature is listed on any plan. Droply: Password protection starts on Starter and is checked at the edge, before any file is served, so the assets behind the page are covered as well as the page. ## Droply and Static.app, row by row Static.app is ahead on price and on sites per tier. Those rows are here too. - **Free plan.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, no card. Static.app: A $0 tier listed with 1 site and 50 MB, whose own feature list also names a 7-day trial. - **Single .html file, no ZIP.** Droply: Yes. Static.app: No. Its Claude page says a loose .html file is not accepted and must be zipped. - **Single .jsx or .tsx, no build.** Droply: Yes, transformed in the visitor browser. Static.app: No. Its Claude page says React artifacts need converting to self-contained HTML first. - **PDFs and documents.** Droply: Hosted as first-class files, with an in-browser viewer. Static.app: Not described as a product feature on its pricing page. - **Password protection.** Droply: From Starter, checked at the edge. Static.app: Not listed on any plan. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Static.app: Not listed on any plan. - **One-click rollback.** Droply: From Pro. Static.app: Not listed on any plan. - **Security check on every publish.** Droply: Every plan, including free. Static.app: Not listed on any plan. - **Sites on the entry paid tier.** Droply: See the pricing page: the count rises with the tier. Static.app: 2 on Starter, 7 on Medium, 30 on Large. - **Custom domain.** Droply: From Pro, $15 a month. Static.app: From Starter, $5 a month or $60 a year. - **Entry paid price.** Droply: $5 a month for Starter. Static.app: $5 a month, or $60 a year. Static.app figures come from its own pricing page and its Claude hosting page, both read on 8 September 2026. Rows marked "not listed" mean the feature does not appear on those pages on that date, not that we tested it. Product plans can change. ## How to move a site from Static.app Your Static.app site stays up while you do this. If you still have the ZIP you uploaded there, you already have everything you need. 1. **Find the archive you uploaded, or the folder you made it from.** Static.app takes a ZIP, so the thing you originally uploaded is a complete copy of the site. Either the ZIP or the folder it was built from will publish here unchanged. 2. **Or paste the live address instead.** Site import copies the pages, styles, images and fonts of a live site onto a Droply link, up to 40 pages and 600 assets. Use it when the archive is gone or was built on a machine you no longer have. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared List prices on both sides. The two entry tiers are the closest thing to a like-for-like row on this page, and Static.app wins it: at its entry price you get two sites and a custom domain, where Starter here gives one site and puts custom domains on Pro. What you are paying us for instead is on the table above. - **Free.** Droply: 1 site, 25 MB, 5,000 visits a month, no card. Static.app: A $0 tier: 1 site, 50 MB, SSL, QR codes, and a 7-day trial listed in the same column. - **Entry paid tier.** Droply: $5 a month for Starter. Static.app: $5 a month or $60 a year for Starter: 2 sites, 500 MB, custom domain. - **Middle tier.** Droply: See the pricing page. Static.app: $10 a month for Medium: 7 sites, 3 GB. - **Top published tier.** Droply: See the pricing page. Static.app: $15 a month for Large: 30 sites, 10 GB. Static.app prices from its own pricing page, read 8 September 2026. Droply prices are read live from the plans table, so they cannot go stale on this page. Product plans can change. ## What you get without paying anything The free plan here is a plan rather than a seven-day window, and this is what it holds. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - A loose .html, .jsx or .tsx file published as it is, with nothing to zip or convert first. ## Frequently asked questions ### Is Droply free? Yes. 1 site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card, and no trial clock. ### Is Droply a good Static.app alternative? It is if you are holding a loose .html file or a React artifact, because Static.app documents that both need a step first. It is not if you are buying sites and a custom domain at the entry price: Static.app gives two sites and a domain for $5 a month, and Starter here gives one site with domains from Pro. ### Can I import my site from Static.app? Yes, two ways. Re-upload the ZIP you gave Static.app, or paste the live URL into site import and let Droply copy up to 40 pages and 600 assets onto a Droply link. ### What does Static.app do that Droply does not? It gives you more sites for the money at every paid tier, includes a custom domain from its entry tier, and ships a macOS desktop app. Droply has no native desktop app; it has a browser upload, a public API, a Chrome extension and a VS Code extension. ### Can I really publish a single HTML file with no ZIP? Yes. Drop the .html and it becomes the page at the root of the site. Static.app's own Claude page says a loose .html file is not accepted there and has to be zipped first. ### Does a React file need converting before I publish it? Not here. A single .jsx or .tsx is published as written and transformed in the visitor browser at the URL. A project with real package imports still needs its build run first; the framework guides give the command and the output folder. ### Can I password-protect a site? Yes, from Starter. The password is checked at the edge before any file is served, so the images, PDFs and scripts are behind it too. No password feature is listed on any Static.app plan. ### Is the Static.app free tier a plan or a trial? Read their pricing page and decide for yourself. It lists a $0 tier with 1 site and 50 MB, and lists a 7-day trial among that same tier's features, which is why this page does not state it either way. ### How many sites can I host on Droply? One on the free plan, and more on each paid tier. The pricing page lists the count per plan. Static.app allows 2 on Starter, 7 on Medium and 30 on Large. ## Other comparisons - [Tiiny Host alternative](https://droply.host/tiiny-host-alternative) - [Carrd alternative](https://droply.host/carrd-alternative) - [Netlify Drop alternative](https://droply.host/netlify-drop-alternative) --- Source: https://droply.host/carrd-alternative # Carrd alternative for a site you have already built Carrd is a one-page site builder: you design inside its editor. Droply is a host: you bring finished files and we serve them. If you want to design in a browser, Carrd is the better tool and it is cheaper. This page is for the other case. ## Who should not switch Most people searching for a Carrd alternative want a different builder, and Droply is not one. Read this list first; if you are in it, we are the wrong tool and there is nothing further down this page that changes that. - You do not have any files and do not want any. Carrd gives you a canvas; Droply gives you a URL for a folder you already have. - Price is the deciding factor. Carrd is $9 a year for Pro Lite and $19 a year for Pro Standard, which is the first tier with a custom domain. Droply is priced per month and does not compete with that. - You want built-in forms, an editor your client can use, or a template gallery to start from. Droply has starter templates and an AI page builder, but neither is a drag-and-drop visual editor. ## Why people look for a Carrd alternative ### You cannot bring a site you already built Carrd builds the site for you inside its own editor. There is no upload path for an HTML file, a folder or a ZIP you produced somewhere else, so a design that exists as code has to be rebuilt by hand in its interface. Source: Carrd documentation, plans and features pages, read 8 September 2026: the workflow described throughout is building inside the editor. Droply: Upload is the entire product. A single .html file, a folder, a ZIP of a built site or a single .jsx all publish as they are, and what we serve is byte for byte what you gave us. ### One page per site Carrd is built around one-page sites, which is a genuine design choice and works well for a link page, a launch page or a profile. It stops working the moment you need a second URL under the same site. Source: Carrd product pages, read 8 September 2026: the product is described throughout as one-page sites. Droply: A site is a folder, so it has as many pages as your folder has, with the paths you gave them. If a one-page link hub is what you actually want, the link-in-bio builder here is free including every design control. ### A PDF or a deck is not a Carrd site Carrd builds pages. A proposal, a menu, a report or a slide deck is not a page you can build there, so a document still needs somewhere else to live and a second link to send. Source: Carrd product and documentation pages, read 8 September 2026: document hosting is not offered as a site type. Droply: PDFs, images, media and office documents are first-class: they get their own URL and render in the browser rather than downloading. See turning a PDF into a link. ### Getting your work back out is a top-tier feature Downloading the unminified sources of the sites you build sits on Pro Plus, $49 a year, per its own plans page. Until then the design lives inside Carrd, which matters when the question is what happens if you leave. Source: Carrd plans documentation, read 8 September 2026. Droply: You already have your files, because you uploaded them. Nothing here holds the only copy of anything you made, on any plan. ## Droply and Carrd, row by row These are different products, so most rows are a difference in kind rather than a win. Carrd is cheaper and that row is here. - **What you bring.** Droply: Finished files: HTML, a folder, a ZIP, a PDF, a single .jsx. Carrd: An idea. You build the site in its editor. - **Upload a site you already built.** Droply: Yes, that is the whole product. Carrd: Not an upload path. - **Pages per site.** Droply: As many as your folder contains. Carrd: One-page sites. - **PDFs and documents.** Droply: Hosted as first-class files, with an in-browser viewer. Carrd: Not a site type. - **Visual drag-and-drop editor.** Droply: No. There is an AI page builder and a link-in-bio builder, neither of which is a canvas. Carrd: Yes, and it is the reason to use it. - **Free plan.** Droply: 1 site with a small badge until Starter. Carrd: 3 sites with a "Made with Carrd" badge. - **Custom domain.** Droply: From Pro, $15 a month. Carrd: From Pro Standard, $19 a year. - **Getting your work out.** Droply: You uploaded it, so you already have it, on every plan. Carrd: Downloading unminified sources is a Pro Plus feature, $49 a year. - **Billing options.** Droply: Monthly or yearly. Carrd: Annual only, per its plans page. - **Password protection.** Droply: From Starter, checked at the edge. Carrd: Not listed on its plans page. - **Entry paid price.** Droply: $5 a month for Starter. Carrd: $9 a year for Pro Lite. Carrd figures come from its own documentation, read on 8 September 2026: the Pro plans page and the custom-domain guide, which states "Requires Pro Standard or higher". Rows marked "not listed" mean the feature does not appear on those pages on that date. Product plans can change. ## How to move a site from Carrd This is the one migration on the site that can genuinely lose work, because the design lives in Carrd rather than in a folder on your machine. Read step one before you cancel anything. 1. **Get the files out first, and check them.** Downloading the unminified sources of your sites is a Pro Plus feature at $49 a year. If you are not on it, decide whether the export is worth one year at that tier before you cancel: after cancellation the export path is gone and the site is what you can see in a browser. 2. **Or copy the live page instead.** Site import takes the address of your published Carrd site and copies its pages, styles, images and fonts onto a Droply link, up to 40 pages and 600 assets. It is a copy of what is served, not the editable original, so check it renders before you rely on it. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared Carrd is annual and cheap, Droply is monthly and is not competing at that number. Comparing them straight across is misleading, so the rows say what each price actually buys. - **Free.** Droply: 1 site, 25 MB, 5,000 visits a month, no card. Carrd: 3 one-page sites on a carrd.co subdomain with a "Made with Carrd" badge. - **Entry paid tier.** Droply: $5 a month for Starter. Carrd: $9 a year for Pro Lite: 3 sites, badge removed. - **First tier with a custom domain.** Droply: Pro, $15 a month. Carrd: Pro Standard, $19 a year: 10 sites. - **Top published tier.** Droply: See the pricing page for the full ladder. Carrd: Pro Plus, $49 a year: 25 sites, custom forms, source download. Carrd prices from its own Pro plans documentation, read 8 September 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything If you already have files, this is what publishing them costs on the free plan. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - A multi-page site, with the folder structure and the paths you built. ## Frequently asked questions ### Is Droply a good Carrd alternative? Only if you already have the files. Carrd builds a site for you inside its editor; Droply hosts one you built somewhere else. If you want a canvas rather than an upload box, Carrd is the right tool and it costs less. ### Can I upload an HTML file to Carrd? No, per its documentation: sites are built in its editor rather than uploaded. That is the single clearest reason someone ends up on this page. ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card. Carrd's free tier is three one-page sites with its badge. ### Which is cheaper, Droply or Carrd? Carrd, clearly. Pro Lite is $9 a year and Pro Standard, the first tier with a custom domain, is $19 a year. Droply is billed monthly from $5 for Starter, and does not try to match those numbers. ### Can I move my Carrd site to Droply? Partly. Site import copies your published page, its styles, images and fonts onto a Droply link. It copies what is served, not the editable Carrd project, so treat it as a snapshot and check it before relying on it. ### Can I build a multi-page site? Yes. A site here is a folder, so it has whatever pages and paths your folder has. Carrd is deliberately one-page, which is a design choice rather than a limitation of the same kind. ### Does Droply have a page builder? It has two, and neither is a visual canvas: an AI builder that writes a page from a description, and a link-in-bio builder whose design controls are all free. Neither is a drag-and-drop editor like Carrd's. ### Can I host a PDF or a slide deck? Yes, as its own link that renders in the browser. That is not something Carrd does: it builds pages, so a document needs a second service and a second link. ### What happens to my site if I stop paying? You keep your files either way, because you uploaded them. The site drops back to free-plan limits rather than disappearing. On Carrd, downloading the unminified sources of what you built is a Pro Plus feature at $49 a year. ## Other comparisons - [Tiiny Host alternative](https://droply.host/tiiny-host-alternative) - [Static.app alternative](https://droply.host/static-app-alternative) - [GitHub Pages alternative](https://droply.host/github-pages-alternative) --- Source: https://droply.host/netlify-drop-alternative # Netlify Drop alternative with no hour to beat Netlify Drop got its biggest refresh in years in July 2026 and it is good: it can build what you drop, redeploy to the same site and take a custom domain. The catch is the one hour an unclaimed drop lives, and the fact that Drop is a doorway into a platform rather than the product. ## Who should not switch Netlify is a build platform with a drop tool attached, and the build platform is very good. If you are using it as intended, nothing here is an argument. - Your project is in Git and you want a deploy on every push, with a preview URL per branch. Droply has no Git integration and no CI, on purpose. - You want Netlify to run the build. Drop will detect and build a project you drop on it; Droply never runs your build and never will, so you build locally and upload the output. - You use functions, edge functions, forms or identity. Those are platform features with no equivalent here, because Droply serves files and does not execute anything of yours. ## Why people look for a Netlify Drop alternative ### An unclaimed drop has one hour Netlify's own docs say a drop made without signing in "creates a temporary project with a live URL that you can claim within one hour". Miss the hour and the site is gone, along with the URL you may already have pasted somewhere. Source: Netlify docs, Drop quickstart, read 8 September 2026. Droply: There is no anonymous drop and therefore no clock. Publishing requires an account here deliberately, so the link belongs to somebody from the first second: there is nothing to claim, and no hour in which claiming it is possible. ### The unclaimed URL is password-protected anyway The quickstart also says an unsigned-in drop's "project URL is protected with a temporary password until you claim it". So the fastest path still cannot be handed to a client without signing in and relaying a password first. Source: Netlify docs, Drop quickstart, read 8 September 2026. Droply: Sign in once, publish, send the URL. There is no interstitial password to pass along, and if you WANT one it is a real setting from Starter rather than a side effect of not having an account. ### The size guidance is a soft one, and it fails late The docs say deploys under 50 MB work best, warn that individual files over 10 MB "may cause your deploy to get stuck", and recommend the CLI for larger projects. A stuck deploy is a worse failure than a refused one, because you find out by waiting. Source: Netlify docs, Drop and create-deploys pages, read 8 September 2026. Droply: The limit is your plan's upload limit, it is printed on the pricing page, and an upload over it is refused with the number before anything is stored. Nothing gets stuck, and the same number applies however you upload. ### Password protection is a Pro-tier feature Netlify's pricing page puts password-protected projects on Pro, $20 a month. Basic authentication headers appear lower down the ladder, which is a different mechanism and a different experience for the person you send the link to. Source: Netlify pricing page, read 8 September 2026 (page updated 5 September 2026). Droply: Password protection starts on Starter, and the check runs at the edge before any file is served, so images, PDFs and scripts are behind it as well as the page. ### Drop is a doorway, not the product Netlify's own framing is that Drop is a way into its Git platform: the docs point you at the CLI for larger projects and at the Git integration for anything ongoing. That is fine, and it means the product is optimised for people who will eventually connect a repository. Source: Netlify docs and blog, Drop refresh of 27 July 2026, read 8 September 2026. Droply: Uploading is the product. There is no next step you are being nudged toward, no repository to connect, and the fifth upload works exactly like the first. ## Droply and Netlify Drop, row by row Netlify is ahead on several of these. Those rows are here in full. - **Free plan.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, no card. Netlify Drop: A 300-credit monthly allowance with an account, announced as 100 GB bandwidth and 300 build minutes. - **Deploying without an account.** Droply: Not possible. Every site has an identified owner. Netlify Drop: Yes, and the temporary project is deleted after one hour unless claimed. - **The link you can send immediately.** Droply: The published URL, straight away. Netlify Drop: An unclaimed drop's URL carries a temporary password until you claim it. - **Runs your build for you.** Droply: No, and this is a deliberate limit. Build locally, upload the output. Netlify Drop: Yes. Drop detects and builds a project you drop on it. - **Single HTML file.** Droply: Yes, drop the .html on its own. Netlify Drop: Its quickstart documents a project folder, a zip, or a pre-built output folder. - **Single .jsx or .tsx, no build.** Droply: Yes, transformed in the visitor browser. Netlify Drop: Not offered as a path; it would be built as a project. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. Netlify Drop: Servable as static assets, not a product feature. - **Rollback to an earlier deploy.** Droply: From Pro, one click. Netlify Drop: Yes. Publishing a previous deploy is supported and instantaneous. - **Password protection.** Droply: From Starter, checked at the edge. Netlify Drop: Password-protected projects from Pro, $20 a month. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Netlify Drop: Not offered. - **Security check on every publish.** Droply: Every plan, including free. Netlify Drop: Not offered. - **Entry paid price.** Droply: $5 a month for Starter. Netlify Drop: $9 a month for Personal; $20 a month for Pro. Netlify figures come from its own documentation, pricing page and changelog, read on 8 September 2026: the Drop quickstart and create-deploys pages, the pricing page (updated 5 September 2026), the free-plan announcement, and the Drop refresh of 27 July 2026. The claim that Drop can build a dropped project comes from current product documentation rather than a version-stamped changelog entry, and it is a claim in Netlify's favour. Product plans can change. ## How to move a site from Netlify If the site came from a repository, you already have everything: run the build and upload the output folder. If it came from a drop, get the files before you delete anything. 1. **Run your build one more time.** Whatever Netlify was running for you, run locally. The framework guides give the exact command and output folder for 23 frameworks, which is the only part of a Netlify build configuration that matters here. 2. **Or download the deploy, or copy the live URL.** A deployed site can be downloaded from the Netlify UI, and site import will copy a live site's pages, styles, images and fonts onto a Droply link, up to 40 pages and 600 assets, without touching the original. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared These ladders are not shaped the same: Netlify meters a credit allowance across builds, bandwidth and functions, while Droply sells a plan with fixed limits. The rows below compare the entry points rather than pretending the middles line up. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, no card. Netlify Drop: 300 credits a month, announced as 100 GB bandwidth and 300 build minutes. Sites are suspended for the rest of the month if the allowance runs out. - **Entry paid tier.** Droply: $5 a month for Starter. Netlify Drop: $9 a month for Personal. - **First tier with password protection.** Droply: Starter. Netlify Drop: Pro, $20 a month. - **What the money is buying.** Droply: Serving capacity and features. No build ever runs, so nothing is metered for compute. Netlify Drop: Build minutes, function invocations and bandwidth, metered together as credits. Netlify prices and allowances from its own pricing page (updated 5 September 2026) and free-plan announcement, read 8 September 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything No claim window, no temporary password on the URL, and no build minutes to run out of. This is the whole free plan. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - A link that is yours from the moment it is published, with nothing to claim. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card. There is no credit allowance to run out of and no suspension at the end of the month. ### Is Droply a good Netlify Drop alternative? It is if you want the link to be yours from the first second, with nothing to claim, and you are not going to connect a repository. It is not if you want Netlify to run your build, give you a preview per branch, or host functions. ### Does Droply delete my site if I do not claim it? No. There is no anonymous deploy here, so there is nothing to claim and no hour in which to claim it. You sign in first, and the site is live from the moment you publish it. ### Can I import my site from Netlify? Yes. Either run your build locally and upload the output folder, or paste the live URL into site import and let Droply copy up to 40 pages and 600 assets onto a Droply link. ### What does Netlify do that Droply does not? It builds your project, deploys on every Git push, gives a preview URL per branch, and runs functions and forms. Droply does none of those: it serves the files you upload and nothing else. ### Can I roll back a bad deploy? Yes, from Pro, in one click. Netlify supports this too and publishing a previous deploy there is instantaneous, so this row is close to a draw. ### Can I password-protect a site? Yes, from Starter. The check runs at the edge before any file is served, so assets are covered as well as the page. On Netlify, password-protected projects start on Pro at $20 a month. ### Is there a size limit on what I can upload? Yes, your plan's upload limit, listed on the pricing page. An upload above it is refused with the number rather than accepted and stalled, which is the failure mode Netlify's docs warn about for files over 10 MB. ### Can I set a link to expire? Yes, from Starter: six hours, a week, or a date. The site stops serving on its own and comes back if you publish to it again. Netlify has no equivalent setting. ## Other comparisons - [Vercel Drop alternative](https://droply.host/vercel-drop-alternative) - [Cloudflare Drop alternative](https://droply.host/cloudflare-drop-alternative) - [Tiiny Host alternative](https://droply.host/tiiny-host-alternative) --- Source: https://droply.host/cloudflare-drop-alternative # Cloudflare Drop alternative for a link that has to last Cloudflare Drop launched in July 2026 and needs no account at all, which is genuinely the fastest way to see a folder on the internet. The preview lives for one hour. This page is about what you use when the link has to outlive the hour and hold something other than a website. ## Who should not switch This is the comparison where the honest answer favours the competitor most often. Cloudflare's free tier is more generous than ours by every number that can be counted, and its network is the best in this list. - You are willing to claim the deployment into a free Cloudflare account. What you get is a Cloudflare Pages project: 20,000 files per site, 500 builds a month and up to 100 custom domains per project, at no cost. Droply does not undercut that. - You are already on Cloudflare for DNS. Keeping the site on the same account as the domain removes a step that this page cannot remove for you. - Raw delivery performance is the deciding factor. Cloudflare's network is larger than ours and this page is not going to pretend otherwise. ## Why people look for a Cloudflare Drop alternative ### One hour, then the deployment and the account both go Cloudflare's launch notes are explicit: the preview stays live for an hour, and after that the deployment and its throwaway account both disappear. That is a fine demo and a bad way to send a client a link on a Friday afternoon. Source: Cloudflare changelog, Drop launch, 8 July 2026, read 8 September 2026. Droply: There is no anonymous path and therefore no window. You sign in, publish, and the URL is live immediately, with no throwaway account behind it and nothing to rescue within the hour. ### Static assets only, so documents have nowhere to go Drop accepts static assets: HTML, CSS, JavaScript, images and fonts. A proposal, a menu, a report or a deck is not on that list, so the document still needs a different service and a second link. Source: Cloudflare changelog, Drop launch, 8 July 2026, read 8 September 2026. Droply: PDFs, images, media and office documents are first-class here: each gets its own URL and renders in the browser instead of downloading. See turning a PDF into a link. ### A single HTML file was not accepted at launch At launch Drop took a folder or a ZIP, not a loose .html file. When what you are holding is one file from an AI tool or an editor, that is an archive step before you can do anything. Source: Cloudflare changelog, Drop launch, 8 July 2026, read 8 September 2026. Cloudflare may have changed this since launch; check before relying on it. Droply: Drop the .html on its own and it becomes the page at the root. A single .jsx or .tsx works the same way, transformed in the visitor browser with no build. ### Sites are public by default and there is no password option Drop sites are public by default and no password option is documented for it. Anything you would rather not have found has to be protected some other way, or not put there. Source: Cloudflare changelog and Drop documentation, read 8 September 2026: no password or access-control option is documented for Drop. Droply: Password protection starts on Starter and is enforced at the edge before any file is served, so the assets are behind it and not only the page. Free sites are also served noindex so search engines do not list them. ### There was no API at launch Drop had no API when it launched, so it is a browser action and nothing else. Anything scripted has to go through Wrangler and Pages instead, which is a different product with a different setup. Source: Cloudflare changelog, Drop launch, 8 July 2026, read 8 September 2026. Droply: The same deploy exists as a public REST API, a Chrome extension and a VS Code extension, and the API and the upload box publish to the same site at the same URL. ## Droply and Cloudflare Drop, row by row Cloudflare is ahead on the free-tier numbers once a deployment is claimed, and those rows say so. - **Account needed to start.** Droply: Yes, always. Every site has an identified owner. Cloudflare Drop: No. A throwaway account is created for you. - **How long an unclaimed link lasts.** Droply: Not applicable. Nothing is unclaimed. Cloudflare Drop: One hour, then the deployment and the throwaway account both disappear. - **Single HTML file.** Droply: Yes. Cloudflare Drop: Not at launch: a folder or a ZIP. - **Single .jsx or .tsx, no build.** Droply: Yes, transformed in the visitor browser. Cloudflare Drop: Not offered. No build step runs. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. Cloudflare Drop: Static assets only: HTML, CSS, JavaScript, images, fonts. - **Files per upload.** Droply: Bounded by your plan's upload size, not a file count. Cloudflare Drop: 1,000 per upload; 20,000 per site once claimed as a Pages project. - **Per-file size.** Droply: Bounded by your plan's upload limit. Cloudflare Drop: 25 MiB per file. - **Password protection.** Droply: From Starter, checked at the edge. Cloudflare Drop: Not documented for Drop. Sites are public by default. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Cloudflare Drop: Only the involuntary kind: the one-hour window on an unclaimed drop. - **API.** Droply: Public REST API, plus Chrome and VS Code extensions. Cloudflare Drop: None at launch. Wrangler and Pages are the scripted path. - **Custom domain.** Droply: From Pro, $15 a month. Cloudflare Drop: Free, once claimed into a Cloudflare account, up to 100 per Pages project. - **Security check on every publish.** Droply: Every plan, including free. Cloudflare Drop: Not offered. Cloudflare figures come from its own changelog entry for the Drop launch, dated 8 July 2026, and the Cloudflare Pages limits documentation, both read on 8 September 2026. Launch-day limitations may have changed since; check Cloudflare's own pages before relying on any row marked "at launch". Product plans can change. ## How to move a site from Cloudflare Drop If the drop is still inside its hour, do this now rather than after. If it was claimed into a Pages project, nothing is urgent and you have the repository or the folder already. 1. **Find the folder you dropped.** Drop takes a folder or a ZIP from your machine, so the source is still on your machine. That is the thing to upload here; nothing has been transformed in between. 2. **If it was claimed, take the Pages build output.** A claimed drop becomes a Cloudflare Pages project. Use the same output folder Pages was serving. The framework guides name the build command and output folder for 23 frameworks if you need to regenerate it. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared This is the section where Cloudflare wins outright, so it is worth being precise about what you are paying for here rather than blurring it. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, no card. Cloudflare Drop: Free, and larger: a claimed Pages project allows 20,000 files, 500 builds a month and up to 100 custom domains. - **Custom domain.** Droply: From Pro, $15 a month. Cloudflare Drop: Included at no cost once the deployment is claimed. - **What the money buys here.** Droply: Password protection, expiring links, rollback, analytics, document hosting and search visibility, none of which Drop offers at any price. Cloudflare Drop: Not applicable: Drop is free and has no paid tier of its own. - **Entry paid price.** Droply: $5 a month for Starter. Cloudflare Drop: No paid Drop tier. Cloudflare Pages Pro sits on the wider Cloudflare plan ladder. Cloudflare Pages free-tier limits from the Cloudflare Pages limits documentation, read 8 September 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything Nothing here expires after an hour, and documents count as sites. This is what the free plan holds. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - PDFs, images and office documents, each with its own URL and an in-browser viewer. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card. It is not a preview and there is nothing to claim. ### Is Droply a good Cloudflare Drop alternative? It is if the link has to last, needs a password, holds a document, or has to be created by a script. It is not if you want the largest free tier: a claimed Cloudflare Pages project is more generous than our free plan on every countable number. ### How long does a Cloudflare Drop link last? One hour, per Cloudflare's own launch notes, after which the deployment and the throwaway account created for it both disappear. Claiming it into a Cloudflare account within that hour turns it into a Pages project that persists. ### Can I host a PDF on Cloudflare Drop? Not as a product feature. Drop accepts static assets: HTML, CSS, JavaScript, images and fonts. Here a PDF is a first-class file with its own link and an in-browser viewer. ### Can I publish a single HTML file? Yes, here. Drop the .html on its own and it becomes the root page. Cloudflare Drop took a folder or a ZIP at launch rather than a loose file. ### Can I password-protect a site? Yes, from Starter, checked at the edge before any file is served. No password option is documented for Cloudflare Drop, and its sites are public by default. ### Does Droply have an API? Yes, a public REST API, plus a Chrome extension and a VS Code extension. Cloudflare Drop had no API at launch; scripted deploys there go through Wrangler and Pages. ### What does Cloudflare do that Droply does not? It deploys without an account, runs on a larger network, and its free Pages tier allows far more files, builds and custom domains than our free plan. It also connects a custom domain at no cost. ### Will my site show up in Google? Only on a paid plan. Free Droply sites are served noindex on purpose, because free subdomains on a shared domain are what spam farms are built from. Search visibility starts on Starter. ## Other comparisons - [Netlify Drop alternative](https://droply.host/netlify-drop-alternative) - [Vercel Drop alternative](https://droply.host/vercel-drop-alternative) - [GitHub Pages alternative](https://droply.host/github-pages-alternative) --- Source: https://droply.host/vercel-drop-alternative # Vercel Drop alternative that updates the same URL Vercel Drop will detect your framework and build it, which is more than we do. Its own documentation also says every drop creates a new project and that Drop cannot redeploy into an existing one, so the second version of your site is at a second address. ## Who should not switch Vercel Drop does one thing this product deliberately does not, and if you need it, none of the rest matters. - You want the host to build your project. Drop detects your framework and builds it. Droply never runs a build: you run it locally and upload the output. - The site is a Next.js app with server-rendered routes, API routes or middleware. Those need Vercel or another Node host. Only a fully static export can be published here. - You are going to connect the project to Git afterwards anyway. Then the new-project-per-drop rule below stops being a problem after the first push. ## Why people look for a Vercel Drop alternative ### Every drop is a new project, so every update is a new URL The limitations in Vercel's own Drop documentation are direct: "Each drop creates a new project. Vercel Drop doesn't redeploy into an existing project." Version two of the site is therefore at a different address from the one you already sent to a client. Source: Vercel docs, Deploying with Vercel Drop, page last updated 16 June 2026, read 8 September 2026. Droply: Re-uploading publishes a new immutable version and points the same address at it. The URL never moves, so links you already sent, bookmarks and printed QR codes all keep resolving to the current version. ### The free tier is for personal, non-commercial use Vercel's pricing page says "Our Hobby plan is for personal, non-commercial use." A client preview, a freelance deliverable or a company landing page is commercial by any ordinary reading, which puts it on Pro at $20 a month plus $20 per developer seat. Source: Vercel pricing page, read 8 September 2026. Droply: The free plan is limited by numbers rather than by what the site is for: 1 site, 25 MB, 5,000 visits and 5 GB a month. Our acceptable use policy governs what you may publish, not whether it is work. ### Password protection costs $150 a month on top of Pro Vercel's deployment-protection docs put Password Protection on the Enterprise plan, or on Pro as part of the Advanced Deployment Protection add-on at $150 a month, with a 30-day minimum before it can be cancelled. On Hobby, Standard Protection leaves the production domain publicly accessible. Source: Vercel docs, Deployment Protection, page last updated 28 August 2026, read 8 September 2026. Droply: Password protection starts on Starter as part of the plan, with no add-on and no minimum term, and the check runs at the edge before any file is served. ### A folder with no index.html gets an interview For a static site with no index.html at the top of the folder, Drop asks which page should be the root, and choosing "No root page" makes the site's root return a 404 while each file still resolves at its own path. That is a reasonable design, and it is a question at the exact moment you wanted a link. Source: Vercel docs, Deploying with Vercel Drop, page last updated 16 June 2026, read 8 September 2026. Droply: A missing index.html is reported after publishing, with the file list we actually found and what to rename, rather than as a modal in the middle of the upload. The site is live either way. ## Droply and Vercel Drop, row by row Vercel is ahead on builds and on network. Those rows are here. - **Account needed to deploy.** Droply: Yes. Every site has an identified owner. Vercel Drop: Yes. The docs say you need a Vercel account and a file or folder. - **Update lands on the same URL.** Droply: Yes, always. A new version, the same address. Vercel Drop: No. Each drop creates a new project and Drop cannot redeploy into an existing one. - **Runs your build for you.** Droply: No, by design. Build locally, upload the output. Vercel Drop: Yes. It detects the framework and builds it. - **Server-rendered routes and functions.** Droply: Not supported at all. Static export only. Vercel Drop: Supported. This is what the platform is for. - **Single HTML file.** Droply: Yes, drop the .html on its own. Vercel Drop: Yes. A file, a folder or a .zip. - **Single .jsx or .tsx, no build.** Droply: Yes, transformed in the visitor browser. Vercel Drop: It would be treated as a project and built. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. Vercel Drop: Servable as static assets, not a product feature. - **Free tier terms.** Droply: No restriction on commercial use. Limits are numbers. Vercel Drop: Hobby is "for personal, non-commercial use". - **Password protection.** Droply: From Starter, included in the plan. Vercel Drop: Enterprise, or a $150 a month add-on on Pro, with a 30-day minimum. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Vercel Drop: Not offered. - **Security check on every publish.** Droply: Every plan, including free. Vercel Drop: Not offered. - **Entry paid price.** Droply: $5 a month for Starter. Vercel Drop: $20 a month for Pro, plus $20 a month per developer seat. Vercel figures come from its own documentation and pricing page, read on 8 September 2026: the Vercel Drop guide (page last updated 16 June 2026), the Deployment Protection guide (28 August 2026) and the pricing page. Product plans can change. ## How to move a site from Vercel Drop Vercel built the site for you, so the thing to move is the build output rather than the drop. Do this once and the address stops moving. 1. **Run the build Vercel was running.** On your own machine, run the framework's build. The framework guides give the exact command and output folder for 23 frameworks, including the static-export flags Next.js needs. 2. **Check for anything that was never static.** API routes, middleware and server-rendered pages do not come across, because nothing executes here. The build will tell you: a static export fails or drops those routes rather than silently half-working. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared The gap here is not really the headline number, it is what the free tier permits and what the password costs. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, work or personal. Vercel Drop: Hobby: 1M edge requests, 100 GB data transfer and 4 hours of active CPU a month, for personal, non-commercial use. - **Entry paid tier.** Droply: $5 a month for Starter. Vercel Drop: $20 a month for Pro, plus $20 a month per developer seat. - **Password protection.** Droply: Included from Starter. Vercel Drop: $150 a month add-on on Pro, or Enterprise. Minimum 30 days before it can be cancelled. - **What you are paying for.** Droply: Serving and features. No build runs, so no compute is metered. Vercel Drop: Compute, bandwidth and platform features, metered per usage. Vercel prices from its own pricing page and Deployment Protection documentation (page last updated 28 August 2026), read 8 September 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything One address per site, on a free plan with no restriction on whether the site is for work. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - The same URL on every republish, so a link you already sent never goes stale. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card, and no restriction on commercial use. ### Is Droply a good Vercel Drop alternative? It is if you want updates to land on the address you already shared and you can run your own build. It is not if you want the host to build the project or you need server-rendered routes. ### Does Vercel Drop update an existing site? No, per its own documentation: each drop creates a new project and Drop does not redeploy into an existing one. Connecting the project to Git afterwards is the documented way to get repeat deploys. ### Can I use the Vercel free plan for client work? Vercel's pricing page says the Hobby plan is for personal, non-commercial use, so read that before putting a client site on it. Droply's free plan has no equivalent restriction; it is limited by numbers. ### Can I host a Next.js site on Droply? Only a fully static export. Server-rendered routes, API routes and middleware do not run here, because nothing of yours executes. The Next.js guide says exactly which configuration produces a publishable folder. ### Can I password-protect a site? Yes, from Starter, as part of the plan. On Vercel, Password Protection is an Enterprise feature or a $150 a month add-on on Pro with a 30-day minimum. ### What happens if my folder has no index.html? The site publishes and then tells you, listing the files it did find and what to rename. Vercel Drop asks during the upload instead, and lets you choose no root page, in which case the site root returns a 404. ### Can I roll back a bad upload? Yes, from Pro. Each upload is kept as its own version and rollback repoints the same address in one click, which is only meaningful because the address does not change in the first place. ### What does Vercel do that Droply does not? It builds your project, runs server-side code, hosts functions and middleware, and deploys on every Git push. Droply serves files and executes nothing. ## Other comparisons - [Netlify Drop alternative](https://droply.host/netlify-drop-alternative) - [Vercel alternative](https://droply.host/vercel-alternative) - [Cloudflare Drop alternative](https://droply.host/cloudflare-drop-alternative) --- Source: https://droply.host/github-pages-alternative # GitHub Pages alternative with no repository to make GitHub Pages is free, and if your site already lives in a repository then a push is a deploy you already know how to do. The reasons to look elsewhere are specific: its terms forbid running a business on it, and a private site needs GitHub Enterprise Cloud. ## Who should not switch GitHub Pages is free with no tier above it to buy, and for a large number of projects that ends the discussion. Be honest with yourself about which of these you are. - The project is already a repository and you are comfortable with Git. Then a push is a deploy, it costs nothing, and there is one site per repository with no count to run out of. - It is an open-source project, a docs site or a personal page. That is precisely what Pages is for, its terms are happy with it, and nothing here is better. - You want a build to run on GitHub Actions on every merge. Droply runs no builds and has no CI, so that workflow simply does not exist here. ## Why people look for a GitHub Pages alternative ### The terms forbid running a business on it GitHub's own usage limits say Pages "is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS)". A client site or a product landing page is squarely in that description. Source: GitHub Docs, GitHub Pages usage limits and prohibited uses, read 8 September 2026. Droply: The free plan does not care what the site is for. It is limited by numbers: 1 site, 25 MB, 5,000 visits and 5 GB a month. What you may publish is governed by the acceptable use policy, which is about content, not about commerce. ### You have to build a repository around the files There is no upload box. Publishing means a repository, a commit, a branch or folder setting, and often an Actions workflow. For someone who was handed a finished folder by a designer, that is a Git tutorial standing between them and a link. Source: GitHub Docs, about GitHub Pages, read 8 September 2026. Droply: Drag the folder, the ZIP or the single .html file onto the page. There is no repository, no commit and no workflow file, and the finished files you were handed are the files served. ### A private site needs GitHub Enterprise Cloud Access control for Pages requires the organization to be on GitHub Enterprise Cloud, and works only for sites published from a private or internal repository. On a personal account there is no way to put a Pages site behind anything. Source: GitHub Docs, changing the visibility of your GitHub Pages site, read 8 September 2026. Droply: Password protection starts on Starter and is checked at the edge before any file is served, so a client preview or an internal document sits behind one password with no plan negotiation. ### Soft limits that you find out about by hitting them Pages sites may be no larger than 1 GB, carry a soft bandwidth limit of 100 GB a month, and a soft limit of 10 builds an hour unless you publish through your own Actions workflow. "Soft" means the number is real but the enforcement is a conversation. Source: GitHub Docs, GitHub Pages usage limits, read 8 September 2026. Droply: The numbers are your plan's numbers, printed on the pricing page, and an upload above the limit is refused with the figure rather than accepted and then discussed later. ## Droply and GitHub Pages, row by row Pages is free and unlimited in site count. Those rows are here. - **Price.** Droply: Free plan, then $5 a month for Starter, the lowest entry tier of any paid host in this comparison. GitHub Pages: Free. There is no paid Pages tier. - **How you publish.** Droply: Upload a folder, a ZIP or a file in the browser. GitHub Pages: Commit to a repository, then a branch or folder setting, often an Actions workflow. - **Number of sites.** Droply: 1 on free, more per paid tier. GitHub Pages: One per repository, plus one user or organization site. - **Commercial use on the free tier.** Droply: Allowed. Limits are numbers, not purposes. GitHub Pages: Not allowed for an online business, e-commerce or SaaS, per its usage limits. - **Private or password-protected site.** Droply: From Starter, checked at the edge. GitHub Pages: Requires GitHub Enterprise Cloud and a private or internal repository. - **Site size.** Droply: Your plan's storage allowance. GitHub Pages: 1 GB per published site. - **Bandwidth.** Droply: 5 GB a month on free, more per tier. GitHub Pages: A soft limit of 100 GB a month. - **Publish frequency.** Droply: Up to 15 publishes a day on free. GitHub Pages: A soft limit of 10 builds an hour, waived with a custom Actions workflow. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. GitHub Pages: Servable as repository files, not a product feature. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. GitHub Pages: Not offered. - **Security check on every publish.** Droply: Every plan, including free. GitHub Pages: Not part of Pages. GitHub scans repositories for secrets separately. - **Custom domain.** Droply: From Pro, $15 a month. GitHub Pages: Free, with HTTPS. GitHub figures come from GitHub Docs, read on 8 September 2026: the GitHub Pages usage limits and prohibited uses page, the about-GitHub-Pages page, and the page on changing a Pages site's visibility. Rows marked "not offered" mean the feature is not part of GitHub Pages on that date. Product terms can change. ## How to move a site from GitHub Pages Your Pages site stays up and your repository is untouched. If the site is built by an Actions workflow, the folder that workflow uploads is the folder to bring. 1. **Find what Pages is actually serving.** For a plain site that is the repository folder itself (often /docs or the branch root). For a built site it is whatever the workflow publishes as its artifact. Run the build locally once and take that folder. 2. **Fix the base path before you upload.** A project site is served from /repository-name/, so many Pages builds hardcode that prefix into their asset URLs. On a Droply subdomain the site is at the root, so rebuild with the base path set back to / or the stylesheets will 404. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared GitHub Pages is free and there is no tier to move up to. The honest comparison is not price, it is what the free price is allowed to be used for. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, any purpose. GitHub Pages: Free: 1 GB per site, a soft 100 GB a month, but not for an online business, e-commerce or SaaS. - **Entry paid tier.** Droply: $5 a month for Starter. GitHub Pages: None. Pages has no paid tier of its own. - **Custom domain.** Droply: From Pro, $15 a month. GitHub Pages: Free, with HTTPS. - **Private site.** Droply: Password protection from Starter. GitHub Pages: GitHub Enterprise Cloud, quoted per organization. GitHub Pages terms and limits from GitHub Docs, read 8 September 2026. Droply prices are read live from the plans table on this page. Product terms can change. ## What you get without paying anything No repository, no workflow file, and no clause about what the site may be for. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - A site served at the root of its own subdomain, so no base-path rewriting. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card, and no restriction on commercial use. ### Is Droply a good GitHub Pages alternative? It is if you do not want to make a repository, if the site is commercial, or if it needs a password. It is not if the project is already in Git and free is the deciding factor, because Pages is free and has no site count to run out of. ### Can I use GitHub Pages for a business website? Its usage limits say no: Pages is not allowed to be used as a free web-hosting service to run an online business, an e-commerce site, or a site primarily providing commercial software as a service. Read that page before putting a commercial site there. ### Can I make a GitHub Pages site private? Only with GitHub Enterprise Cloud, and only for a site published from a private or internal repository. Here, password protection starts on Starter on any account. ### How do I move my GitHub Pages site? Take the folder Pages serves, rebuild with the base path set to / instead of /repository-name/, and upload it. The base path is the one thing that reliably breaks a Pages site moved to a subdomain root. ### Do I need Git to publish on Droply? No. There is no Git integration at all. You upload finished files from the browser, the API, a Chrome extension or a VS Code extension. ### What is the size limit? Your plan's upload limit and storage allowance, listed on the pricing page. GitHub Pages caps a published site at 1 GB with a soft bandwidth limit of 100 GB a month. ### Can I keep my custom domain? Yes, from Pro at $15 a month. Note that GitHub Pages gives custom domains and HTTPS at no cost, so this is a row where moving costs you money. ### Will my site be indexed by Google? Only on a paid plan. Free Droply sites are served noindex deliberately, because free subdomains on a shared domain are the raw material for spam farms. Indexing starts on Starter. GitHub Pages sites are indexable at no cost. ## Other comparisons - [Render alternative](https://droply.host/render-alternative) - [Firebase Hosting alternative](https://droply.host/firebase-hosting-alternative) - [Cloudflare Drop alternative](https://droply.host/cloudflare-drop-alternative) --- Source: https://droply.host/vercel-alternative # Vercel alternative for a site that is already built Vercel is the best place in the world to run a Next.js application and this page is not going to argue otherwise. It is a lot of platform to carry if what you have is a finished folder, a personal-use-only free tier, and a password that costs $150 a month. ## Who should not switch Most Vercel projects should stay on Vercel. This list is longer than the usual one because the overlap between the two products is genuinely small. - Your app uses server-side rendering, API routes, middleware, ISR or image optimisation. None of that runs here. A fully static export works; the rest is the platform. - You want a preview deployment for every pull request, with the comment on the PR. Droply has no Git integration and cannot do this. - You use Vercel's analytics, edge config, KV, blob storage or AI SDK deployments. Those are platform products with no counterpart here. ## Why people look for a Vercel alternative ### The free tier is personal, non-commercial use only Vercel's pricing page states plainly: "Our Hobby plan is for personal, non-commercial use." A freelance deliverable, a client preview or a company page is not personal use, which moves it to Pro at $20 a month plus $20 a month per developer seat. Source: Vercel pricing page, read 8 September 2026. Droply: The free plan makes no judgement about who you are or what the site is for. It is 1 site, 25 MB, 5,000 visits and 5 GB a month, and the acceptable use policy governs content rather than commerce. ### A password on a preview is a $150 a month add-on Password Protection is available on Enterprise, or on Pro as part of the Advanced Deployment Protection add-on at $150 a month, which cannot be cancelled for 30 days. On Hobby, Standard Protection covers preview deployments but leaves the production domain public. Source: Vercel docs, Deployment Protection, page last updated 28 August 2026, read 8 September 2026. Droply: Password protection is part of the plan from Starter, with no add-on, no minimum term and no separate billing line. The check runs at the edge, so the assets sit behind it too. ### The whole platform assumes a repository and a build Vercel is designed around Git: connect a repo, and a build runs on every push. That is excellent when you have a repo and a build. When somebody has emailed you a ZIP of a finished site, it is a pipeline you have to construct before anything is on the internet. Source: Vercel docs, deployment methods table, read 8 September 2026. Droply: Upload the ZIP. There is no repository, no build configuration and no framework detection to get wrong, because nothing is built: the files you upload are the bytes served. ### You are paying for compute you are not using The Hobby allowance is denominated in edge requests, data transfer and active CPU hours, because the platform assumes your site computes. A finished static site does not compute; it just gets served. Source: Vercel pricing page, read 8 September 2026. Droply: Nothing of yours executes here, so nothing is metered for compute. The limits are storage, visits and bandwidth, which are the only three numbers a static site can actually consume. ## Droply and Vercel, row by row Vercel is a much larger product. These are the rows where the two overlap. - **Server-side rendering and functions.** Droply: Not supported at all. Vercel: Supported, and the reason to use it. - **Runs your build.** Droply: Never. Build locally, upload the output. Vercel: Yes, on every push, with framework detection. - **Git integration.** Droply: None. Vercel: Deploy on every push, preview per pull request. - **Publishing without Git.** Droply: The only way. Browser, API or extension. Vercel: Vercel Drop or the CLI. Each Drop makes a new project. - **Free tier terms.** Droply: No restriction on commercial use. Vercel: Hobby is "for personal, non-commercial use". - **Free tier limits.** Droply: 1 site, 25 MB, 5,000 visits, 5 GB a month. Vercel: 1M edge requests, 100 GB data transfer, 4 hours active CPU a month. - **Password protection.** Droply: From Starter, included in the plan. Vercel: Enterprise, or a $150 a month add-on on Pro with a 30-day minimum. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Vercel: Not offered. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. Vercel: Servable as static assets, not a product feature. - **Security check on every publish.** Droply: Every plan, including free. Vercel: Not offered. - **Seats.** Droply: Pricing is per plan. See the pricing page for team seats. Vercel: $20 a month per developer seat on Pro, viewers free. - **Entry paid price.** Droply: $5 a month for Starter. Vercel: $20 a month for Pro. Vercel figures come from its own pricing page and its Deployment Protection documentation (page last updated 28 August 2026), both read on 8 September 2026. Rows marked "not offered" mean the feature is not part of Vercel's static hosting on that date. Product plans can change. ## How to move a static site from Vercel This only works for a site that is genuinely static. Find that out first, because the build will tell you in a minute and a half. 1. **Produce a static export and see whether it succeeds.** Run the framework's static export locally. For Next.js that is the output: export configuration; the Next.js guide gives the exact form. If the export fails or drops routes, the site has server-side parts and it should stay on Vercel. 2. **List what the export left behind.** API routes, middleware, on-demand revalidation and image optimisation do not come across. Decide what replaces each one before you move the domain, not after. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared Vercel meters compute because Vercel runs your code. Nothing of yours runs here, so the ladders measure different things and the rows say which. The headline gap is still worth naming: the entry paid tier here is $5 a month flat, against $20 a month plus $20 for each developer seat. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month, work or personal. Vercel: Hobby: 1M edge requests, 100 GB transfer, 4 hours active CPU, personal and non-commercial only. - **Entry paid tier.** Droply: $5 a month for Starter. Vercel: $20 a month for Pro, plus $20 a month per developer seat. - **Password protection.** Droply: Included from Starter. Vercel: $150 a month Advanced Deployment Protection add-on on Pro, or Enterprise. - **What is metered.** Droply: Storage, visits and bandwidth. Vercel: Edge requests, data transfer, active CPU, function invocations and more. Vercel prices from its own pricing page and Deployment Protection documentation, read 8 September 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything No seats, no compute meter, and no clause about whether the site is for work. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - A published site with no build configuration to get wrong, because no build runs. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card, and no restriction on commercial use. ### Is Droply a good Vercel alternative? Only for a site that is already static. If your project uses server-side rendering, API routes or middleware, Vercel is the right platform and moving would break the site. ### Can I use Vercel free for client work? Vercel's pricing page says the Hobby plan is for personal, non-commercial use, so read it before putting a client site there. Droply's free plan has no equivalent clause. ### Can I host a Next.js site here? Only a fully static export. Set the export output, run the build, and upload the folder it produces. The Next.js guide covers the configuration and what it silently drops. ### How much does password protection cost? It is included from Starter here. On Vercel it is an Enterprise feature, or a $150 a month Advanced Deployment Protection add-on on Pro that cannot be cancelled for 30 days. ### Do I pay per developer? No. Droply prices per plan, and team seats are a plan feature listed on the pricing page. Vercel Pro is $20 a month plus $20 a month per developer seat. ### What do I lose by moving? Git-triggered deploys, preview URLs per pull request, framework builds, functions, middleware, image optimisation and Vercel's analytics and storage products. None of those exist here. ### What do I gain? Uploads without a repository, a free tier you may use commercially, password protection inside the plan, expiring links, document hosting, and a security check on every publish. ### Can I keep the same URL when I republish? Yes, always. Each upload is a new version and publishing repoints the same address, so links you already sent keep working. Vercel Drop, the no-Git path there, creates a new project per drop instead. ## Other comparisons - [Vercel Drop alternative](https://droply.host/vercel-drop-alternative) - [Netlify Drop alternative](https://droply.host/netlify-drop-alternative) - [Render alternative](https://droply.host/render-alternative) --- Source: https://droply.host/render-alternative # Render alternative that does not need a Git repo Render hosts static sites for free and does it well, as long as the site is in a repository. There is no upload path at all: the documented way to deploy is to connect a repo and let Render build on every push. This page is for when that is the whole obstacle. ## Who should not switch Render is a real platform and static sites are the free corner of it. If you use the rest, keeping the site next to it is worth more than anything on this page. - You already run a web service, a database, a cron job or a background worker on Render. Keeping the static front end in the same workspace is a genuine operational win. - Your site is in a repository and you want it rebuilt on every push. Render does that for free on Hobby and Droply does not do it at all. - You need more than 5 GB of traffic for free. Render's Hobby workspace includes 5 GB a month, so at that end the two are close and Render costs nothing. ## Why people look for a Render alternative ### A Git repository is not optional, it is the only door Render's static-sites documentation describes one workflow: link your site's Git repo, choose a branch, and Render updates the site on every push. There is no upload path. If the finished site arrived as a ZIP in an email, the first step is creating a repository for someone else's files. Source: Render docs, static sites, read 8 September 2026. Droply: Drag the folder, the ZIP or the single .html file onto the page. No repository, no branch, no build settings, and nothing to keep in sync afterwards. ### A build runs whether or not you needed one Static sites count against the workspace's monthly pipeline minutes: 500 on Hobby, 1,000 on Pro, and $5 per additional 1,000. For a site that is already built, that is a meter running on work that did not need doing. Source: Render pricing page, read 8 September 2026. Droply: No build ever runs, so there is no minute to count. A publish is an upload and a pointer flip, and the fifth one costs exactly what the first one did. ### Bandwidth is billed per gigabyte once the allowance is gone Hobby includes 5 GB of outbound bandwidth a month and Pro includes 25 GB, with everything above billed at $0.15 per GB. A page that gets shared unexpectedly is a bill rather than a limit. Source: Render pricing page and the workspace-plans changelog of 23 April 2026, read 8 September 2026. Droply: Bandwidth is a plan allowance rather than a meter, so an unexpected week of traffic is a cap you hit, not an invoice you receive. The numbers per tier are on the pricing page. ### Documents are not a thing it hosts Render serves what your build produces. A PDF, a deck or a spreadsheet is not a site, so sharing one means a different service, a different link, and a different place to look when it needs updating. Source: Render docs, static sites, read 8 September 2026: document hosting is not offered as a service type. Droply: PDFs, images, media and office documents are first-class: each gets a URL and renders in the browser. See turning a PDF into a link. ## Droply and Render, row by row Render static sites are free. That row is here, at the top. - **Price for a static site.** Droply: Free plan, then $5 a month for Starter. Render: Free to deploy on the Hobby workspace. - **How you publish.** Droply: Upload a folder, a ZIP or a file in the browser. Render: Connect a Git repo. Render builds and deploys on every push. - **Publishing without Git.** Droply: The only way. Render: Not documented. - **Build minutes.** Droply: None consumed. No build runs. Render: 500 a month on Hobby, 1,000 on Pro, then $5 per 1,000. - **Included bandwidth.** Droply: 5 GB a month on free, more per tier. Render: 5 GB on Hobby, 25 GB on Pro, 1 TB on Scale. - **Bandwidth over the allowance.** Droply: A plan cap, not a meter. Render: $0.15 per additional GB. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. Render: Not a service type. - **Password protection.** Droply: From Starter, checked at the edge. Render: Not offered for static sites. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Render: Not offered. - **Rollback.** Droply: From Pro, one click. Render: Redeploy a previous commit from the dashboard. - **Security check on every publish.** Droply: Every plan, including free. Render: Not offered. - **Entry paid tier.** Droply: $5 a month for Starter. Render: $25 a month for Pro, flat, plus usage. Render figures come from its own documentation and pricing page, read on 8 September 2026, plus the workspace-plans changelog entry of 23 April 2026 that replaced the per-member plans. Rows marked "not offered" mean the feature does not appear in those documents on that date. Product plans can change. ## How to move a site from Render Everything you need is already on your machine, because Render built it from your repository. The site stays up while you do this. 1. **Run the same build command locally.** Take the build command and publish directory from the Render service settings and run them yourself. That publish directory is exactly the folder to upload; the framework guides confirm the output folder for 23 frameworks. 2. **Move any redirect and header rules by hand.** Render's redirect and rewrite rules live in its dashboard rather than in your repository, so they do not travel with the folder. Write them down before you delete the service. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared Render bills a static site as usage on top of a workspace plan. Droply bills a plan, at $5 a month against Render Pro at $25 flat plus usage. The rows below compare like with like where that is possible and say so where it is not. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month. Render: Hobby: free to deploy, 5 GB bandwidth and 500 build minutes included, then usage billed. - **Entry paid tier.** Droply: $5 a month for Starter. Render: $25 a month for Pro, flat: 25 GB bandwidth, 1,000 build minutes. - **Overage.** Droply: None. A plan cap rather than a meter. Render: $0.15 per GB of bandwidth, $5 per 1,000 extra build minutes. - **Top published tier.** Droply: See the pricing page. Render: $499 a month for Scale: 1 TB bandwidth, 5,000 build minutes. Render prices and allowances from its own pricing page, read 8 September 2026, and the workspace-plans changelog of 23 April 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything No repository, no build minutes, and no per-gigabyte meter behind the free plan. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - Publishing straight from the browser, the API, Chrome or VS Code, with no repo in between. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card. Nothing is metered per gigabyte on top. ### Is Droply a good Render alternative? It is if the Git requirement is the obstacle, or if you want to publish a document, put a password on a preview, or set a link to expire. It is not if you already run other services on Render, because Render static sites are free. ### Can I deploy to Render without a Git repository? Not by any documented route. Render's static-sites documentation describes connecting a repo and deploying on every push, and there is no upload path in it. ### Does Droply charge for bandwidth overage? No. Each plan has a bandwidth allowance and it behaves as a cap rather than as a meter, so an unexpectedly popular page cannot generate a bill. Render bills $0.15 per GB above its included amount. ### How do I move my Render static site? Run the build command and publish directory from your Render service settings locally, then upload that folder. Copy any redirect or header rules out of the Render dashboard first, because they live there rather than in your repository. ### Does Droply run builds? No, never. That is why there are no build minutes to run out of. You run the build on your machine and upload the output; the framework guides give the exact command and folder for 23 frameworks. ### Can I roll back a bad deploy? Yes, from Pro, in one click. Render can redeploy a previous commit from its dashboard, so both have an answer here; the difference is whether you needed a commit in the first place. ### Can I password-protect a site? Yes, from Starter, checked at the edge before any file is served. Render does not offer password protection for static sites. ### What does Render do that Droply does not? It runs your build on every push, and it hosts web services, databases, cron jobs and background workers next to the static site. Droply serves files and runs nothing. ## Other comparisons - [GitHub Pages alternative](https://droply.host/github-pages-alternative) - [Firebase Hosting alternative](https://droply.host/firebase-hosting-alternative) - [Vercel alternative](https://droply.host/vercel-alternative) --- Source: https://droply.host/firebase-hosting-alternative # Firebase Hosting alternative with no CLI to install Firebase Hosting is generous: 10 GB of storage free, a custom domain and SSL at no cost. Getting a file onto it means a Google Cloud project, the Firebase CLI and two commands, and the free transfer allowance is a daily figure rather than a monthly one. ## Who should not switch Firebase Hosting is free and its free tier is bigger than ours on the number most people check first. Be clear about that before reading the rest. - You already use Firebase for auth, Firestore or functions. Hosting is the front end of that stack and separating it buys you nothing. - You want a custom domain with SSL at no cost. Firebase includes both on the free Spark plan; here custom domains start on Pro at $15 a month. - You are comfortable in a terminal and deploy from CI. Two commands from a script is a perfectly good workflow and this page is not going to improve on it. ## Why people look for a Firebase Hosting alternative ### You need a Google Cloud project and a CLI before anything is live Firebase's own quickstart is explicit: create a Firebase project first, install the Firebase CLI, then run firebase init hosting and firebase deploy --only hosting. For a designer with a finished folder, that is a Node install and a project console standing between them and a URL. Source: Firebase documentation, Hosting quickstart, read 8 September 2026. Droply: Drag the folder onto the page. Nothing is installed, no project is created, and the first publish takes about as long as the upload does. If what you have is a single file rather than a folder, a lone .html file is a whole site here. ### The free transfer allowance is per day, not per month Spark includes 360 MB of data transfer a day. That is roughly 12 GB spread evenly across a month, and nothing about traffic is spread evenly: one post that does well uses a week of it in an afternoon and the site stops serving for the rest of the day. Source: Firebase pricing page, read 8 September 2026. Droply: The allowance is monthly: 5 GB a month on the free plan, and larger on every tier above it. A busy day borrows from a quiet one instead of hitting a wall at lunchtime. The per-tier figures are on the pricing page. ### Going over means pay-as-you-go with no ceiling Past the free allowances you are on Blaze: $0.026 per GB stored and $0.15 per GB transferred, billed as usage. There is no plan price to cap it at, which is the right model for an application and a nervous one for a static page you forgot about. Source: Firebase pricing page, read 8 September 2026. Droply: A plan has a fixed price and its limits behave as caps. Traffic beyond the allowance is refused rather than billed, so the worst case is a page that stops serving, not a bill you did not expect. ### No password protection and no expiring links Hosting serves your files publicly. There is no built-in password gate and no way to set a link to stop working on a date, so a client preview or a time-limited offer needs application code or a different service. Source: Firebase Hosting documentation, read 8 September 2026: no password gate or link-expiry feature is documented for Hosting. Droply: Password protection starts on Starter and is enforced at the edge before any file is served. Auto-expiring links start on Starter: six hours, a week, or a date you choose. Both work on a document as well as a site, which is what makes a PDF on a link usable for anything confidential. ## Droply and Firebase Hosting, row by row Firebase wins the free-tier rows on storage and on the custom domain. Both are here. - **How you publish.** Droply: Upload a folder, a ZIP or a file in the browser. Firebase Hosting: A Firebase project, the CLI, firebase init hosting, firebase deploy. - **Free storage.** Droply: 25 MB. Firebase Hosting: 10 GB. - **Free data transfer.** Droply: 5 GB a month. Firebase Hosting: 360 MB per day. - **Custom domain on the free tier.** Droply: No. From Pro, $15 a month. Firebase Hosting: Yes, with SSL, at no cost. - **What happens over the limit.** Droply: A cap: the plan stops serving beyond its allowance. Firebase Hosting: Blaze billing: $0.026 per GB stored, $0.15 per GB transferred. - **Single HTML file.** Droply: Yes, drop the .html on its own. Firebase Hosting: Yes, inside the public directory the CLI deploys. - **Single .jsx or .tsx, no build.** Droply: Yes, transformed in the visitor browser. Firebase Hosting: Not offered. - **PDFs and documents.** Droply: First-class files with an in-browser viewer. Firebase Hosting: Servable as static assets, not a product feature. - **Password protection.** Droply: From Starter, checked at the edge. Firebase Hosting: Not documented for Hosting. - **Expiring links.** Droply: From Starter: six hours, a week, or a date. Firebase Hosting: Not documented for Hosting. - **Rollback.** Droply: From Pro, one click. Firebase Hosting: Release history in the console; a previous release can be rolled back. - **Security check on every publish.** Droply: Every plan, including free. Firebase Hosting: Not offered. Firebase figures come from Google's own documentation, read on 8 September 2026: the Firebase pricing page and the Hosting quickstart. Rows marked "not documented" mean the feature does not appear in Firebase Hosting's documentation on that date. Product plans can change. ## How to move a site from Firebase Hosting The folder Firebase deploys is a plain folder on your machine, so this is one of the shortest migrations here. Do not delete the Firebase project until the DNS has moved. 1. **Take the public directory.** Open firebase.json and read the hosting public value, which defaults to public. That directory is exactly what Firebase serves, so it is exactly what to upload here. Nothing needs rebuilding. 2. **Rewrite any rewrite rules.** Firebase rewrites, redirects and headers live in firebase.json and do not travel with the folder. Single-page apps in particular rely on a rewrite to index.html, which is a setting on the site here rather than a file in the folder. 3. **Drop the folder on Droply.** Sign up, then drag the folder, the ZIP or the single HTML file onto the upload area. Nothing is repackaged and no build runs: the files you upload are the files served. 4. **Check what the security pass found.** Every publish is read for things that should not be public: a committed .env, a .git directory, a private key, an API key in a bundle. Old exports carry these more often than fresh builds do, so read it before you send the link anywhere. 5. **Point your domain at it, if you had one.** From Pro at $15 a month you move the DNS record to Droply and the certificate is issued for you. Change the record last, once the Droply URL already renders what you expect, so there is no window where the domain resolves to nothing. ## Pricing compared Firebase is free until it is usage-billed, with no plan in between. That is the real difference, and it cuts both ways: below the free allowance Firebase costs nothing and Droply does not, and above it Firebase has no ceiling while Starter is $5 a month whatever happens. - **Free.** Droply: 1 site, 25 MB, 5,000 visits and 5 GB a month. Firebase Hosting: Spark: 10 GB storage, 360 MB per day of transfer, custom domain and SSL included. - **Beyond the free allowance.** Droply: $5 a month for Starter, a fixed price with fixed limits. Firebase Hosting: Blaze: pay as you go, $0.026 per GB stored and $0.15 per GB transferred. - **Custom domain.** Droply: From Pro, $15 a month. Firebase Hosting: Free, with SSL, on both plans. - **Predictability.** Droply: The bill cannot move. The site stops serving instead. Firebase Hosting: The bill moves with traffic. Budget alerts exist; a hard cap does not. Firebase prices from Google's own Firebase pricing page, read 8 September 2026. Droply prices are read live from the plans table on this page. Product plans can change. ## What you get without paying anything No CLI, no cloud project, and a monthly allowance rather than a daily one. - 1 live site on a 25 MB account, with no card and no trial clock. - Up to 25 MB per upload, and up to 15 publishes a day. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - The same URL on every re-upload, so a link you already sent keeps working. - 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. - A monthly bandwidth allowance, so one busy afternoon does not take the site off the internet. ## Frequently asked questions ### Is Droply free? Yes. 1 live site, 25 MB of storage, 5,000 visits and 5 GB a month, HTTPS included, no card and no usage billing behind it. ### Is Droply a good Firebase Hosting alternative? It is if you want to publish from a browser, need a password or an expiring link, or want a bill that cannot move. It is not if you want a free custom domain or 10 GB of free storage, both of which Firebase gives you and we do not. ### Do I need the Firebase CLI to deploy? On Firebase, yes: the quickstart says to create a project, install the CLI, then run firebase init hosting and firebase deploy --only hosting. Here you drag a folder onto a page. ### What is the Firebase free transfer limit? Its pricing page lists 360 MB of data transfer per day on the Spark plan, which is a daily cap rather than a monthly pool. Droply's free plan gives 5 GB a month, so a busy day can borrow from a quiet one. ### How do I move my Firebase site? Read the hosting public value in firebase.json, which defaults to public, and upload that directory. Copy any rewrite, redirect or header rules out of firebase.json first, because they do not travel with the folder. ### Can I get a free custom domain? Not here. Custom domains start on Pro at $15 a month. Firebase includes a custom domain and SSL on its free Spark plan, and that is a genuine advantage. ### Can I password-protect a site? Yes, from Starter, checked at the edge before any file is served. Firebase Hosting documents no password gate; protecting a page there means writing application code. ### Can I get an unexpected bill? Not here. Plan limits behave as caps: past the allowance the site stops serving rather than generating charges. Firebase Blaze is pay as you go, with budget alerts but no hard ceiling. ### Does a single-page app work? Yes. The rewrite-everything-to-index.html behaviour that Firebase configures in firebase.json is a setting on the site here, so it survives the move without a config file. ## Other comparisons - [Render alternative](https://droply.host/render-alternative) - [GitHub Pages alternative](https://droply.host/github-pages-alternative) - [Cloudflare Drop alternative](https://droply.host/cloudflare-drop-alternative) # Features --- Source: https://droply.host/features # Droply features One page per feature, each stating the exact plan it starts on. Plan availability on those pages is read from the plan records the application enforces with, not written by hand. ## Your own address and audience What turns a shared link into something that looks like yours, and tells you whether anyone opened it. - [Custom domains](https://droply.host/features/custom-domains): Serve an uploaded site from a domain you own, with the certificate issued and renewed for you. - [QR codes](https://droply.host/features/qr-codes): Turn a published link into a printable QR code, without sending the link to a third-party generator. - [Site analytics](https://droply.host/features/analytics): Visits, uniques, devices, referrers and downloads, counted at the edge with no script in your page. - [Email capture](https://droply.host/features/email-capture): Collect addresses from a page with no backend, and read or export them from the dashboard. ## Control who sees it and who can change it A published link is public by default and a publish is permanent by default. These are the ways to change both, and to undo one. - [Password protection](https://droply.host/features/password-protection): One password in front of a whole site, checked at the edge before any file is served. - [Expiring links](https://droply.host/features/expiring-links): Give a link a deadline, from six hours to an exact moment, and get the content back if you change your mind. - [Version rollback](https://droply.host/features/version-rollback): Every publish is kept as its own version, so putting the previous one back is one step, not a re-upload. - [Team seats](https://droply.host/features/team-seats): Invite colleagues instead of sharing a login, and scope who can reach which sites. ## Get work in and out Ways to publish that are not a browser tab: an import, an API call, an editor, a toolbar button. - [Site import](https://droply.host/features/site-import): Paste a URL and get a working copy of that static site on a link of your own. - [Public API](https://droply.host/features/api): A small REST API for creating sites and publishing deployments from a script. - [Chrome extension](https://droply.host/features/chrome-extension): A side panel that turns a file or pasted HTML into a live link without leaving the tab. - [VS Code extension](https://droply.host/features/vscode-extension): Publish a built folder from inside the editor and get the live address back in the panel. ## Features with a page of their own - [AI website builder](https://droply.host/ai-website-builder): Describe a page, watch it get written, and publish it without opening an editor. - [Deploy security check](https://droply.host/website-security-check): Every deploy is read for a published .env file, a .git folder, a private key or a leaked API key. On every plan. - [Link in bio builder](https://droply.host/link-in-bio): A one-page link hub with fifteen themes and sixty blocks, with every design control on the free plan. - [MCP server for AI assistants](https://droply.host/mcp-server): Connect Claude or another AI assistant and let it publish pages and finished sites to your account, on every plan. --- Source: https://droply.host/features/custom-domains # Custom domains for a site you uploaded Point a domain you already own at a site you dropped in here, and the certificate is issued and renewed for you. No server, no DNS panel of ours to learn, no renewal to remember. ## Plan availability Connecting a domain starts on Pro ($15 a month). Every plan below it still gets a permanent HTTPS address on our own domain. - **Free:** not included - **Starter:** not included - **Pro:** included - **Business:** included - **Enterprise:** included ## What connecting a domain actually changes The site does not move and it does not get rebuilt. One more name starts answering for it, and that name is yours. When you publish here, the site is already live on a subdomain of ours over HTTPS. Connecting a custom domain adds your own name in front of exactly the same files: www.yourstudio.com and the address we gave you serve the same bytes from the same deployment. You add two DNS records at your registrar, we watch for them, and once they resolve the certificate is requested, installed and renewed on its own for as long as the domain stays pointed here. The part people expect to be difficult is the certificate, and it is the part you do not touch. There is no ACME client to install, no renewal cron to forget, and no separate certificate purchase. Behind the scenes the edge asks us whether a domain is allowed to have one before it issues, which is also what stops somebody pointing a domain they do not own at your account. Apex domains and subdomains both work, and the same site can answer on several names at once, so a rename does not break the link you already sent. If you have not published anything yet, static website hosting covers the upload side first. ## How to use it 1. **Publish the site first.** Drop the files in and confirm the page looks right on the address we issue. A domain pointed at a site that is not working yet just moves the problem. 2. **Add the DNS records.** The dashboard shows the exact records for your domain, and we have a per-registrar walkthrough if your panel calls them something else. 3. **Wait for the check to pass.** We poll for the records and issue the certificate as soon as they resolve. Most registrars are done inside an hour, some take longer. ## When people reach for this - **A client site that has to look like the client owns it.** Agencies rarely get to hand over a link on somebody else's brand. Publish the build, connect the client's domain, and the only name in the address bar is theirs. See static hosting for freelancers for the whole workflow. - **A campaign page that outlives the campaign.** A landing page on a memorable name is easier to put on a poster or read out loud than a generated subdomain, and it stays yours if you ever move it somewhere else. - **A documentation or status page on a subdomain.** Point docs.yourcompany.com here and keep the main site wherever it already lives. A subdomain is the easiest way to add a static page to an existing setup without touching it. ## Doing this without us The alternative is not "no custom domain". It is a small pile of separate jobs that each have to keep working. - **Getting the certificate.** Droply: Requested and installed when the DNS check passes. A VPS you set up yourself: Install an ACME client, open port 80, keep it running. - **Renewing it.** Droply: Automatic, with no action and no expiry date to track. A VPS you set up yourself: A timer you have to notice when it stops firing. - **Server maintenance.** Droply: None. There is no server of yours in the path. A VPS you set up yourself: Patching, restarts, and a web server config to maintain. - **Several names on one site.** Droply: Add each one; they all serve the same deployment. A VPS you set up yourself: A virtual host block and a certificate entry per name. - **What it costs.** Droply: Included from Pro upward, at $15 a month. A VPS you set up yourself: The machine, plus your time when it breaks. Compared against running a small Linux server yourself, which is the usual alternative for a static site on a custom domain. Checked September 2026. ## When this is not the right tool A custom domain here points at static files. If your domain needs to do more than that, some of it belongs elsewhere. - We do not sell or register domains. You buy the name wherever you like and point it here. - Email on that domain is untouched and stays with your provider. We serve web traffic only, so your MX records are your business. - You need access to the domain's DNS. If somebody else manages it, they have to add two records for you. - A domain can only be connected to one account at a time, which is what stops a stranger claiming it. ## Frequently asked questions ### Which plan do I need for a custom domain? Custom domains start on Pro, which is $15 a month. Free and cheaper tiers still get a permanent HTTPS address on our own domain; what the paid tier adds is the ability to put your own name in front of it. ### Is the SSL certificate included? Yes, and it is not an add-on or an extra charge. The certificate is requested as soon as the DNS check passes and renewed automatically for as long as the domain stays pointed here. ### Can I use an apex domain, like example.com with no www? Yes. Both an apex domain and a subdomain work. The dashboard shows the exact records for whichever you are connecting, because the record type is different for each. ### How long does it take to go live? Usually under an hour, and often much less. The time is spent waiting for your registrar to publish the records, not on our side; once we can see them the certificate is issued in seconds. ### Can one site answer on more than one domain? Yes. Connect each name and they all serve the same deployment. That is the usual way to keep an old address working after a rebrand. ### What happens to my old address? It keeps working. Connecting a domain adds a name, it does not take one away, so any link you already sent on the original address stays live. ## Related features - [Password protection](https://droply.host/features/password-protection) - [Site analytics](https://droply.host/features/analytics) - [QR codes](https://droply.host/features/qr-codes) --- Source: https://droply.host/features/qr-codes # A QR code for anything you publish Every published link can hand you a QR code for it, so the same page works on a poster, a table card or a slide without a third-party generator in the middle. ## Plan availability QR codes are included on every plan, including the free one. - **Free:** included - **Starter:** included - **Pro:** included - **Business:** included - **Enterprise:** included ## A code that points at something you control The code encodes your published address. Because that address never changes when you re-publish, the printed code does not go stale. Publish a page, a PDF or an image, and the site gets a QR code for its address. You download it and put it wherever a printed thing needs to reach a screen: a menu card, a poster, an exhibition label, the last slide of a deck, a parcel insert. The code carries only the URL, so scanning it opens the page in the phone's own browser with no app and no intermediate redirect page. The reason this is worth having next to the hosting rather than as a separate tool is the update path. Free QR generators encode whatever URL you paste, and if that URL later has to change, every printed copy is dead. Here the address belongs to the site, not to the file, so publishing a new version replaces the content behind a code that is already on a thousand table cards. If the thing you are printing is a document, PDF to QR code is the same idea with the document workflow around it. ## How to use it 1. **Publish the page or file.** Drop in the HTML, the PDF or the image and let it go live. The address you get is the one the code will carry. 2. **Download the code.** Open the site in the dashboard and take the QR image. It is a plain image file, so it drops into any layout tool. 3. **Print it and keep the page current.** Re-publish whenever the content changes. The code keeps working because the address did not move. ## When people reach for this - **A menu that changes weekly.** Print the code once, laminate it, and update the menu page whenever the kitchen does. QR code menu covers the restaurant version, including what to do about the printed copy you still have. - **A poster or flyer that has to lead somewhere.** An event page, a price list or a set of directions is easier to scan than to type. The page can carry more detail than the poster has room for. - **A document handed out at a stand.** A spec sheet or a brochure as a code beats a stack of paper, and you can see afterwards whether anyone actually opened it if analytics is on. ## Doing this without us Free QR generators are everywhere. The differences that matter show up after the thing is printed. - **Changing the destination later.** Droply: Re-publish the page; the code is untouched. A free online QR generator: Not possible unless you paid for a tracked code. - **Who owns the link.** Droply: You do. The code encodes your address directly. A free online QR generator: Often a shortener domain that can expire or be blocked. - **What happens if the service closes.** Droply: Nothing. The code points at your site, not at us. A free online QR generator: Every printed code stops resolving. - **Where the page itself lives.** Droply: Here, published in the same step. A free online QR generator: Somewhere else, arranged separately. Compared against the general category of free QR generators rather than one named product, because the behaviour above is what they have in common. Checked September 2026. ## When this is not the right tool This is a code for a link you host here. It is not a QR product in its own right. - There is no scan counter on the code itself. What you get is ordinary page analytics for the page it opens. - There is no logo-in-the-middle or colour styling. It is a plain, high-contrast code, which is the version that scans reliably. - It encodes a URL. Codes that carry a Wi-Fi password, a contact card or a payment string are a different job. ## Frequently asked questions ### Is the QR code free? It is included on every plan, including the free one. There is no per-code charge and no limit on how many times a code can be scanned. ### Does the code expire? No. It encodes your published address, so it keeps working for as long as the site is published. Nothing about the code has a time limit of its own. ### Can I change what the code opens after printing it? Yes, by publishing new content to the same site. The address stays the same, so the printed code now opens the new page. That is the main reason to generate the code here rather than in a generator. ### What image format do I get? A plain raster image you can drop straight into a document, a slide or a print layout. No account is needed on the scanning side. ### Can I put a QR code on a PDF I published? Yes. A PDF gets an address like any other upload, so it gets a code like any other page. PDF to QR code walks through it. ### Will the code work without an app? Yes. Every current phone camera reads QR codes natively, and the code contains a normal HTTPS address, so it opens in the phone's browser. ## Related features - [Custom domains](https://droply.host/features/custom-domains) - [Site analytics](https://droply.host/features/analytics) - [Expiring links](https://droply.host/features/expiring-links) --- Source: https://droply.host/features/analytics # Site analytics for a page you just published Visits, unique visitors, devices, referrers, missing pages and file downloads, counted at the edge. No tracking script to add and no cookie banner to write. ## Plan availability Analytics starts on Pro. - **Free:** not included - **Starter:** not included - **Pro:** included - **Business:** included - **Enterprise:** included ## Counted where the bytes are served The numbers come from the server that answered the request, not from JavaScript running in the visitor's browser. Every request to your site passes through our edge, so that is where it is counted. You get visits and unique visitors over time, the split between desktop and mobile, which sites and searches sent people to you, which addresses returned a missing page, and how many times each downloadable file was opened. Nothing is added to your HTML, which means the numbers do not depend on the visitor allowing a script to run, and a static page you uploaded stays exactly the file you uploaded. The download counter is the one people are usually missing. If what you published is a PDF on a link rather than a website, a page-view script would tell you nothing at all, because there is no page for it to sit in. Counting at the edge means a PDF, an image and an HTML page are all measured the same way. The missing-page list is worth the same attention for a different reason: it is usually a link you sent out with a typo in it, and it is the one report that tells you to go and fix something. ## How to use it 1. **Publish on a plan that includes it.** Analytics starts on Pro. Nothing needs to be switched on in the page itself. 2. **Send the link.** Counting begins with the first request. There is no snippet to paste and no verification step. 3. **Read it in the dashboard.** Open the site and check visits, devices, referrers, missing pages and downloads over the range you care about. ## When people reach for this - **Finding out whether a client opened the preview.** A build sent for review either got looked at or it did not, and that changes what the next email says. Client website preview is the workflow this sits inside. - **Seeing which channel actually worked.** A link goes out in a newsletter, a post and a message thread. The referrer breakdown tells you which of the three was worth the effort. - **Counting downloads of a document.** A price list, a menu or a resume gets opened rather than browsed. Downloads are counted per file, so a document that lives on one link still produces a number. ## Doing this without us The usual answer is a third-party analytics script. It is a reasonable answer, and here is what it costs on a static page. - **Editing your HTML.** Droply: Nothing to add. The page you uploaded is the page served. A tracking script in your page: A snippet in every page, re-added on every rebuild. - **Blocked visitors.** Droply: Counted anyway; the request reached the server. A tracking script in your page: Missing entirely if the script is blocked. - **PDFs and other files.** Droply: Counted as downloads, per file. A tracking script in your page: Invisible. A script needs a page to run in. - **Cookie consent.** Droply: No cookie is set for counting. A tracking script in your page: Usually a consent banner and a policy to maintain. - **Page weight.** Droply: Unchanged. A tracking script in your page: An extra third-party request on every view. Compared against the general pattern of client-side analytics scripts rather than one named product. Checked September 2026. ## When this is not the right tool This answers "did anyone come, from where, on what". It is deliberately not a product analytics suite. - There are no funnels, no custom events and no per-visitor session replay. If you need those, add your own analytics script; nothing here stops you. - Visitors are counted without a persistent identifier, so the unique count is an estimate rather than a person count. - Country breakdown is not switched on yet, because it needs a geolocation database we have not shipped. - Numbers are for sites hosted here. We cannot report on a page that lives somewhere else, including one you copied in with site import and then took down. ## Frequently asked questions ### Do I need to add a tracking script? No. Counting happens at the edge that serves your files, so there is nothing to paste into your HTML and nothing to re-add after a rebuild. ### Which plan includes analytics? It starts on Pro. Free sites are served and counted for quota purposes, but the reporting view is a paid feature. ### Does this need a cookie banner? No cookie is set in order to count a visit. You are still responsible for anything your own page loads, so if you add a third-party script yourself, that is a separate question. ### Can I see who visited? No, and that is deliberate. You get aggregate numbers: visits, uniques, device split, referrers, missing pages and download counts. There is no per-person view. ### Are downloads of a PDF counted? Yes. Files are counted individually, which is the main reason edge counting is useful here: a script in a page cannot see a PDF being opened. ### Do bots inflate the numbers? Known crawlers are classified separately so they do not sit in the same total as real visits. No classifier is perfect, so treat a small tail of odd traffic as noise. ## Related features - [Email capture](https://droply.host/features/email-capture) - [Custom domains](https://droply.host/features/custom-domains) - [Expiring links](https://droply.host/features/expiring-links) --- Source: https://droply.host/features/email-capture # Email capture on a static page Collect addresses from a page that has no backend, read them in the dashboard, and export them when you want them somewhere else. ## Plan availability Email capture starts on Business. - **Free:** not included - **Starter:** not included - **Pro:** not included - **Business:** included - **Enterprise:** included ## The one thing a static page cannot do on its own A static page can show a form. It cannot receive what the form sends, because there is nothing running to receive it. That gap is the reason most "just a landing page" projects end up dragging in a whole platform. Email capture closes it without changing what your page is: the page stays a file you uploaded, and the submission goes to us instead of to a server you would otherwise have to run. Addresses collect against the site they came from, you read them in the dashboard, and you can take them out again whenever you want them in a mailing tool. It is worth being precise about the scope, because "forms" means very different things to different people. This is address collection for a waiting list, a launch notification or a simple newsletter signup. It is not a form builder with conditional fields, and it does not send the mail for you: what it gives you is the list, which is the part a static page genuinely cannot produce. If you want a link page rather than a full site to do the collecting, the link in bio builder has a block for it. ## How to use it 1. **Put the form on your page.** An ordinary form with an email field. You keep your own markup and styling; nothing is injected into the page. 2. **Publish on a plan that includes it.** Capture starts on Business. Submissions are held against the site they arrived from. 3. **Read or export the list.** Check what has come in from the dashboard, and export when you want the addresses in a mailing tool. ## When people reach for this - **A waiting list before the product exists.** One page, one field, no infrastructure. This is the case where standing up a server to receive twenty addresses is obviously the wrong amount of work. - **A launch notification on a single page site.** A date, a description and a way to be told. Publish the page, connect a domain of your own, and it is finished. - **A downloadable document behind a name.** Ask for an address on the page that links to the PDF. The document itself stays a normal link, so nothing breaks if someone shares it. ## Doing this without us There are two normal answers, and both add a moving part that has to keep working. - **What you add to the page.** Droply: A form. The page stays a file you uploaded. A third-party form service: An embedded script or an iframe from another domain. - **Where submissions live.** Droply: With the site, in the same dashboard. A third-party form service: In a second account with its own login and its own plan. - **Getting the addresses out.** Droply: Export whenever you want them elsewhere. A third-party form service: Varies, and export is sometimes a paid tier. - **Extra cost.** Droply: Included from Business upward. A third-party form service: A separate subscription on top of hosting. Compared against the general pattern of embedded form services rather than one named product. Checked September 2026. ## When this is not the right tool This collects addresses. Anything past that is a job for a tool built for it. - It does not send email. There is no campaign editor, no scheduling and no delivery reporting. - It is not a general form builder. Multi-step forms, file uploads inside a form and conditional fields are out of scope. - There is no double opt-in flow built in, so if your jurisdiction requires one, you will want a mailing tool that runs it. - You are the controller of the addresses you collect. Say so on your page, and keep your own privacy notice accurate. ## Frequently asked questions ### Which plan includes email capture? It starts on Business. Plans below it can still show a form on a page, but there is nothing on our side to receive the submission. ### Do I need a backend? No, and that is the point. Your page stays static; the submission is received by us rather than by a server you maintain. ### Can I export the addresses? Yes. Export is part of the feature, not a separate tier, because a list you cannot take with you is not really your list. ### Does it send the welcome email? No. It collects addresses and stops there. Sending is a job for a mailing tool, and this is designed to hand the list to one. ### Can I use my own form markup? Yes. It is an ordinary form in your own page, so the layout, the styling and the field labels are yours. ### What about spam submissions? Submissions are rate limited, but no filter is perfect on a public page. Check the list before you import it anywhere, the same as with any public form. ## Related features - [Site analytics](https://droply.host/features/analytics) - [Custom domains](https://droply.host/features/custom-domains) - [Team seats](https://droply.host/features/team-seats) --- Source: https://droply.host/features/password-protection # Password protect a page you published Set one password on a site and nothing behind it is served until a visitor enters it. The check happens at the edge, before any file leaves the server. ## Plan availability Password protection starts on Starter. - **Free:** not included - **Starter:** included - **Pro:** included - **Business:** included - **Enterprise:** included ## A door in front of the files, not a notice on the page The password is checked by the server that would otherwise hand over the bytes. If it has not been entered, there are no bytes to hand over. Turn it on for a site and every request to that site meets a prompt first: the page, its stylesheet, its images, a PDF sitting in a subfolder, all of it. Once a visitor gets the password right, their browser holds a cookie for that site and the rest of the visit is normal. There are no accounts to create, no invitations to send and nothing for the visitor to sign up for, which matters when the person you are sending it to is a client rather than a colleague. The distinction worth understanding is between this and a password written into the page itself. A JavaScript prompt in an HTML file is decoration: the file has already been downloaded by the time it runs, so anyone who opens the source can read what it was hiding, and the assets around it were never protected at all. Here the check happens before the response is written, so a direct link to an asset is refused the same way the page is. Wrong guesses from one visitor are locked out after a handful of tries, which is what actually stops someone working through a list. ## How to use it 1. **Publish the site.** Upload as normal and check the page works. Protection is a setting on the site, not something baked into the files. 2. **Set a password.** Open the site in the dashboard and set one. It is stored hashed, so nobody, including us, reads it back out later. 3. **Send the link and the password separately.** Two channels beat one. The link is safe to put in a calendar invite; the password is not. ## When people reach for this - **A build a client is reviewing before launch.** Work in progress should not turn up in a search result or get forwarded past the person who asked for it. Client website preview is this exact workflow, written out. - **A document meant for one recipient.** A quote, a proposal or a contract shared as a PDF on a link is easier to send than an attachment and easier to withdraw afterwards. - **An internal page you would rather not publish openly.** A runbook, a price sheet or an event brief that needs to be reachable from a phone, without becoming public. Pair it with an expiry date if it is only relevant for a week. ## Doing this without us The two usual substitutes both look like protection, and one of them is not. - **When the check happens.** Droply: Before the response is written. A JavaScript password in the page: After the file has already been downloaded. - **Images, PDFs and other assets.** Droply: Covered by the same gate. A JavaScript password in the page: Not covered. A direct link opens them. - **Reading the password out of the source.** Droply: Not possible; it is stored hashed on our side. A JavaScript password in the page: Usually one click in view-source. - **Guessing attempts.** Droply: Locked after a handful of wrong tries. A JavaScript password in the page: Unlimited and invisible. - **What the visitor has to do.** Droply: Type a password once. A JavaScript password in the page: Type a password once, with none of the above. Compared against the client-side password snippets commonly recommended for static sites. Checked September 2026. ## When this is not the right tool This is one shared password for one site. It is deliberately not an access control system. - There is one password per site, not one per visitor, so you cannot tell two recipients apart or revoke one of them. - There are no user accounts, roles or per-page permissions for visitors. - Anyone who has the password can pass it on. If that is a real risk, add an expiry so the window is short. - It protects a site hosted here. It cannot put a gate in front of a page hosted somewhere else. ## Frequently asked questions ### Which plan includes password protection? It starts on Starter. Sites on plans below it are public, and free sites are additionally served with a noindex header so they do not appear in search results. ### Are the images and PDFs protected too? Yes. The check runs before any file is served, so a direct link to an asset inside a protected site is refused exactly like the page is. ### Do my visitors need an account? No. They type one password and nothing else. There is no sign-up, no email verification and no account for them to manage. ### Can I use a different password per person? No. There is one password per site. If you need to tell recipients apart, publish separate sites, or use an expiry so the shared password stops working on a date. ### Can somebody read the password from the page source? No. It never reaches the browser. It is stored as a hash on our side and compared server-side, which is the difference between this and a script in your HTML. ### What stops someone guessing it? Repeated wrong answers from the same network are refused after a small number of attempts, before the comparison even runs, so working through a word list is not practical. ## Related features - [Expiring links](https://droply.host/features/expiring-links) - [Custom domains](https://droply.host/features/custom-domains) - [Version rollback](https://droply.host/features/version-rollback) --- Source: https://droply.host/features/expiring-links # Expiring links that stop working on a date you pick Give a published site a deadline of six hours, a day, a week, a month, or an exact moment. When it passes, the link shows an expired notice instead of your content. ## Plan availability Scheduling an expiry starts on Starter. Turning one off is never gated, on any plan. - **Free:** not included - **Starter:** included - **Pro:** included - **Business:** included - **Enterprise:** included ## A deadline on the link, not a delete on the files At the moment you chose, the address stops serving your content and starts serving a short notice saying the link has expired. You pick from six hours, one day, seven days, thirty days, or an exact date and time in your own timezone. Nothing is destroyed when it fires: the deployment stays where it is, and bringing the site back is a matter of setting a new date, at which point the same address serves the same content again. That is the difference between an expiry and a deletion, and it is deliberate, because the most common reason to want an expiry is that you are not sure yet. A reminder goes out before the deadline so an expiry does not surprise you, and the switch that turns one off is available on every plan including the free one. That second part matters more than it sounds: a control that can be armed on a paid plan and not disarmed after a downgrade is a trap, so cancelling is always allowed. If what you want is the opposite, a link that never goes anywhere, that is just publishing normally; every plan's links are permanent by default, which is not true of the drag-and-drop tools that delete an unclaimed upload after an hour. ## How to use it 1. **Publish the site.** Upload as normal. The expiry is a setting on the site, so you can add it now or a week from now. 2. **Pick a deadline.** Six hours, a day, a week, a month, or an exact moment. Custom times are read in your browser's timezone, so midnight means your midnight. 3. **Let it fire, or change your mind.** You get a reminder before it happens. Afterwards, setting a new date puts the same content back at the same address. ## When people reach for this - **A proposal that should not circulate forever.** A quote with prices in it has a natural shelf life. Give it two weeks, and combine it with a password if it should not be forwarded either. - **An event page that stops being true.** Directions, a schedule and a dress code are actively unhelpful the week after the event. An expiry stops a stale page turning up in a search months later. - **A file drop for one afternoon.** Sending a large asset to a collaborator does not need to be permanent. Six hours is usually longer than anyone needs. Sharing a PDF as a link covers the document case. ## Doing this without us The two habits this replaces are deleting things by hand and never deleting them at all. - **What happens on the day.** Droply: The link expires on its own, whether or not you are looking. Remembering to take it down: Nothing, unless you remember. - **Getting it back.** Droply: Set a new date; the same content returns to the same address. Remembering to take it down: Re-upload and hope the address is still free. - **What a visitor sees afterwards.** Droply: A short notice saying the link has expired. Remembering to take it down: A missing page, or the stale content forever. - **Warning before it happens.** Droply: A reminder before the deadline. Remembering to take it down: A calendar entry you also have to set. Compared against manual takedown, which is the actual alternative for most people sharing a temporary link. Checked September 2026. ## When this is not the right tool An expiry controls an address. It is not a guarantee about copies that already exist. - Anyone who downloaded the file before the deadline still has it. Expiry stops new access, it does not reach into a laptop. - It applies to a whole site, not to one page inside it. - It is not a delete. The content is retained so it can be restored, which is the point, but if you want the files gone you should delete the site instead. Version history is a separate setting and follows its own plan rules. - A search engine may still show a cached description for a while after the link expires. ## Frequently asked questions ### Which plan lets me set an expiry? Scheduling one starts on Starter. Removing an expiry that is already set is available on every plan, including free, so a downgrade can never leave you unable to cancel it. ### What can I choose? Six hours, one day, seven days, thirty days, or an exact date and time. Custom moments are interpreted in your browser's timezone rather than ours. ### What does a visitor see after it expires? A short page saying the link has expired. They do not see your content, and they do not see a raw server error. ### Is my content deleted when it expires? No. The deployment is kept and the site can be brought back by setting a new date, at which point the same address serves the same content again. ### Will I be warned before it fires? Yes. A reminder is sent ahead of the deadline. If you set a deadline that is already inside that window, the reminder is skipped rather than sent late. ### Do links expire by default? No. Every link here is permanent unless you give it a deadline, including on the free plan. That is different from the anonymous drop tools, which delete an unclaimed upload after about an hour. ## Related features - [Password protection](https://droply.host/features/password-protection) - [Version rollback](https://droply.host/features/version-rollback) - [QR codes](https://droply.host/features/qr-codes) --- Source: https://droply.host/features/version-rollback # Rollback to the version you published before Every upload is kept as its own version. If the new one is wrong, put the previous one back on the same address in one step, with no re-upload. ## Plan availability Rolling back to an earlier version starts on Pro, which keeps 10 of them. - **Free:** not included - **Starter:** not included - **Pro:** included - **Business:** included - **Enterprise:** included ## Publishing is additive, so undo is cheap A new upload does not overwrite the old one. It becomes a new version, and the address is pointed at it. Every time you publish, the files are extracted into their own immutable folder and the live address is switched to point there. The previous folder is still on disk, untouched. Rolling back is that switch running in the other direction: the address moves back to the earlier version and the site is correct again in seconds, without you finding the old ZIP, without a re-upload, and without the address changing at any point. How far back you can go depends on the plan, because keeping versions costs storage; Pro keeps 10. Older versions fall off the end as new ones arrive, so the list is a recent history rather than an archive, and it is measured in publishes rather than in days: a site you update twice a year keeps a much longer stretch of calendar time than one you update twice a week. This is the feature that makes it reasonable to publish a change you are not certain about, which is most of them. It pairs naturally with a preview link for the changes you would rather not publish at all until somebody has looked, and it is the reason the same-URL rule works in practice: re-publishing at will is only comfortable if getting back is trivial. It also changes what a bad deploy costs. Without it, the honest answer to "the new version is broken" is to fix it under pressure, because there is nothing to go back to; with it, the answer is to restore, then fix it properly, which is a different afternoon. ## How to use it 1. **Publish as usual.** Each upload becomes a version automatically. There is nothing to enable and no commit message to write. 2. **Open the version list.** The site's history shows every kept version with when it was published and which one is live. 3. **Restore one.** Pick a version and put it back. The address does not change, so links you already sent keep working. ## When people reach for this - **A build that broke something after it went out.** A missing asset or a wrong path is obvious only once it is live. Rolling back buys the time to fix it properly instead of fixing it in a hurry. - **A client who preferred the previous version.** This happens, and re-uploading last week's export is a bad way to answer it. See static hosting for freelancers for the surrounding workflow. - **A price list or menu that changed too early.** Content that goes out on a schedule sometimes goes out a day early. Rolling back is faster than editing it back. ## Doing this without us Without kept versions, undo means finding the old files and uploading them again. - **Finding the previous build.** Droply: It is in the site's version list. Re-uploading an older export: Wherever you happened to save it, if you did. - **How long it takes.** Droply: A pointer switch, in seconds. Re-uploading an older export: A rebuild, or a re-upload, or both. - **Whether the address changes.** Droply: It does not. Re-uploading an older export: It should not, but only if you overwrite in place correctly. - **How far back you can go.** Droply: 10 versions on Pro. Re-uploading an older export: As far as your own backups reach. Compared against keeping your own copies of each build, which is what a static site without version history requires. Checked September 2026. ## When this is not the right tool This is undo for what you published. It is not source control and it is not a backup service. - It keeps published output, not your project source. Your repository is still where the source belongs. - There are no branches, no diffs between versions and no merge. It is a list of what was live, in order. - History depth is limited per plan, so a very old version eventually falls off the end. - Free plans keep the current version only, which means the previous one is not there to restore. ## Frequently asked questions ### Which plan includes rollback? Restoring an earlier version starts on Pro, which keeps 10 versions. Plans below it publish normally; what they do not get is the list to restore from. ### Does the URL change when I roll back? No. The address belongs to the site rather than to a version, so rolling back is invisible to anyone holding a link. ### How long does it take? Seconds. The files for the older version are already on disk, so restoring is a pointer switch rather than an upload. ### How many versions are kept? It depends on the plan, because each kept version uses storage. Pro keeps 10, and higher tiers keep more. ### Can I roll back after connecting a custom domain? Yes. A custom domain points at the site, not at a version, so it follows the rollback like any other address. ### Is this a backup of my project? No. It stores what you published, which is your built output. Keep your source in version control the way you would anyway. ## Related features - [Expiring links](https://droply.host/features/expiring-links) - [Site import](https://droply.host/features/site-import) - [Password protection](https://droply.host/features/password-protection) --- Source: https://droply.host/features/team-seats # Team seats and shared site access Invite colleagues into the account so publishing is not one person's login. Access can be scoped, so a contractor sees the sites they work on and nothing else. ## Plan availability Seats start on Business, which includes 5. The largest plan includes 25. - **Free:** single user - **Starter:** single user - **Pro:** single user - **Business:** 5 seats - **Enterprise:** 25 seats ## Publishing stops being one person's password Each colleague gets their own sign-in, their own audit trail, and access that can be narrowed to a subset of the sites. A shared login is the default arrangement in small teams and it fails in the same three ways every time: nobody can tell who published the broken version, the person who leaves still has the password, and the one account holder becomes a bottleneck the week they are away. Seats fix all three by giving each person their own access. Removing somebody is one action rather than a password change that has to be redistributed to everybody else. Access can also be narrowed. Sites are organised into spaces, and a teammate can be granted specific spaces rather than the whole account, which is how you give a contractor the two client sites they are working on without handing over the rest of your portfolio. Grant nothing and they see everything, so scoping is something you switch on deliberately; the dashboard is explicit about which of the two a person currently has. For agencies this pairs with custom domains per client and the freelancer workflow. ## How to use it 1. **Move to a plan with seats.** Seats start on Business, which includes 5. The plan sets how many people can be in the account at once. 2. **Invite by email.** They accept, set up their own sign-in, and appear in the account with their own name against their actions. 3. **Scope them if you need to.** Grant specific spaces to limit what a teammate can reach. Leave it open and they can work across the whole account. ## When people reach for this - **An agency with a contractor on two projects.** Scope them to those two client spaces. When the engagement ends, remove the seat, and nothing else about the account has to change. - **A marketing team that publishes without waiting.** Three people who each need to put a landing page up should not be queueing behind one login. Everyone publishes under their own name. - **A studio handing a project over.** Work stays in the account rather than in one designer's personal login, which is what makes a handover possible at all. ## Doing this without us The alternative is one shared password, which works right up until the moment it matters. - **Who published this version.** Droply: Recorded against the person who did it. A shared login: Unknowable. - **Someone leaves.** Droply: Remove their seat. A shared login: Change the password, tell everyone else the new one. - **Limiting what a contractor sees.** Droply: Grant them specific spaces. A shared login: Not possible; one login sees everything. - **Two people working at once.** Droply: Normal. Each has their own session. A shared login: Workable, but nobody can tell the sessions apart. - **Second factor per person.** Droply: Each account arms its own. A shared login: One shared secret, or none. Compared against sharing a single account, which is the arrangement most small teams start with. Checked September 2026. ## When this is not the right tool Seats are for people who work on the sites. They are not a way to give visitors accounts. - This is not visitor authentication. To restrict who can open a published page, use password protection instead. - Seat counts are set by the plan, so a bigger team needs a bigger plan rather than a per-seat add-on. - Permissions are per space rather than per action. There is no read-only reviewer role. - Billing stays with the account owner. Teammates cannot change the plan or the payment method. ## Frequently asked questions ### Which plan includes team seats? They start on Business, which includes 5. The largest plan includes 25. Plans below that are single-user accounts. ### Can I limit what a teammate can see? Yes. Grant them specific spaces and they reach only the sites in those spaces. A teammate with no grants at all has access to everything, so scoping is a deliberate step rather than a default. ### What happens when someone leaves? Remove their seat. Their access ends immediately and the sites stay in the account, which is the main reason not to run a team on one shared password. ### Do teammates need their own subscription? No. Seats are part of the account's plan. Each person signs in as themselves, and billing stays with the owner. ### Can two people publish at the same time? Yes. Each seat is a normal sign-in with its own session, and publishes are recorded against whoever made them. ### Can a teammate change the plan? No. Billing and plan changes stay with the account owner, so a seat cannot upgrade, downgrade or cancel the subscription. ## Related features - [Custom domains](https://droply.host/features/custom-domains) - [Public API](https://droply.host/features/api) - [Password protection](https://droply.host/features/password-protection) --- Source: https://droply.host/features/site-import # Import a site from its address Paste the address of a static site hosted somewhere else and we fetch its pages, styles, images and fonts, then publish the copy on a link of yours. ## Plan availability Importing is available on every plan, including the free one. Plan upload and storage limits still apply to the result. - **Free:** included - **Starter:** included - **Pro:** included - **Business:** included - **Enterprise:** included ## A crawl, a rewrite, and a normal publish We fetch the address you give us, follow its internal links, collect what those pages need, and rewrite the references so the copy works on its own. The crawler starts at the address you paste and walks the site's own links up to 40 pages and 600 assets, taking the HTML, the stylesheets, the images and the fonts. Then it rewrites the links and asset references so nothing in the copy points back at the original host, packages the result, and runs it through the same publish pipeline as a file you would have dropped in yourself. What you end up with is an ordinary site here, with its own address, its own version history and its own settings. This exists because the hard part of leaving a host is rarely the hosting. It is finding the files, and on an old site there frequently is no build any more: the person who made it is gone, the source is gone, and the only surviving copy is the one on the internet. Importing turns that into something you can hold. If what you have is already a folder or a ZIP, skip this and use the ZIP upload, which is faster and exact. ## How to use it 1. **Paste the address.** The public URL of the site you want copied. It has to be reachable without a password, because the crawler sees only what a visitor sees. 2. **Let the crawl run.** Pages and assets are fetched under a cap, then the references are rewritten so the copy stands on its own. 3. **Review and publish.** The result becomes a site here, on your own link. Check it, then connect a domain if it is replacing the original. ## When people reach for this - **Rescuing a site whose source is gone.** An old brochure site with no repository and no build. Import it, and you have a copy you can host, edit and keep. - **Leaving a host that is shutting down or getting expensive.** Copy first, compare, then switch the DNS. Nothing has to be taken down while you decide. - **Taking a snapshot before a redesign.** Keep the current site on a link of its own so the old version is still reachable while the new one is built. ## Doing this without us The manual version is a site mirroring tool plus a pile of path fixes. - **Getting the files.** Droply: Paste a URL. A command-line mirroring tool: Install a tool and get its flags right. - **Fixing absolute paths.** Droply: Rewritten during the import. A command-line mirroring tool: A find-and-replace pass you do yourself. - **Publishing the result.** Droply: Same step. It comes out live. A command-line mirroring tool: A separate upload to a separate host. - **Cost.** Droply: Included on every plan, including the free one. A command-line mirroring tool: Free, plus the afternoon. Compared against the general practice of mirroring a site locally with a command-line tool. Checked September 2026. ## When this is not the right tool An import copies what a visitor can see. Anything the original site produced on its server is not visible to a visitor. - A dynamic site does not come across as a dynamic site. A WordPress blog imports as flat pages, with no admin, no comments and no search. - Anything behind a login, a paywall or a password cannot be fetched, because the crawler is an ordinary anonymous visitor. - A page that builds itself in the browser from an API call will import as the empty shell it serves. - The crawl is capped at 40 pages, so a large site comes across partially. - Copy only what you have the right to copy. Importing someone else's site does not make it yours. ## Frequently asked questions ### Which plan includes site import? It is available on every plan, including the free one. Your plan's upload size and storage limits still apply to the imported result, so a very large site may need a bigger plan to publish. ### How many pages can it copy? Up to 40 pages and 600 assets per import. Bigger sites are copied partially rather than refused, so you get the front of the site rather than nothing. ### Will my WordPress site work after importing? The pages will be there and they will look right, but it will be a static copy. There is no admin, no comment form and no server-side search, because none of that is something a visitor can download. ### Can it import a site behind a password? No. The crawler fetches as an anonymous visitor, so it sees exactly what the public sees and nothing behind a login. ### Does the original site change? No. Importing is a read. Nothing is altered at the source, and the original stays online until you decide otherwise. ### What if the import misses something? You can upload the missing files into the same site afterwards, or use a ZIP upload if you can get an exact copy of the original folder. ## Related features - [Version rollback](https://droply.host/features/version-rollback) - [Custom domains](https://droply.host/features/custom-domains) - [Public API](https://droply.host/features/api) --- Source: https://droply.host/features/api # Publish from a script with the API A small REST API for creating sites, uploading a deployment and reading what happened, with an OpenAPI description you can generate a client from. ## Plan availability Raw API tokens start on Pro. The first-party extensions sign in separately and work on every plan. - **Free:** not included - **Starter:** not included - **Pro:** included - **Business:** included - **Enterprise:** included ## The same publish, without the browser A token, a POST with your build, and the site is live. It is the dashboard's publish path with a different front door. You create a token in the dashboard, then call the API to list your sites, create one, and upload a deployment to it. The response tells you the live address and what state the deployment is in, so a script can wait for it rather than guessing. The whole surface is described in the API reference and in a machine-readable OpenAPI 3.1 document, which is enough for most generators to produce a client without you writing one. The obvious use is a release step: your build runs wherever it already runs, and the last line publishes the output here. That is deliberately different from a Git integration. We do not watch a repository and we do not run your build, so nothing here needs access to your source; you build where you already build and hand us the folder. Rate limits are per plan and per token, so a runaway loop in a script hits a ceiling rather than your bill. ## How to use it 1. **Create a token.** Tokens live in the dashboard under API tokens, and each one is named and revocable on its own. 2. **Call the API.** Create a site if you need one, then upload your built folder as a deployment. The reference has the exact calls. 3. **Read the result.** The response carries the live address and the deployment state, so your script can fail loudly instead of assuming it worked. ## When people reach for this - **A release step at the end of your build.** The last command in your pipeline publishes the output. See the framework build guides for what each toolchain writes and where. - **Publishing generated reports on a schedule.** A nightly job that renders HTML and posts it, so the same address always has yesterday's numbers on it. - **A tool of your own that hands users a link.** An internal generator that needs somewhere to put its output. Publish through the API and give the person a URL instead of a download. ## Doing this without us The comparison that matters is not another API, it is the Git-based platforms this deliberately is not. - **What triggers a publish.** Droply: Your call, whenever you decide. A Git-connected platform: A push to a watched branch. - **Access to your source.** Droply: None. We never see the repository. A Git-connected platform: Repository access is the integration. - **Where the build runs.** Droply: Wherever it already runs. A Git-connected platform: On their builders, in their environment. - **Publishing without a repository at all.** Droply: Normal. There is no repository in the model. A Git-connected platform: Usually needs a CLI path instead. - **What you send.** Droply: The finished folder. A Git-connected platform: The source, plus a build configuration. Compared against the Git-integration model used by the developer platforms, not against a specific vendor. Checked September 2026. ## When this is not the right tool This publishes static output. It is not a build service and it is not a general file API. - There is no Git integration, no webhook on push and no build step. You build, then you upload. - It serves what you upload. It cannot run server-side code, so an API that needs to execute your application is out of scope. - Raw tokens are a paid feature. If all you want is to publish from an editor or a browser, the VS Code extension does that on every plan. - Rate limits and plan limits apply to API calls exactly as they do in the dashboard. ## Frequently asked questions ### Which plan includes API access? Raw API tokens start on Pro. That is separate from the first-party extensions, which sign in with an emailed code and work on every plan including free. ### Is there an OpenAPI description? Yes, OpenAPI 3.1, served as JSON. Most client generators will take it as-is, and the reference links to it. ### Can I deploy from CI? Yes. That is the main use. Your build runs where it already runs, and one call at the end uploads the output folder. ### Does it connect to my Git repository? No, and it is not planned. We never ask for repository access, which also means nothing here can read your source. ### Can I revoke a token? Yes. Tokens are listed in the dashboard, named, and revocable individually, so a token you put in a CI job can be replaced without touching the others. ### Are there rate limits? Yes, per plan and keyed per token, so one noisy script cannot spend another one's allowance. ## Related features - [VS Code extension](https://droply.host/features/vscode-extension) - [Chrome extension](https://droply.host/features/chrome-extension) - [Team seats](https://droply.host/features/team-seats) --- Source: https://droply.host/features/chrome-extension # The Chrome extension publishes from your toolbar A side panel that takes a file or a block of pasted HTML and puts it on a live link, without going to the dashboard or leaving the tab you are in. ## Plan availability The extension works on every plan, free included. It signs in with an emailed code rather than a raw API token, which is why it is not gated the way the API is. - **Free:** included - **Starter:** included - **Pro:** included - **Business:** included - **Enterprise:** included ## One click from the toolbar to a link Pin the icon, open the panel, drop a file or paste HTML, and the panel hands back the live address. The extension is a side panel rather than a popup, which means it stays open while you work in the page beside it. You either drag a file onto it or paste a block of HTML into it, and it publishes through exactly the same pipeline as the dashboard: the same size limits, the same security check on the deploy, the same site list afterwards. The result appears in your account like anything else, so it can get a domain or a password later without being republished. It signs in with a code sent to your email, and the credential it stores is scoped so it can do one thing: publish. That is why it works on every plan including free, while raw API tokens are a paid feature. The two are genuinely different credentials, and the distinction is worth knowing before you go looking for a token you do not need. The panel is the shortest path from "I have this HTML in front of me" to "here is a link", which in practice is most of what people want from a static host. ## How to use it 1. **Install it and pin the icon.** Install from the Chrome Web Store listing, then pin the icon so the panel is one click away. Any Chromium browser that loads MV3 extensions will do. 2. **Sign in with an emailed code.** Enter the email on your account and paste the code we send. No password and no token to copy. 3. **Drop a file or paste HTML.** The panel publishes it and shows you the live address. It appears in your dashboard alongside everything else. ## When people reach for this - **HTML an assistant just wrote for you.** Copy the block out of the chat, paste it into the panel, get a link. Hosting an AI-generated website covers what to do when the output is a whole project rather than one file. - **A file somebody needs right now.** A PDF or an image that has to be a link rather than an attachment, without opening another tab to do it. - **A quick check of something you are writing.** Publish a draft page, look at it on your phone, then re-publish. The address stays the same each time. ## Doing this without us The alternative is the dashboard, which is fine, and a few more steps. - **Leaving the page you are on.** Droply: No. The panel opens beside it. Going to the dashboard: A new tab, and back again afterwards. - **Publishing pasted HTML.** Droply: Paste into the panel. Going to the dashboard: Save it as a file first, then upload it. - **Signing in.** Droply: Once, with an emailed code. Going to the dashboard: Whenever the session lapses. - **What it costs.** Droply: Nothing, on every plan including free. Going to the dashboard: Nothing, on every plan including free. Compared against the dashboard upload flow, which is the same product and the honest baseline here. Checked September 2026. ## When this is not the right tool It is a publish button. Managing what you published still happens in the dashboard. - It does not manage sites. Domains, passwords, expiry and rollback are dashboard settings. - It publishes what you hand it. It does not build a project, so a framework app still needs a build first. - It needs an existing account. Sign-up and billing stay on the site. - Plan limits apply. An upload over your plan's size cap is refused in the panel the same way it would be anywhere else. ## Frequently asked questions ### Does the extension cost anything? No. It works on every plan, including free, because it signs in with a scoped credential rather than a raw API token. ### Do I need an API token? No. It sends a code to your email and stores a credential that can only publish. Raw API tokens are a separate, paid feature; see the API page if that is what you are after. ### Which browsers does it work in? Chrome, and other Chromium browsers that load MV3 extensions. There is no Firefox or Safari build. ### Can I publish HTML I copied from somewhere? Yes. Paste it into the panel and it is published as a page. You do not have to save it as a file first. ### Where do the sites go? Into your account, exactly like a dashboard upload. They appear in the same list and take the same settings afterwards. ### Can I sign out of it? Yes, and you can also revoke its credential from the dashboard's token list, which is the right move if you lose the machine. ## Related features - [VS Code extension](https://droply.host/features/vscode-extension) - [Public API](https://droply.host/features/api) - [QR codes](https://droply.host/features/qr-codes) --- Source: https://droply.host/features/vscode-extension # The VS Code extension publishes a built folder Pick the folder you just built, publish it without leaving the editor, and get the live address back in the panel. Works on every plan, free included. ## Plan availability The extension works on every plan, free included. It signs in with an emailed code rather than a raw API token, which is why it is not gated the way the API is. - **Free:** included - **Starter:** included - **Pro:** included - **Business:** included - **Enterprise:** included ## The last step of the build, inside the editor Choose the output folder, publish, and the panel hands back the address. No terminal, no token, no browser tab. You run your build the way you always do, then open the panel and pick the folder it wrote: dist, build, _site, whatever your toolchain produces. The extension packages that folder and publishes it through the same pipeline as everything else, then shows you the live link. Re-publishing the same site later keeps the same address, so the link you pasted into a message stays correct as you iterate. Like the browser extension, it signs in with a code sent to your email and holds a credential scoped to publishing, which is why it works on every plan including free. If you would rather script it than click it, the API does the same job from a command line on the plans that include tokens. And if you are not sure which folder is the one to publish, the framework build guides name the build command and the output folder for each toolchain we support. ## How to use it 1. **Install it from the Marketplace.** The extension adds a panel to the sidebar. It works in VS Code and in the forks that load Marketplace extensions. 2. **Sign in with an emailed code.** Enter your account email and paste the code. There is also a token option if you prefer one and your plan includes tokens. 3. **Choose the folder and publish.** Pick your build output. The panel shows the live address when it is done, and re-publishing keeps the same one. ## When people reach for this - **Showing a build to somebody before it is finished.** Publish the output, send the link, keep working. Client website preview covers the review side, including how to keep it private. - **A static site you rebuild often.** A docs site or a portfolio that changes weekly. Build, publish from the panel, done, with the previous version still there if the new one is wrong. - **Working on a machine you would rather not put a token on.** The emailed code signs you in without a long-lived key in your settings file, and the credential can be revoked from the dashboard. ## Doing this without us The alternatives are a terminal command or a trip to the browser. Both work; both are more steps. - **Preparing the upload.** Droply: Pick the folder in the panel. Zipping and uploading by hand: Zip it yourself, and get the root right. - **Leaving the editor.** Droply: No. Zipping and uploading by hand: A browser tab, every time. - **Credentials on the machine.** Droply: A scoped, revocable sign-in. Zipping and uploading by hand: A browser session, or a token in a file. - **Cost.** Droply: Nothing, on every plan including free. Zipping and uploading by hand: Nothing, plus the extra steps. Compared against zipping a build folder and uploading it through the dashboard, which is the same product and the honest baseline. Checked September 2026. ## When this is not the right tool It publishes a folder. It does not turn the editor into a build server. - It does not run your build. Run it yourself, then publish the output folder. - It publishes static output only, so a project that needs a server at runtime is out of scope whatever you point it at. - Uploads over your plan's size cap are refused with an error rather than silently truncated. - Site settings such as domains, passwords and expiry live in the dashboard, not in the panel. ## Frequently asked questions ### Does the VS Code extension cost anything? No. It works on every plan, free included, because it signs in with a scoped publish credential rather than a raw API token. ### Do I need an API token for it? No. An emailed code is enough. There is a token option if you prefer one and your plan includes tokens, but it is not required. ### Does it build my project? No. Run your build yourself and publish the folder it writes. The build guides list the command and the output folder per framework. ### Does re-publishing change the address? No. Publishing to the same site keeps the same address, which is what makes it safe to send a link before the site is finished. ### Does it work in VS Code forks? It works in editors that load Marketplace extensions. Availability in a given fork depends on that fork's extension registry rather than on us. ### What if my build is too big? The upload is refused with a clear error. Publish a smaller build or move to a plan with a larger cap; the limits are the same ones the dashboard applies. ## Related features - [Public API](https://droply.host/features/api) - [Chrome extension](https://droply.host/features/chrome-extension) - [Version rollback](https://droply.host/features/version-rollback) # Tools --- Source: https://droply.host/tools # Free browser tools Format, validate and convert files locally in the browser. Every tool runs client side: nothing is uploaded and no account is needed. - [JSON Beautifier](https://droply.host/tools/json-beautifier): Free online JSON beautifier and pretty printer. Paste messy JSON and get clean, indented, readable output instantly, all in your browser, nothing uploaded. - [JSON Minifier](https://droply.host/tools/json-minifier): Free online JSON minifier. Strip whitespace and line breaks to shrink JSON for faster APIs and smaller payloads. Runs in your browser, never uploaded. - [JSON Validator](https://droply.host/tools/json-validator): Free online JSON validator and syntax checker. Find the exact line and reason your JSON is invalid, then fix it fast, all in your browser, never uploaded. - [JSON to XML Converter](https://droply.host/tools/json-to-xml): Free online JSON to XML converter. Turn any JSON object or array into clean, well-formed XML instantly, processed in your browser and never uploaded. - [XML to JSON Converter](https://droply.host/tools/xml-to-json): Free online XML to JSON converter. Parse any XML document into clean, structured JSON in one click, done entirely in your browser and never uploaded. - [JSON to CSV Converter](https://droply.host/tools/json-to-csv): Free online JSON to CSV converter. Flatten a JSON array into a clean, spreadsheet-ready CSV for Excel or Google Sheets, in your browser, never uploaded. - [HTML Formatter](https://droply.host/tools/html-formatter): Free online HTML formatter and beautifier. Paste messy or minified HTML and get clean, properly indented markup instantly, in your browser, never uploaded. - [HTML Viewer](https://droply.host/tools/html-viewer): Free online HTML viewer. Paste HTML and see it rendered live, with the formatted source alongside. Runs in a safe browser sandbox, nothing is uploaded. - [HTML Validator](https://droply.host/tools/html-validator): Free online HTML checker. Spot unclosed tags, broken nesting, and missing attributes with fast structural checks that run in your browser, never uploaded. - [Test HTML](https://droply.host/tools/test-html): Free online HTML, CSS & JavaScript playground with a live preview. Write code in separate panes, see it run instantly, then publish it to a live page. - [HTML to Markdown](https://droply.host/tools/html-to-markdown): Free online HTML to Markdown converter. Paste HTML or drop a file and get clean, GitHub-flavored Markdown instantly, in your browser, nothing uploaded. - [Markdown to HTML](https://droply.host/tools/markdown-to-html): Free online Markdown to HTML converter with live preview. Turn GitHub-flavored Markdown into clean, safe HTML that runs in your browser, never uploaded. - [PDF Viewer](https://droply.host/tools/pdf-viewer): Free online PDF viewer. Open and read any PDF in your browser, no upload, no sign-up. Pages render locally and privately, and hosting it is one click. - [Meta Tag Generator](https://droply.host/tools/meta-tag-generator): Free meta tag generator. Fill in a title, description and image, then get the title, description, Open Graph and Twitter tags ready to paste into a page. - [Open Graph Checker](https://droply.host/tools/open-graph-checker): Free Open Graph checker. Enter a URL and see the title, description, image and card tags a crawler actually reads, plus what is missing and why it matters. - [Favicon Generator](https://droply.host/tools/favicon-generator): Free favicon generator. Drop an image and get every size a browser and a phone asks for, as PNGs plus the link tags to paste, generated in your browser. - [Robots.txt Generator](https://droply.host/tools/robots-txt-generator): Free robots.txt generator. Choose what crawlers may fetch, add disallow rules and a sitemap line, and get a valid robots.txt you can download or publish. - [Sitemap Generator](https://droply.host/tools/sitemap-generator): Free XML sitemap generator. Paste a list of URLs and get a valid sitemap.xml with optional lastmod dates, ready to download, publish or cite in robots.txt. - [Redirect Generator](https://droply.host/tools/redirect-generator): Free redirect generator. Paste your old and new paths and get the rules in _redirects, .htaccess and Nginx syntax, with the status code explained for each. - [Webpage to PDF](https://droply.host/tools/webpage-to-pdf): How to save any webpage as a PDF using the print dialog already in your browser, what breaks in the export, and how to put the result on a shareable link. --- Source: https://droply.host/tools/json-beautifier # JSON Beautifier & Formatter Paste or drop a JSON file and get clean, indented, readable output in one click. Everything runs in your browser, so your data never leaves your device, and when you are happy with the result you can publish it to a live link in seconds. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste or drop your JSON.** Paste your JSON into the editor, or drag and drop a .json file onto the page. 2. **Beautify it.** Click Beautify to instantly indent and format the JSON into clean, readable output. 3. **Copy, download, or publish.** Copy the formatted JSON, download it as a file, or publish it to a live HTTPS link to share. ## Frequently asked questions ### Is this JSON beautifier free? Yes, completely free, with no sign-up, no watermark, and no limit on how many times you can use it. ### Is my JSON uploaded anywhere? No. All formatting happens entirely in your browser using JavaScript. Your JSON is never sent to our servers, so it stays private even for confidential data. ### Is there a file size limit? There is no fixed limit. Because the work runs locally, the only real ceiling is your device’s memory. Files up to several megabytes format instantly, and much larger ones still work, just a little slower. ### Why does it say my JSON is invalid? The beautifier parses your JSON first, so it flags real syntax problems: usually a trailing comma, a single quote instead of a double quote, an unquoted key, or a missing bracket. Fix the highlighted spot and re-run. To check structure without reformatting, use the dedicated JSON Validator. ### Can I choose the indentation? Yes. You can switch between 2-space, 4-space, and tab indentation to match your project’s style, then copy or download the result. ### How do I host or share the formatted JSON? Click Publish and your formatted file goes live at its own HTTPS link in seconds, handy for sharing an API sample, a config, or a fixture with a teammate. No build step, no server setup. --- Source: https://droply.host/tools/json-minifier # JSON Minifier & Compressor Compress JSON by removing every unnecessary space and line break, producing the smallest valid payload for faster API responses and smaller config files. It all happens locally in your browser, and you can publish the minified result to a live link when you are done. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Add your JSON.** Paste your JSON or drop a .json file into the editor. 2. **Minify it.** Click Minify to strip all whitespace and line breaks and produce the smallest valid JSON. 3. **Copy, download, or publish.** Copy the minified output, download it, or publish it to a live link to share. ## Frequently asked questions ### Is the JSON minifier free? Yes, it is completely free with no sign-up and no usage limits. ### Does minifying change my data? No. Minifying only removes insignificant whitespace and newlines. Every key, value, and the exact structure are preserved, so the output parses to exactly the same data. ### Is my JSON sent to a server? Never. Minification runs 100% in your browser, so your data stays on your device and nothing is uploaded. ### Is there a size limit? No hard limit. Processing happens locally, so the practical ceiling is your device’s memory; multi-megabyte files minify in a moment. ### Why won’t my JSON minify? The tool validates before compressing, so invalid JSON is rejected. The most common causes are trailing commas, comments (not allowed in standard JSON), or unescaped characters in strings. Fix the flagged spot and try again. ### How do I host the minified JSON? Hit Publish to push the minified file straight to a live HTTPS URL, perfect for serving a compact config or fixture without standing up a server. --- Source: https://droply.host/tools/json-validator # JSON Validator & Syntax Checker Check whether your JSON is valid and pinpoint the exact line and reason when it is not, with clear, plain-English error messages. Validation runs entirely in your browser, so even sensitive payloads stay private on your device. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste your JSON.** Paste your JSON into the editor or drop a .json file onto the page. 2. **Validate it.** Click Validate to parse the JSON and surface the first error with its line and a plain-English explanation. 3. **Fix and re-check.** Correct the highlighted issue and validate again until you get a clean, valid result. ## Frequently asked questions ### Is the JSON validator free? Yes, free to use as often as you like, with no account and no limits. ### Is my JSON uploaded to validate it? No. Validation runs entirely in your browser. Nothing is sent to a server, so confidential JSON never leaves your machine. ### What does the validator check? It parses your input against the JSON standard (RFC 8259) and reports the first syntax error with its location, catching trailing commas, missing or extra brackets, unquoted keys, single quotes, and invalid escape sequences. ### What are the most common JSON errors? By far the most common are a trailing comma after the last item, using single quotes instead of double quotes, unquoted keys, and comments (which standard JSON does not allow). The error message points you at the exact spot. ### Is there a file size limit? No fixed limit. Validation runs locally, so the only constraint is your device’s memory. Large files are handled comfortably. ### My JSON is valid. How do I format or host it? Once it validates, use the JSON Beautifier to pretty-print it, or the JSON Minifier to compress it, and from either you can publish the file to a live HTTPS link. --- Source: https://droply.host/tools/json-to-xml # JSON to XML Converter Convert JSON objects and arrays into clean, well-formed XML in one click, ready for legacy systems, SOAP services, or XML-based config. The conversion happens in your browser, and you can publish the resulting XML to a live link without any setup. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste your JSON.** Paste your JSON or drop a .json file into the editor. 2. **Convert to XML.** Click Convert to transform the JSON into clean, well-formed XML. 3. **Copy, download, or publish.** Copy the XML, download it as a .xml file, or publish it to a live link. ## Frequently asked questions ### Is the JSON to XML converter free? Yes, it is completely free with no sign-up and no usage caps. ### Is my data uploaded during conversion? No. The conversion runs 100% in your browser, so your JSON and the XML it produces never touch our servers. ### How are JSON keys mapped to XML? Each JSON key becomes an XML element and nested objects become nested elements. Arrays are emitted as repeated elements, and the output is wrapped in a single root element so it is always well-formed. ### Why did my conversion fail? The converter validates the JSON first, so the usual cause is invalid JSON (a trailing comma or a missing bracket). Also note that JSON keys with characters that are illegal in XML element names need adjusting; the error message tells you which key. ### Is there a size limit? No hard limit. Everything runs locally, so the constraint is just your device’s memory; typical documents convert instantly. ### How do I host the XML output? Click Publish and the generated .xml file goes live at its own HTTPS link in seconds, with no server or build step required. --- Source: https://droply.host/tools/xml-to-json # XML to JSON Converter Turn XML documents into clean, structured JSON that is easy to use in modern JavaScript and APIs. The parsing runs entirely in your browser, keeping your data private, and the JSON result can be published to a live link in seconds. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste your XML.** Paste your XML or drop an .xml file into the editor. 2. **Convert to JSON.** Click Convert to parse the XML into clean, structured JSON. 3. **Copy, download, or publish.** Copy the JSON, download it, or publish it to a live HTTPS link. ## Frequently asked questions ### Is the XML to JSON converter free? Yes, free, unlimited, and no sign-up required. ### Is my XML sent to a server? No. Parsing and conversion happen entirely in your browser, so your XML never leaves your device. ### How are XML attributes and text handled? Elements become JSON keys, nested elements become nested objects, and repeated elements become arrays. Attributes are preserved (commonly with an @ prefix) and element text is captured so no information is lost. ### Why won’t my XML convert? The converter needs well-formed XML. The usual culprits are an unclosed tag, more than one root element, or an unescaped &, in text. The error message points you to the problem. ### Is there a size limit? No fixed limit. Because it runs locally, the only ceiling is your device’s memory, and most documents convert instantly. ### How do I host the JSON result? Hit Publish to push the converted .json file to a live HTTPS URL, ideal for sharing an API sample or fixture, with no server setup. --- Source: https://droply.host/tools/json-to-csv # JSON to CSV Converter Flatten an array of JSON objects into a tidy, spreadsheet-ready CSV you can open in Excel or Google Sheets. The conversion runs in your browser so your data stays private, and the CSV can be published to a live link in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste your JSON array.** Paste an array of JSON objects, or drop a .json file, into the editor. 2. **Convert to CSV.** Click Convert to flatten the array into a clean, spreadsheet-ready CSV. 3. **Copy, download, or publish.** Copy the CSV, download it as a .csv file, or publish it to a live link. ## Frequently asked questions ### Is the JSON to CSV converter free? Yes, completely free, with no account and no limits on use. ### Is my JSON uploaded to convert it? No. The conversion runs fully in your browser, so your data is never sent to a server and stays private. ### What JSON shape works best? An array of objects converts cleanly: each object becomes a row and each key becomes a column. Nested objects are flattened into dotted column names, and the column set is unioned across all rows so nothing is dropped. ### How are commas and quotes handled? Values containing commas, quotes, or line breaks are automatically wrapped in quotes and escaped per the CSV spec (RFC 4180), so the file opens correctly in Excel and Google Sheets. ### Is there a size limit? No hard limit. It runs locally, so the practical ceiling is your device’s memory. Large arrays convert quickly. ### How do I host or share the CSV? Click Publish and the generated .csv file is live at its own HTTPS link in seconds, a quick way to hand a data export to a colleague without email attachments. --- Source: https://droply.host/tools/html-formatter # HTML Formatter & Beautifier Paste tangled, minified, or hand-edited HTML and get clean, consistently indented markup in one click, with inline CSS and JavaScript tidied up too. Everything runs in your browser, so your code stays private, and you can publish the formatted page to a live link the moment it looks right. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste or drop your HTML.** Paste your HTML into the editor, or drag and drop an .html file onto the page. 2. **Format it.** Click Format to instantly indent the markup, including any inline CSS and JavaScript, into clean, readable output. 3. **Copy, download, or publish.** Copy the formatted HTML, download it as a file, or publish it to a live HTTPS link to share. ## Frequently asked questions ### Is this HTML formatter free? Yes, completely free, with no sign-up, no watermark, and no limit on how often you can use it. ### Is my HTML uploaded anywhere? No. All formatting happens entirely in your browser with JavaScript. Your markup is never sent to our servers, so it stays private even for confidential or internal pages. ### Does it format inline CSS and JavaScript too? Yes. As well as indenting your HTML tags, the formatter tidies the CSS inside blocks and the JavaScript inside blocks, so the whole document comes out readable. ### Can I choose the indentation? Yes. Switch between 2-space, 4-space, and tab indentation to match your project’s style, then copy or download the cleaned-up markup. ### Does formatting change how my page renders? No. The formatter only adds whitespace and line breaks between tags; it never rewrites your content, attributes, or structure, so the page renders exactly as before, just easier to read. ### How do I host the formatted HTML? Click Publish and your page goes live at its own HTTPS link in seconds, a fast way to share a prototype or a one-off page with no build step or server setup. --- Source: https://droply.host/tools/html-viewer # HTML Viewer & Live Preview Paste HTML and watch it render live as you type, with the cleaned-up source shown right beside the preview. The page renders inside a sandboxed frame in your own browser, so nothing is uploaded and any scripts are safely isolated. When you like what you see, you can publish it to a live link in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste or drop your HTML.** Paste your HTML into the editor, or drag and drop an .html file onto the page. 2. **See it render live.** Watch the page render instantly in a sandboxed preview, with the formatted source shown alongside it. 3. **Copy or publish.** Copy the tidied source, or publish the page to a live HTTPS link to share it. ## Frequently asked questions ### Is the HTML viewer free? Yes, free to use as often as you like, with no account and no usage limits. ### Is my HTML uploaded to preview it? No. The preview is rendered entirely in your browser, so your HTML is never sent to a server and even private or unfinished pages stay on your device. ### Is it safe to preview HTML that contains scripts? Yes. The preview runs inside a sandboxed iframe that is isolated from this page and from your account, so any JavaScript in the pasted HTML cannot read or change anything outside the preview. ### Do images, CSS, and links work in the preview? Inline CSS and styling render exactly as they will in a browser. Images and stylesheets that point at absolute URLs load normally; ones that rely on relative paths only appear once the page is hosted with those files alongside it. ### Can I see the formatted source too? Yes. Alongside the live preview the viewer shows your HTML cleaned up and indented, so you can read the markup and copy the tidied version in one place. ### How do I host the page I am previewing? Click Publish and the HTML goes live at its own HTTPS link in seconds, an easy way to share a quick page or prototype without a build step or any server setup. --- Source: https://droply.host/tools/html-validator # HTML Validator & Structure Checker Run quick, pragmatic structural checks on your HTML to catch the mistakes that break a page: unclosed tags, mismatched or badly nested elements, and missing required attributes. The checks run entirely in your browser, so your markup stays private. This is a fast sanity check, not full W3C conformance validation. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste or drop your HTML.** Paste your HTML into the editor, or drag and drop an .html file onto the page. 2. **Run the checks.** Click Check to scan locally for unclosed tags, broken nesting, and missing required attributes. 3. **Fix and re-check.** Jump to each flagged issue, correct it, and run the checks again until the markup is clean. ## Frequently asked questions ### Is the HTML validator free? Yes, free to use as often as you like, with no sign-up and no limits. ### Is my HTML uploaded to check it? No. Every check runs entirely in your browser. Nothing is sent to a server, so your markup never leaves your machine. ### What exactly does it check? It runs pragmatic structural checks: unclosed or mismatched tags, elements that are nested incorrectly, and missing required attributes such as alt on images. It points you at the spot so you can fix it fast. ### Is this the same as the W3C validator? No, and it does not claim to be. This is a quick local sanity check for the structural problems that most often break a page, not a full W3C conformance validation of every HTML spec rule. For a complete standards audit, run the official W3C validator as well. ### Why does it flag valid-looking HTML? The most common triggers are a tag you forgot to close, two tags closed in the wrong order, or a self-closing element written incorrectly. The message names the element and where it is, so the fix is usually quick. ### My HTML is clean. How do I format or preview it? Use the HTML Formatter to pretty-print and indent it, or the HTML Viewer to render it live in a safe sandbox and check how it looks. --- Source: https://droply.host/tools/test-html # Test HTML, CSS & JavaScript Write HTML, CSS, and JavaScript in three dedicated panes and watch the result render live as you type. It is a fast, no-setup playground for prototyping a layout, testing a snippet, or learning front-end. Your code runs in an isolated sandbox in your own browser, so nothing is uploaded, and when it works you can publish it to a live HTTPS page in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Write your HTML, CSS & JS.** Type your markup in the HTML pane, your styles in the CSS pane, and your scripts in the JavaScript pane. 2. **See it run live.** Watch the three panes render together instantly in the sandboxed preview as you edit. 3. **Add any libraries you need.** Pull in frameworks or stylesheets by adding normal script and link tags pointing at a CDN in the HTML pane. 4. **Publish to a live page.** Click Publish to bundle everything into one page and get a live HTTPS link to share. ## Frequently asked questions ### Is this HTML, CSS & JavaScript playground free? Yes, completely free, with no sign-up, no watermark, and no limit on how often you can use it. Just open it and start writing code. ### Does my code run safely? Yes. Your HTML, CSS, and JavaScript run inside an isolated sandbox in your own browser. The preview is walled off from this page and your account, and nothing is uploaded to any server. Your code stays entirely on your device. ### How does the live preview work? As you type, your three panes are combined into a single document (the CSS goes into a block and the JavaScript into a block) and rendered in the preview. The result updates instantly, so you see exactly how the page behaves. ### Can I publish or host the result? Yes. Click Publish and your HTML, CSS, and JavaScript are bundled into one page that goes live at its own HTTPS link in seconds, a fast way to share a prototype or demo with no build step or server setup. If the code came from an AI tool and does not run here, it is probably a project rather than a page: see hosting an AI-generated website and the per-tool pages for ChatGPT, Gemini and v0. ### Can I use external libraries or CDN links? Yes. Add normal and tags in the HTML pane to pull in any library or stylesheet from a CDN. Frameworks, icon sets, fonts, and more all load just as they would on a real page. ### Will my work be saved if I refresh? Your code lives in the editor while the tab is open, so a live preview never loses it. To keep a copy, publish it to a live link or copy each pane out. There is no account, so nothing is stored on our side. --- Source: https://droply.host/tools/html-to-markdown # HTML to Markdown Converter Turn web pages and rich HTML into clean, readable Markdown you can drop straight into a README, a wiki, a blog post, or your notes. Headings, lists, links, images, tables, and code blocks are all converted faithfully. Everything runs in your browser, so your content stays private, and the finished Markdown can be published to a live link in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste or drop your HTML.** Paste your HTML into the editor, or drag and drop an .html file onto the page. 2. **Convert to Markdown.** Click Convert to turn the HTML into clean, GitHub-flavored Markdown instantly. 3. **Copy, download, or publish.** Copy the Markdown, download it as a .md file, or publish it to a live HTTPS link to share. ## Frequently asked questions ### Is this HTML to Markdown converter free? Yes, completely free, with no sign-up, no watermark, and no limit on how often you can convert. ### Is my HTML uploaded anywhere? No. The conversion runs entirely in your browser with JavaScript. Your HTML is never sent to our servers, so it stays private even for confidential or internal pages. ### Which Markdown flavor does it output? It produces GitHub-Flavored Markdown (GFM), which builds on the CommonMark standard and adds tables, fenced code blocks, and strikethrough. The result renders correctly on GitHub, GitLab, and most static-site generators. ### What HTML elements are converted? Headings, paragraphs, bold and italic text, ordered and unordered lists, links, images, blockquotes, inline code, fenced code blocks, and tables all map to their Markdown equivalents. Tags that have no Markdown form are unwrapped so their text is kept rather than lost. ### Why does some HTML come through as raw tags? Markdown only covers a subset of HTML, so anything without an equivalent (such as complex layout s or embedded widgets) may be passed through as inline HTML. That is valid Markdown and renders fine; you can delete those fragments if you do not need them. ### How do I host or share the Markdown? Click Publish and the generated .md file goes live at its own HTTPS link in seconds, a quick way to share a converted doc or README without a build step or any server setup. --- Source: https://droply.host/tools/markdown-to-html # Markdown to HTML Converter Write or paste Markdown and watch it turn into clean HTML live as you type, with a rendered preview beside the source. It understands GitHub-Flavored Markdown (tables, fenced code blocks, task lists, and more) and the output is sanitized so it is safe to publish. Everything runs in your browser, your content is never uploaded, and you can push the finished page to a live link in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste or write your Markdown.** Paste your Markdown into the editor, or drag and drop a .md file onto the page. 2. **See the HTML render live.** Watch the formatted preview update as you type, with the generated HTML source shown alongside it. 3. **Copy or publish.** Copy the clean, sanitized HTML, or publish the page to a live HTTPS link to share it. ## Frequently asked questions ### Is this Markdown to HTML converter free? Yes, completely free, with no sign-up and no limit on how many times you can convert. ### Is my Markdown uploaded anywhere? No. The conversion and preview run entirely in your browser. Your Markdown is never sent to our servers, so even private drafts stay on your device. ### Which Markdown flavor is supported? It supports GitHub-Flavored Markdown (GFM), a superset of the CommonMark standard. That means tables, fenced code blocks, task lists, strikethrough, and autolinks all render the way they do on GitHub. ### Is the generated HTML safe to publish? Yes. The HTML is run through a sanitizer that strips dangerous constructs (such as injected tags and inline event handlers) so the output is clean and safe to host, even when the Markdown came from an untrusted source. ### Can I see a live preview? Yes. The page renders your Markdown as you type, showing the formatted result next to the source so you can check headings, links, code, and tables before you copy or publish. ### How do I host the HTML page? Click Publish and the generated HTML goes live at its own HTTPS link in seconds, an easy way to share a converted document or a quick page with no build step or server setup. --- Source: https://droply.host/tools/pdf-viewer # PDF Viewer & Reader Open any PDF and read it page by page right in your browser. Drop in a file and it renders instantly, with no software to install and no account to create. Every page is drawn locally on your own device, so the document never leaves your machine and stays completely private. When you want to share it, one click hosts the PDF at its own live link. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Open your PDF.** Drag and drop a .pdf file onto the page, or click to choose one from your device. 2. **Read it page by page.** The PDF renders instantly in your browser; scroll or page through the document, all rendered locally on your device. 3. **Publish to a live link.** Click Publish to host the PDF at its own HTTPS link and share it with anyone, in any browser. ## Frequently asked questions ### Is this PDF viewer free? Yes, completely free, with no sign-up, no watermark, and no limit on how many PDFs you can open. ### Is my PDF uploaded anywhere? No. The PDF is rendered locally in your browser and is never uploaded; it stays on your device, so even confidential documents remain private. The only time it leaves your machine is if you choose to host it with Publish. ### Is there a file size limit, and what about large PDFs? There is no fixed limit. Because the rendering runs locally, the practical ceiling is your device’s memory. Most PDFs open instantly, and very large or image-heavy files still work, they just take a moment longer per page and use more memory. ### Do scripts inside a PDF run in this viewer? No. The viewer draws each page to a canvas and does not execute any JavaScript or other active content embedded in the PDF, so opening a document here cannot run code on your machine. You see the pages exactly as designed, without the risk. ### Can I read a password-protected PDF? If a PDF is encrypted, you will be prompted for its password before the pages render; the password is used only in your browser to unlock the file locally and is never sent anywhere. Documents with no password open straight away. ### How do I host or share the PDF? Click Publish and the original PDF goes live at its own HTTPS link in seconds, ready to read in any browser. It is a quick way to send a report, invoice, or brochure without an email attachment, with no server or build step. --- Source: https://droply.host/tools/meta-tag-generator # Meta Tag Generator Fill in what your page is about and get the full block of head tags for it: title, description, canonical, Open Graph and Twitter card, with a live preview of how the result looks in a search result and in a shared link. It all runs in your browser, and you can publish a starter page carrying the tags in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Describe the page.** Enter the title, description, canonical URL and social image for the page you are writing tags for. 2. **Check the previews.** Watch the search result and social card previews update as you type, with character counters for the two fields that get truncated. 3. **Copy or publish.** Copy the block of tags into your page head, or publish a starter page carrying them to a live link. ## Frequently asked questions ### Is the meta tag generator free? Yes, completely free, with no sign-up and no limit on how many pages you generate tags for. ### Is anything I type uploaded? No. The tags are built entirely in your browser, so the title, description and URLs you type never reach our servers. ### How long should my title and description be? Around 60 characters for the title and 155 for the description. The counters update as you type and turn amber when a field is long enough to be truncated in a search result. ### Do I need both Open Graph and Twitter card tags? Not always. X falls back to Open Graph when the Twitter tags are missing, so the one worth adding on its own is twitter:card, which decides whether you get a small thumbnail or a large image. ### Why is my image not showing when I share the link? Usually the image URL is relative rather than absolute, the image is smaller than 1200 by 630, or the network has cached an older version of the page. Use a full https:// URL and re-check with the Open Graph checker. ### Can I publish a page with these tags? Yes. Publish puts a minimal HTML page carrying the generated tags on a live HTTPS link, which is a quick way to test how a link preview will look before the real page exists. --- Source: https://droply.host/tools/open-graph-checker # Open Graph & Meta Tag Checker Enter the address of a page and see the meta tags a crawler actually gets back: the title, the description, the canonical, the Open Graph set and the Twitter card, with a preview of the link card they produce and a list of what is missing. The page is fetched by us rather than by your browser, because a browser is not allowed to read another site. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Enter a URL.** Paste the full public address of the page you want to check, including https://. 2. **Read the tags.** See the title, description, canonical, Open Graph and Twitter card tags the page actually returns, with a preview of the card they produce. 3. **Fix what is missing.** Take the list of missing tags to the meta tag generator, paste the result into your page head, and check it again. ## Frequently asked questions ### Is the Open Graph checker free? Yes, free and with no sign-up. Requests are rate limited per visitor so the fetcher stays available for everyone. ### Does this upload anything of mine? No. You give it a public URL and our server fetches that URL. Nothing of yours is uploaded, and the page we fetch is read for a fixed list of tag names and then discarded. ### Why does it say no tags were found on a page that has them? Almost always because the tags are added by JavaScript after load. Crawlers read the HTML the server sent, which is what this reads too, so tags written at runtime are invisible to both. ### Can it check a page behind a login or on my laptop? No. It fetches as an anonymous visitor on the public internet, so a page behind a password, on a private network or on localhost cannot be reached. ### I fixed a tag but the preview on a social network has not changed. Networks cache what they fetched. This checker reads your page live, so if it shows the new value the page is correct; use the network's own re-fetch tool to clear its copy. ### What do I do with what it finds? Use the meta tag generator to build the block of tags you are missing, paste it into your page head, and re-check. --- Source: https://droply.host/tools/favicon-generator # Favicon Generator Drop in a square image and get the whole set of icon sizes a browser, a phone home screen and an app manifest ask for, as PNG files you can download individually or as one ZIP, along with the exact link tags to paste into your page. The resizing is done by your own browser, so the image is never uploaded. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Drop in a square image.** Choose or drag a PNG, JPEG, WebP or SVG. A square source of 512 pixels or more gives the cleanest result. 2. **Review every size.** Each generated size is previewed at its real dimensions, so you can see whether the 16 pixel version is still readable before you use it. 3. **Download and paste the tags.** Download the icons individually or as one ZIP, then copy the generated link tags into your page head. ## Frequently asked questions ### Is the favicon generator free? Yes, free with no sign-up, and there is no limit on how many icon sets you generate. ### Is my image uploaded? No. The resizing happens entirely in your browser using a canvas, so the image never leaves your device. ### What sizes do I get? The ones browsers and phones actually request: 16, 32 and 48 for tabs and bookmarks, 180 for the Apple touch icon, and 192 and 512 for a web app manifest. ### Do I get a .ico file? No, PNG only. Every browser in use reads a PNG favicon through a tag; an .ico is only needed as the no-tag fallback at the site root. ### What image should I start with? A square PNG of at least 512 pixels. Check how it looks at 16 pixels before shipping it: fine detail and wordmarks disappear at tab size. ### The old icon is still showing after I updated it. Browsers cache favicons aggressively and a normal refresh often will not clear one. Open the icon file directly to confirm the new version is being served, then give it time. --- Source: https://droply.host/tools/robots-txt-generator # Robots.txt Generator Build a valid robots.txt without looking up the syntax: pick how open the site should be, add the paths crawlers should leave alone, name your sitemap, and copy or download the result. It is generated in your browser, and one click publishes it to a live link so you can see exactly what a crawler will read. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Pick how open the site is.** Start from allow everything, block everything, or allow with exceptions, and the base rules are written for you. 2. **Add your rules.** List the paths crawlers should leave alone, add a group for a specific bot if you need one, and name your sitemap. 3. **Copy, download or publish.** Copy the file, download it as robots.txt, or publish it to a live link to see exactly what a crawler will read. ## Frequently asked questions ### Is the robots.txt generator free? Yes, free with no sign-up, and the file is generated in your browser rather than on a server. ### Where does the file have to go? At the root of the host, as /robots.txt. It does not work from a subfolder, and every subdomain needs its own copy. ### Does Disallow hide a page from search results? No. It stops a crawler fetching the page, but a disallowed URL can still be listed with no description if other pages link to it. Use a noindex meta tag on a page that is allowed to be crawled. ### Can I block one crawler and allow the rest? Yes, by adding a group that names it. Remember that a crawler obeys only the most specific group that matches it, so any rule it still needs has to be repeated in that group. ### Do I need a Sitemap line? It is optional and worth adding. It must be an absolute URL, and it applies to the whole file rather than to one user-agent group. ### How do I test the result? Click Publish to put the generated file on a live HTTPS link and open it, so you see exactly the bytes a crawler would read before you deploy it to your own host. --- Source: https://droply.host/tools/sitemap-generator # XML Sitemap Generator Paste your list of page addresses, one per line, and get a valid sitemap.xml back. You can add a last-modified date to every entry, and the result is checked as you type so an address that is not a full URL is flagged rather than written into the file. Download it, or publish it to a live link in one click. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste your URLs.** One full address per line. Anything that is not a valid absolute URL is flagged instead of being written into the file. 2. **Choose whether to date them.** Add a last-modified date to every entry if you know it is accurate, or leave it off rather than stamping today onto everything. 3. **Download or publish.** Download the sitemap.xml, or publish it to a live link, then reference it from your robots.txt. ## Frequently asked questions ### Is the sitemap generator free? Yes, free with no sign-up. The XML is built in your browser, so the URLs you paste are not sent anywhere. ### Does it crawl my site to find the pages? No. It builds a sitemap from the list you paste. That is deliberate: you decide which pages belong in the file, which is the part a crawler cannot get right for you. ### Should I include every page? Only canonical pages that return 200 and are meant to be indexed. Redirects, noindex pages and duplicates make the file less trustworthy rather than more complete. ### Why are there no priority or changefreq fields? Because Google ignores both, and so do most other engines. Emitting them adds bytes and invites tuning that has no effect. ### How many URLs can one file hold? Up to 50,000 URLs or 50 MB uncompressed. Beyond that, split the list into several files and add a sitemap index pointing at them. ### How do search engines find it? Add a Sitemap: line with the absolute URL to your robots.txt, and submit it in your search console if you use one. The robots.txt line is the one that works everywhere. --- Source: https://droply.host/tools/redirect-generator # Redirect Rule Generator Paste the old address and the new one, a pair per line, and get the same set of redirects written three ways: as a Netlify-style _redirects file, as Apache .htaccess rules, and as Nginx location directives. Everything is generated in your browser, and the status code for each rule is yours to choose. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Paste your pairs.** One redirect per line: the old path, a space, the new path, and optionally a status code. 2. **Pick the default status.** Choose 301 for a permanent move or 302 for a temporary one. Any line that names its own code keeps it. 3. **Copy the format you need.** Switch between _redirects, .htaccess and Nginx output and copy or download the one your host reads. ## Frequently asked questions ### Is the redirect generator free? Yes, free with no sign-up. The rules are generated in your browser and nothing you paste is sent anywhere. ### Should I use 301 or 302? Use 301 when the move is permanent, because it transfers ranking signals. Use 302 when you intend to put the original back. A 301 is cached hard by browsers, so it is difficult to undo. ### What format should each line be in? One pair per line: the old path, a space, the new path, and optionally the status code. Both paths can be root-relative, and the destination can be an absolute URL on another host. ### Does the order of the rules matter? Yes. All three formats match in order, so a general pattern placed above a specific one will swallow it. Put your most specific rules first. ### Can I redirect from a host I no longer own? No. A redirect is served by whatever answers the old address, so it has to be configured on that host. If you have already left it, those URLs cannot be rescued from here. ### How do I check a rule actually works? Request the old URL and read the status and the location header it returns, rather than clicking a link. A rule that lands somewhere via three hops looks identical in a browser to one that lands in a single hop. --- Source: https://droply.host/tools/webpage-to-pdf # Save a Webpage as a PDF There is no converter on this page, and that is deliberate: your browser already does this better than a server can, because it has your fonts, your session and the page exactly as you are looking at it. What follows is how to get a good PDF out of the print dialog, what tends to break, and how to put the result on a link once you have it. This tool runs entirely in the browser. Nothing is uploaded, and no account is needed. ## How to use it 1. **Open the print dialog.** Press Ctrl and P, or Cmd and P on a Mac, on the page you want to keep. 2. **Choose Save as PDF and check the settings.** Set the destination to Save as PDF, turn on Background graphics, and adjust margins or scale if the layout is being cut. 3. **Share it as a link.** Publish the saved PDF to get an HTTPS link that opens in the browser, with no attachment and no download. ## Frequently asked questions ### Why is there no converter on this page? Because your own browser does it better. It has your session, your fonts and the page as you are actually seeing it, where a server fetches an anonymous version with the cookie banner still in the way. ### How do I save a page as a PDF? Press Ctrl and P (or Cmd and P), then choose Save as PDF as the destination instead of a printer. ### My PDF came out with no colours or backgrounds. Turn on Background graphics under More settings in the print dialog. It is off by default, which is why coloured panels and dark sections vanish. ### The right-hand side of the page is cut off. Reduce the scale to 80 or 90 percent, or set margins to None. Switching to landscape helps a wide table but makes ordinary text harder to read. ### Will videos, maps and charts work? No. Anything interactive flattens or disappears: video becomes a still or a blank box, and a canvas chart can come out empty. Expand what you need first and screenshot the rest. ### How do I share the PDF once I have it? Drop it in here and it gets its own HTTPS link that opens in a browser rather than downloading, and it can carry a password or an expiry date. # Guides --- Source: https://droply.host/deploy # Publish a built framework project to Droply Droply publishes finished static files and never runs your build, so the only thing worth knowing per framework is which command produces the finished site and which folder to upload. Frameworks that render on a server need a static export first, and one of them has no supported export at all. | Framework | Build command | Folder to upload | Static by default | |---|---|---|---| | [Angular](https://droply.host/deploy/angular) | `ng build` | `dist//browser` | Yes | | [Astro](https://droply.host/deploy/astro) | `npm run build` | `dist` | Yes | | [Create React App](https://droply.host/deploy/create-react-app) | `npm run build` | `build` | Yes | | [Docusaurus](https://droply.host/deploy/docusaurus) | `npm run build` | `build` | Yes | | [Eleventy](https://droply.host/deploy/eleventy) | `npx @11ty/eleventy` | `_site` | Yes | | [Gatsby](https://droply.host/deploy/gatsby) | `npm run build` | `public` | Yes | | [Hexo](https://droply.host/deploy/hexo) | `npx hexo generate` | `public` | Yes | | [Hugo](https://droply.host/deploy/hugo) | `hugo` | `public` | Yes | | [Jekyll](https://droply.host/deploy/jekyll) | `bundle exec jekyll build` | `_site` | Yes | | [MkDocs](https://droply.host/deploy/mkdocs) | `mkdocs build` | `site` | Yes | | [Quarto](https://droply.host/deploy/quarto) | `quarto render` | `_site` | Yes | | [Slidev](https://droply.host/deploy/slidev) | `npm run build` | `dist` | Yes | | [Storybook](https://droply.host/deploy/storybook) | `npm run build-storybook` | `storybook-static` | Yes | | [Vite](https://droply.host/deploy/vite) | `npm run build` | `dist` | Yes | | [VitePress](https://droply.host/deploy/vitepress) | `npm run docs:build` | `.vitepress/dist` | Yes | | [VuePress](https://droply.host/deploy/vuepress) | `npm run docs:build` | `.vuepress/dist` | Yes | | [Zola](https://droply.host/deploy/zola) | `zola build` | `public` | Yes | | [Next.js](https://droply.host/deploy/nextjs) | `npm run build` | `out` | No | | [Nextra](https://droply.host/deploy/nextra) | `npm run build` | `out` | No | | [Nuxt](https://droply.host/deploy/nuxt) | `npx nuxi generate` | `.output/public` | No | | [Remix](https://droply.host/deploy/remix) | No static export | Needs a host that runs Node | No | | [SvelteKit](https://droply.host/deploy/sveltekit) | `npm run build` | `build` | No | | [TanStack Start](https://droply.host/deploy/tanstack-start) | No static export | Needs a host that runs Node | No | --- Source: https://droply.host/deploy/angular # How to publish an Angular site Angular builds to a static bundle. The one thing to get right is which folder inside dist to upload. - Build command: `ng build` - Folder to upload: `dist//browser` - Renders on a server by default: no ## Steps 1. **Build the project.** Run ng build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to dist//browser. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Angular - Upload the `browser` folder inside `dist/`, not `dist` itself. Angular 17 and later nest the browser build one level deeper than older versions did. - If you have enabled SSR or prerendering with `@angular/ssr`, the build also emits a server bundle. Only the browser folder is publishable here. ## Frequently asked questions ### Does Droply build my Angular project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The dist//browser folder that ng build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/astro # How to publish an Astro site Astro is static by default, so the build output is ready to publish with no adapter and no server. - Build command: `npm run build` - Folder to upload: `dist` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to dist. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Astro - This applies to the default static output. If you have added an SSR adapter (node, vercel, netlify), the build produces a server instead and there is nothing static to upload. ## Frequently asked questions ### Does Droply build my Astro project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The dist folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/create-react-app # How to publish a Create React App site Create React App builds to a static folder that any static host can serve, Droply included. - Build command: `npm run build` - Folder to upload: `build` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to build. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Create React App - Set `"homepage": "."` in package.json before building if your assets 404 after publishing. CRA otherwise writes absolute paths that assume the site is at the domain root. - A single-page app serves its own routes in the browser, so a deep link opened directly falls back to the index page. ## Frequently asked questions ### Does Droply build my Create React App project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The build folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/docusaurus # How to publish a Docusaurus site Docusaurus generates a complete static documentation site, ready to publish as-is. - Build command: `npm run build` - Folder to upload: `build` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to build. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Docusaurus - Set `url` and `baseUrl` in docusaurus.config.js to match where the site will live before you build, or internal links and the sitemap point at the wrong place. ## Frequently asked questions ### Does Droply build my Docusaurus project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The build folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/eleventy # How to publish an Eleventy site Eleventy writes plain HTML and copies your assets next to it. There is no runtime and no hydration, so the build output is the whole site. - Build command: `npx @11ty/eleventy` - Folder to upload: `_site` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npx @11ty/eleventy in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to _site. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Eleventy - The output folder is `_site` by default and is set by `dir.output` in your Eleventy config. Check the config before you go looking for a folder that is not there. - Leave `pathPrefix` at `/` for a Droply subdomain. It exists for sites served from a subfolder, and setting it rewrites your links to a path that does not exist here. - Eleventy does not copy files it was not told about. If your CSS or images are missing after publishing, the passthrough copy for that folder is missing from the config, not from the upload. ## Frequently asked questions ### Does Droply build my Eleventy project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The _site folder that npx @11ty/eleventy creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/gatsby # How to publish a Gatsby site Gatsby produces a finished static site. The folder is called public, which catches people out because most other tools call it dist. - Build command: `npm run build` - Folder to upload: `public` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to public. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Gatsby - The folder to upload is `public`, not `dist`, and not the `static` folder (that one holds your source assets before the build). ## Frequently asked questions ### Does Droply build my Gatsby project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The public folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/hexo # How to publish a Hexo site Hexo generates a finished blog into a folder. The generate step is the one that matters here; the deploy step it ships is for other targets. - Build command: `npx hexo generate` - Folder to upload: `public` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npx hexo generate in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to public. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Hexo - Use `hexo generate`, not `hexo deploy`. The deploy command pushes to a configured target such as a Git remote; here you want the folder it generated. - The output folder is `public`, and `public_dir` in _config.yml can change it. - Set `url` in _config.yml to the address the site will actually live at, and leave `root` as `/`. A `root` left pointing at a subfolder breaks every asset path on a subdomain. ## Frequently asked questions ### Does Droply build my Hexo project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The public folder that npx hexo generate creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/hugo # How to publish a Hugo site Hugo builds a whole site in one command with no Node toolchain involved. The output is finished HTML, which is exactly what gets served here. - Build command: `hugo` - Folder to upload: `public` - Renders on a server by default: no ## Steps 1. **Build the project.** Run hugo in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to public. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Hugo - The build command is just `hugo`. `hugo server` is the local preview and writes nothing to disk, which is why people go looking for a `public` folder that was never created. - Set `baseURL` in your config to the address the site will actually live at. Hugo writes it into canonical tags, feeds and sitemaps, so a leftover localhost value publishes fine and then points every crawler at your laptop. - Content dated in the future, or marked `draft: true`, is left out of a normal build. If a page is missing after publishing, check that before you check the upload. - `hugo --minify` is worth running for a public site. It changes nothing about how you publish it. ## Frequently asked questions ### Does Droply build my Hugo project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The public folder that hugo creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/jekyll # How to publish a Jekyll site Jekyll builds a finished site into _site. Publishing it somewhere other than GitHub Pages is mostly a matter of running that build yourself first. - Build command: `bundle exec jekyll build` - Folder to upload: `_site` - Renders on a server by default: no ## Steps 1. **Build the project.** Run bundle exec jekyll build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to _site. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Jekyll - Build with `JEKYLL_ENV=production` in front of the command. The default environment is `development`, and themes commonly hide analytics, comments and SEO tags outside production, so a site built without it can be missing exactly the tags you wanted. - Set `url` in _config.yml to where the site will live and leave `baseurl` empty. `baseurl` is for a site served from a subfolder, which a subdomain is not. - Run it through Bundler (`bundle exec`) rather than a bare `jekyll`, so the build uses the gem versions pinned in your Gemfile.lock instead of whatever is installed globally. - GitHub Pages allows a restricted plugin set. A site that builds locally with extra plugins is fine here, because you upload the result rather than ask anyone to rebuild it. ## Frequently asked questions ### Does Droply build my Jekyll project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The _site folder that bundle exec jekyll build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/mkdocs # How to publish a MkDocs site MkDocs turns a folder of Markdown into a finished documentation site. The output folder is called site, which is the detail people get wrong. - Build command: `mkdocs build` - Folder to upload: `site` - Renders on a server by default: no ## Steps 1. **Build the project.** Run mkdocs build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to site. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about MkDocs - The folder to upload is `site`, not `docs`. `docs` holds your Markdown source, and uploading that publishes your source rather than your site. - `site_dir` in mkdocs.yml changes the output folder. Read it before assuming the default. - Set `site_url` to the address the site will live at. The search index and the canonical tags in Material for MkDocs both read it. - Use `mkdocs build`, not `mkdocs gh-deploy`. The second one commits to a gh-pages branch, which is a different destination entirely. ## Frequently asked questions ### Does Droply build my MkDocs project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The site folder that mkdocs build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/quarto # How to publish a Quarto site Quarto renders notebooks and Markdown into a finished site. Your code runs while it renders, so what gets published is plain HTML. - Build command: `quarto render` - Folder to upload: `_site` - Renders on a server by default: no ## Steps 1. **Build the project.** Run quarto render in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to _site. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Quarto - A website project renders into `_site` by default. `output-dir` under `project` in _quarto.yml changes it, and a book project writes somewhere else, so read the config rather than assuming. - The code runs at render time, on your machine, not at the published address. Anything that needs a live kernel, such as a Shiny document, will not work as a static upload. - Render the whole project with `quarto render`, not a single file. Rendering one document leaves the rest of the site as it was at the last full render. ## Frequently asked questions ### Does Droply build my Quarto project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The _site folder that quarto render creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/slidev # How to publish a Slidev site Slidev builds a deck into a single-page app you can send as a link instead of a file, which is the whole reason to host one. - Build command: `npm run build` - Folder to upload: `dist` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to dist. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Slidev - Build at the root, not under a path. `slidev build --base /talks/name/` exists for subfolder hosting and the base must begin and end with a slash; on a Droply subdomain you do not need it. - Turn on the Single-page app switch in the site settings if you share a link to a specific slide. The deck routes in the browser, so a deep link is a path with no file behind it. - The speaker notes view and the presenter remote are part of the built output. A published deck is public, so treat the notes as public too. ## Frequently asked questions ### Does Droply build my Slidev project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The dist folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/storybook # How to publish a Storybook site A built Storybook is a static site, which makes this the cheapest way to give a designer or a client a component library they can click through. - Build command: `npm run build-storybook` - Folder to upload: `storybook-static` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build-storybook in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to storybook-static. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Storybook - The script is `build-storybook`, not `build`. Running the project build gives you the application, not the component explorer. - The output folder is `storybook-static`. - It is a published web page, so it is public unless you protect it. Password protection is checked at the edge and covers every file, which is usually what an internal component library wants. - A story that calls a real API still calls it from the visitor browser. A published Storybook pointed at a staging service is a public pointer to that service. ## Frequently asked questions ### Does Droply build my Storybook project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The storybook-static folder that npm run build-storybook creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/vite # How to publish a Vite site Vite builds a plain static bundle, which is exactly what Droply serves. Build it, upload the folder, done. - Build command: `npm run build` - Folder to upload: `dist` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to dist. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Vite - If your app uses client-side routing, set `base` in vite.config.js to `/` before building, or asset paths come out wrong on a subdomain. ## Frequently asked questions ### Does Droply build my Vite project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The dist folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/vitepress # How to publish a VitePress site VitePress builds a static documentation site into a folder inside .vitepress. - Build command: `npm run docs:build` - Folder to upload: `.vitepress/dist` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run docs:build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to .vitepress/dist. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about VitePress - The output is nested at `docs/.vitepress/dist` in the default layout. Upload that folder, not the `docs` folder that contains your Markdown source. ## Frequently asked questions ### Does Droply build my VitePress project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The .vitepress/dist folder that npm run docs:build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/vuepress # How to publish a VuePress site VuePress builds a static documentation site into a folder inside .vuepress. - Build command: `npm run docs:build` - Folder to upload: `.vuepress/dist` - Renders on a server by default: no ## Steps 1. **Build the project.** Run npm run docs:build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to .vuepress/dist. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about VuePress - The output is nested at `docs/.vuepress/dist` in the default layout. Upload that folder, not your Markdown source. ## Frequently asked questions ### Does Droply build my VuePress project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The .vuepress/dist folder that npm run docs:build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/zola # How to publish a Zola site Zola is a single binary that builds a site into public. There is no dependency install, no lockfile and nothing to keep current. - Build command: `zola build` - Folder to upload: `public` - Renders on a server by default: no ## Steps 1. **Build the project.** Run zola build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to public. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Zola - The build deletes and rewrites `public` every time, so never keep anything in there that the build does not produce. - Set `base_url` in config.toml to the real address. `zola build --base-url ` overrides it for a one-off build, which is the honest way to publish a preview to a different subdomain. - Zola fails the build on a broken internal link when link checking is on. That is worth leaving on: a link that fails locally is a 404 on the published site. - `--output-dir` moves the folder if you need it somewhere else. Most projects never touch it. ## Frequently asked questions ### Does Droply build my Zola project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The public folder that zola build creates, not the project folder. Upload it directly or ZIP it first; both work. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/nextjs # How to publish a Next.js site as a static export Next.js renders on a server by default, so it needs one config change before it can be published as a finished site. - Build command: `npm run build` - Folder to upload: `out` - Renders on a server by default: yes, this is the static export route ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to out. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Next.js - Add `output: "export"` to next.config.js, then build. The static site appears in `out`, not `.next`. - Anything that runs on the server does not survive the export: API routes, server actions, middleware, on-demand revalidation and dynamic image optimisation. - If your app depends on those, it needs a host that runs Node. That is a real answer, not a limitation we can configure around. ## Frequently asked questions ### Does Droply build my Next.js project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The out folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### Can I host a server-rendered Next.js app here? No. Droply serves static files and never runs server code, so anything that renders per request needs a host that runs Node. The static export route above is the way to publish a Next.js project here, and only if the project does not depend on server behaviour. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/nextra # How to publish a Nextra site as a static export Nextra is a Next.js site, so it renders on a server until you switch it to a static export. Two config keys do that, and its own guide names both. - Build command: `npm run build` - Folder to upload: `out` - Renders on a server by default: yes, this is the static export route ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to out. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Nextra - Add `output: "export"` AND `images: { unoptimized: true }` to next.config.mjs. the Nextra static-export guide lists both as required, and the second one is the one people miss: without it the build fails on the image optimizer rather than on anything you wrote. - The static site lands in `out`, not `.next`. `distDir` can move it. - If your site uses Pagefind search, its postbuild script has to write into the exported folder. the Nextra guide gives the exact command; a search box that returns nothing on a published site is usually this. ## Frequently asked questions ### Does Droply build my Nextra project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The out folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### Can I host a server-rendered Nextra app here? No. Droply serves static files and never runs server code, so anything that renders per request needs a host that runs Node. The static export route above is the way to publish a Nextra project here, and only if the project does not depend on server behaviour. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/nuxt # How to publish a Nuxt site as a static export Nuxt renders on a server by default, but it ships a static generator that produces a publishable site. - Build command: `npx nuxi generate` - Folder to upload: `.output/public` - Renders on a server by default: yes, this is the static export route ## Steps 1. **Build the project.** Run npx nuxi generate in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to .output/public. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about Nuxt - Use `npx nuxi generate`, not the usual build. The static site lands in `.output/public`. - Server routes and anything under `server/` do not come across. Data fetched at build time does. ## Frequently asked questions ### Does Droply build my Nuxt project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The .output/public folder that npx nuxi generate creates, not the project folder. Upload it directly or ZIP it first; both work. ### Can I host a server-rendered Nuxt app here? No. Droply serves static files and never runs server code, so anything that renders per request needs a host that runs Node. The static export route above is the way to publish a Nuxt project here, and only if the project does not depend on server behaviour. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/remix # How to publish a Remix site as a static export Remix is built around server rendering, and there is no supported way to export it as a finished static site. - Build command: none that produces a static site - Folder to upload: nothing publishable without changing the project first - It builds its pages on a live server. To publish it here it has to be exported as a finished site first; if your tool has no option for that, this project needs a host that runs the server for you. ## Steps 1. **Export it as a static site.** It builds its pages on a live server. To publish it here it has to be exported as a finished site first; if your tool has no option for that, this project needs a host that runs the server for you. 2. **Check for an index.html.** Open the folder you got. If there is no index.html in it, the export produced a server bundle and there is nothing to publish yet. 3. **Upload the folder.** Drag it into Droply and the site is live on an HTTPS droply.id subdomain in seconds. ## Worth knowing about Remix - This is the honest answer rather than a workaround: a Remix app needs a host that runs the server for you. - If the project is mostly static content, moving it to a static framework is a smaller job than fighting the export. ## Frequently asked questions ### Does Droply build my Remix project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Can I host a server-rendered Remix app here? No. Droply serves static files and never runs server code, so anything that renders per request needs a host that runs Node. The static export route above is the way to publish a Remix project here, and only if the project does not depend on server behaviour. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/sveltekit # How to publish a SvelteKit site as a static export SvelteKit renders on a server by default. Switching to the static adapter makes it publishable. - Build command: `npm run build` - Folder to upload: `build` - Renders on a server by default: yes, this is the static export route ## Steps 1. **Build the project.** Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build. 2. **Find the output folder.** The build writes a finished site to build. That folder, not the project folder, is what gets uploaded. 3. **Drag it in.** Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL. ## Worth knowing about SvelteKit - Install `@sveltejs/adapter-static`, switch to it in svelte.config.js, then build. The site lands in `build`. - Every route has to be prerenderable. A route that reads request data at runtime will fail the build with a clear message naming the route. ## Frequently asked questions ### Does Droply build my SvelteKit project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Which folder do I upload? The build folder that npm run build creates, not the project folder. Upload it directly or ZIP it first; both work. ### Can I host a server-rendered SvelteKit app here? No. Droply serves static files and never runs server code, so anything that renders per request needs a host that runs Node. The static export route above is the way to publish a SvelteKit project here, and only if the project does not depend on server behaviour. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/deploy/tanstack-start # How to publish a TanStack Start site as a static export TanStack Start builds a server bundle rather than a finished site, so it needs to be exported as static first, if your setup allows it at all. - Build command: none that produces a static site - Folder to upload: nothing publishable without changing the project first - It builds its pages on a live server each time someone visits, and Droply publishes finished pages, so there is nothing here for us to put online yet. In the tool you built it with, look for an option like "static site", "static export" or "SPA" and export it that way, then upload the folder you get. ## Steps 1. **Export it as a static site.** It builds its pages on a live server each time someone visits, and Droply publishes finished pages, so there is nothing here for us to put online yet. In the tool you built it with, look for an option like "static site", "static export" or "SPA" and export it that way, then upload the folder you get. 2. **Check for an index.html.** Open the folder you got. If there is no index.html in it, the export produced a server bundle and there is nothing to publish yet. 3. **Upload the folder.** Drag it into Droply and the site is live on an HTTPS droply.id subdomain in seconds. ## Worth knowing about TanStack Start - A TanStack Start build produces no index.html at all, which is why uploading it fails with nothing found rather than with a partial site. - In the tool you built it with, look for a "static site", "static export" or "SPA" option and export it that way. - This is the exact case that made us detect frameworks by name: the generic advice would have sent you round the same loop twice. ## Frequently asked questions ### Does Droply build my TanStack Start project for me? No, and it never will. Droply publishes finished static files. Running your build would mean running your dependencies on our servers, which is a different and much riskier product. Build locally or in your existing CI, then upload the result. ### Can I host a server-rendered TanStack Start app here? No. Droply serves static files and never runs server code, so anything that renders per request needs a host that runs Node. The static export route above is the way to publish a TanStack Start project here, and only if the project does not depend on server behaviour. ### What happens when I update the site? Build again and upload again. The new version replaces the old one at the same URL, so a link you have already shared keeps working. The Pro, Business and Enterprise plans keep a version history you can roll back to in one click. ### Can I use my own domain? Yes, on the Pro, Business and Enterprise plans. Point your domain at Droply, and the certificate is issued and renewed automatically. --- Source: https://droply.host/guides/connect-domain # Connect a custom domain Step-by-step DNS instructions for each registrar. The record to create is the same everywhere; only the screens differ. - [Cloudflare](https://droply.host/guides/connect-domain/cloudflare) - [GoDaddy](https://droply.host/guides/connect-domain/godaddy) - [Namecheap](https://droply.host/guides/connect-domain/namecheap) - [Squarespace (Google Domains)](https://droply.host/guides/connect-domain/squarespace) - [Hostinger](https://droply.host/guides/connect-domain/hostinger) - [AWS Route 53](https://droply.host/guides/connect-domain/route53) - [Porkbun](https://droply.host/guides/connect-domain/porkbun) - [IONOS](https://droply.host/guides/connect-domain/ionos) - [Another provider](https://droply.host/guides/connect-domain/other) --- Source: https://droply.host/guides/connect-domain/cloudflare # Connect a custom domain from Cloudflare Your domain is managed in the Cloudflare dashboard. The single most important thing here: the record must be set to "DNS only" (grey cloud), or your secure connection will not work. ## Steps 1. Sign in at **dash.cloudflare.com** with your Cloudflare email and password. 2. On the home screen, click the **website (domain)** you want to connect from your list of sites. 3. In the left-hand menu, click **DNS**, then click **Records**. 4. Click the **Add record** button above the list of existing records. 5. Open the **Type** dropdown and choose the type Droply shows you (usually **CNAME**, or **TXT** for a verification record). 6. In the **Name** field, enter the label exactly as Droply shows it (see "Good to know" below for the root domain). 7. In the **Target** field (called **Content** for a TXT record), paste the **Value** Droply shows you (the one shown above). 8. For a CNAME, click the **Proxy status** toggle so it reads **DNS only** and shows a grey cloud, not an orange one. This step does not apply to TXT records. 9. Leave **TTL** set to **Auto**. 10. Click **Save**. ## Notes - **Critical:** for the CNAME, **Proxy status** must be **DNS only** (grey cloud), NOT **Proxied** (orange cloud). If it stays orange, your site fails with an SSL handshake error (Error 525). Just click the cloud icon to switch it to grey. - The **Name** field takes only the label, not the full address. For a subdomain like `www.yourdomain.com`, enter just `www` and Cloudflare adds the rest. For the root domain (e.g. `yourdomain.com` with nothing in front), enter `@`. - Cloudflare automatically flattens a CNAME on the root (`@`), so pointing your root domain at Droply works here even though plain DNS normally forbids it. - If a record with the same name already exists (an old `www` or `@`, or an A record), edit or delete it first, since duplicates conflict. - Changes are usually live within a few minutes, though it can occasionally take up to an hour to fully propagate before Droply confirms the domain. --- Source: https://droply.host/guides/connect-domain/godaddy # Connect a custom domain from GoDaddy Your domain is managed in GoDaddy. You will copy the Type, Name, and Value Droply shows you into the matching boxes on GoDaddy's DNS page. ## Steps 1. Go to **godaddy.com** and sign in, then click your account name in the top right and choose **My Products**. 2. Under **Domains**, open the **Portfolio** tab to see your domains. 3. Find your domain, click the three dots **...** next to it, and choose **Edit DNS**. 4. On the DNS page, scroll to the **Records** section and click **Add New Record**. 5. Open the **Type** menu and pick the type Droply shows you (for example **CNAME** or **TXT**). 6. In the **Name** box, enter the label Droply gave you (for example `blog`), and in the **Value** box paste the target Droply shows you (the one above). 7. Leave **TTL** on its default of **1 Hour** unless told otherwise. 8. Click **Save** (if you added more than one record, click **Save All Records**). ## Notes - **Name field = label only.** Type just the prefix without your domain, so `blog`, not `blog.yourdomain.com`. GoDaddy adds the rest. - For the root domain, enter `@` in the **Name** box. `@` means your domain by itself, with no prefix. - GoDaddy does not allow a CNAME on the root `@` domain. If Droply asks you to point the bare domain, use the `www` record (or the alternate record Droply provides) instead. - Add each record Droply shows as its own separate entry, and do not delete your existing records unless Droply tells you to. - Changes usually go live within an hour but can take up to **48 hours** to fully update, so wait a bit before checking. --- Source: https://droply.host/guides/connect-domain/namecheap # Connect a custom domain from Namecheap Your domain is managed in Namecheap. The record goes in the Advanced DNS tab of your domain. ## Steps 1. Go to the Namecheap site and **Sign In** to your account. 2. In the left sidebar, click **Domain List**. 3. Find your domain and click the **Manage** button next to it. 4. At the top of the page, click the **Advanced DNS** tab. 5. In the **Host Records** section, click **Add New Record**. 6. Open the **Type** dropdown and choose the type Droply shows you (for example **CNAME Record** or **TXT Record**). 7. In the **Host** field, enter the label Droply gave you (just the label, like `www`, or `@` for the root domain). 8. In the **Value** field, paste the target Droply shows you (the one above). 9. Leave **TTL** on **Automatic**. 10. Click the green checkmark to confirm the row, then click **Save All Changes**. ## Notes - **Host field = label only.** Enter just the part before your domain. For a subdomain type only `www`; for the root domain use `@`. - Namecheap does not allow a real **CNAME Record** on the root domain (`@`), because it conflicts with email records. If Droply asks for the root, use the subdomain (like `www`) it provides. - Do not add a trailing dot to the **Value**; Namecheap formats it for you. - Remove any old conflicting **CNAME**, **A**, or **URL Redirect** record on the same **Host** first, or the new one will not work. - This only works if your domain uses Namecheap's nameservers. On the **Domain** tab, check that **Nameservers** is set to **Namecheap BasicDNS**; if it points elsewhere, the record belongs at that other provider. - Changes usually take about **30 minutes**, but full propagation can take a few hours. --- Source: https://droply.host/guides/connect-domain/squarespace # Connect a custom domain from Squarespace (Google Domains) Google Domains moved to Squarespace, so domains bought there are managed in Squarespace now. The record goes in your domain's DNS settings. ## Steps 1. Go to **account.squarespace.com/domains** and sign in (use your old Google Domains login if your domains were moved over). 2. On the **Domains** dashboard, click the name of the domain you want to connect. 3. In the left-hand menu, click **DNS**, then **DNS Settings**. 4. Scroll down to the **Custom Records** section and click **Add Record**. 5. If asked, re-enter your password (or finish two-factor) and click **Continue** to confirm it is you. 6. Open the **Type** dropdown and choose the type Droply shows you (for example **CNAME** or **TXT**). 7. In the **Host** field enter the label from Droply, and in the **Data** field paste the target Droply shows you (the one above). 8. Click **Save**, then repeat **Add Record** for any second record Droply shows. ## Notes - The **Host** field takes only the label. For `www.yourdomain.com`, type just `www`; Squarespace adds your domain automatically. - Squarespace does not allow `@` in the **Host** field for a CNAME, so you cannot point your bare root domain with a CNAME. Use the subdomain Droply provides (commonly `www`). - Each custom record uses a default **TTL** of 4 hours; leave it as-is unless told otherwise. - If Droply shows two records, add each one separately and enter each Host/Data pair exactly. - DNS changes are not instant: typically a few minutes to a few hours, occasionally up to **24-48 hours**. --- Source: https://droply.host/guides/connect-domain/hostinger # Connect a custom domain from Hostinger Your domain is managed in the Hostinger hPanel. The record goes in the DNS records area for your domain. ## Steps 1. Go to **hpanel.hostinger.com** and log in to your Hostinger account. 2. In the top menu, click **Domains**, then open **Domain portfolio**. 3. Click the domain you want to connect to open its management page. 4. In the left sidebar, click **DNS / Nameservers**, then select the **DNS records** tab. 5. Under **Add new record**, choose the type in the **Type** dropdown (for example **CNAME** or **TXT**). 6. In the **Name** field, enter the label Droply gave you (see "Good to know" for the root domain). 7. In the **Target** field (also shown as **Points to**), paste the target Droply shows you (the one above). 8. Leave **TTL** at its default unless told otherwise. 9. Click **Add Record** to save it, and repeat for any second record Droply shows. ## Notes - **Name field = label only.** Enter just the host part; Hostinger adds your domain. For `www.yourdomain.com` type only `www`. - For the root/main domain, type `@` in the **Name** field (that means the bare domain itself). - Hostinger does not allow a **CNAME** on the root `@` record. If Droply asks for a root CNAME, use the label it provides (often `www`) instead. - Copy the target character for character; a stray space or missing letter breaks the connection. - After saving, DNS changes can take **up to 24 hours** to propagate, though it is often much faster. - If your domain uses external nameservers (not Hostinger's), the record must be added at that other provider instead. --- Source: https://droply.host/guides/connect-domain/route53 # Connect a custom domain from AWS Route 53 Your domain is managed in Amazon Route 53. The record goes inside your domain's "hosted zone", where all of its DNS settings live. ## Steps 1. Open the Route 53 console and sign in to your AWS account (use an account that can edit DNS). 2. In the left navigation pane, choose **Hosted zones**. 3. On the **Hosted zones** page, click the name of the hosted zone for your domain. 4. Click the orange **Create record** button on the right. 5. If a step-by-step wizard opens, click **Switch to quick create** for the simple form. 6. Leave the routing policy as **Simple routing** (the default). 7. In **Record name**, type only the label Droply gave you (for example `www`), or leave it empty for the root domain. 8. Open the **Record type** dropdown and pick the type Droply shows you (**CNAME**, or **TXT**). 9. In the **Value** field, paste the target Droply shows you (the one above). 10. You can leave **TTL (seconds)** at its default; lowering it to `300` makes changes show up faster. 11. Click **Create records** at the bottom right, and repeat for any second record. ## Notes - **Record name = label only.** Route 53 adds your domain automatically, so enter just `www`, not `www.yourdomain.com`. For the root domain itself, leave the field empty. - The root domain cannot use a plain CNAME (a DNS rule). If Droply asks for a root CNAME, point a subdomain like `www` instead, or contact us about an alternative. - If you do not see a **hosted zone** for your domain, your DNS is managed elsewhere; add the record there instead. - Make sure you are editing a **Public hosted zone**, not a Private one. - Changes usually reach Route 53 within about 60 seconds, but can take longer to be visible everywhere. --- Source: https://droply.host/guides/connect-domain/porkbun # Connect a custom domain from Porkbun Your domain is managed in Porkbun. Log in, open your domain's DNS editor, add the record Droply shows you, and save. ## Steps 1. Go to **porkbun.com** and log in with your username and password. 2. In the top-right corner click **ACCOUNT**, then choose **Domain Management**. 3. Find your domain and click the **DNS** button under it to open the **Manage DNS Records** page. 4. Click the **Add Record** button. 5. Open the **Type** dropdown and pick the type Droply shows you (**CNAME** or **TXT**). 6. In the **Host** field, type the label Droply gave you (or leave it blank for the root domain). 7. In the **Answer/Value** field, paste the target Droply shows you (the one above). 8. Leave **TTL** at its default unless told otherwise. 9. Click the **Add** button to save, and repeat for any second record. ## Notes - **Host field = label only.** If Droply shows `blog.yourdomain.com`, enter just `blog`. Porkbun adds your domain. - For the root domain (your bare domain), leave the **Host** field empty. Do not type `@` or your domain name there. - Porkbun does not allow a `CNAME` on the root domain. If Droply asks you to point the bare domain, use the `www` label, or Porkbun's **ALIAS** record type for the root. - A `CNAME` host must be unique - remove any other record (like an A record) on the exact same Host first. - Paste the value with no extra spaces and no trailing dot, then double-check it before clicking **Add**. - DNS changes can take a few minutes to a few hours to take effect. --- Source: https://droply.host/guides/connect-domain/ionos # Connect a custom domain from IONOS Your domain is managed in the IONOS Control Center. The record goes in the DNS settings for your domain. ## Steps 1. Go to **my.ionos.com** and log in with your IONOS email and password. 2. In the top menu, open **Domains & SSL** to see your domains. 3. Find the domain you want to connect and click the gear icon (or **three-dots** menu) under **Actions**. 4. From that menu, choose **DNS** to open the domain's DNS records. 5. Click the **Add record** button to start a new entry. 6. Pick the type Droply shows you (for example **CNAME** or **TXT**) under **Type**. 7. In the **Hostname** field, enter only the label Droply gave you (for example `www`), or leave it as the root for the bare domain. 8. In the **Points to** field (or **Value** for a TXT record), paste the target Droply shows you (the one above). 9. Leave **TTL** at its default, then click **Save**. ## Notes - The **Hostname** field takes only the label: type just `www` (IONOS adds your domain on the end), not `www.yourdomain.com`. - For a record on the root domain, leave the **Hostname** field empty or use `@`. - IONOS does not allow a true **CNAME** on the root domain; if Droply's record is a CNAME for the bare domain and IONOS blocks it, use a subdomain like `www` instead. - Enter the **Points to** value without `http://` or `https://`. - Make sure your domain still uses the **IONOS name servers** (the default), or the record will not take effect. - Your change saves instantly, but can take up to about **1 hour** to be visible everywhere. --- Source: https://droply.host/guides/connect-domain/other # Connect a custom domain from Another provider These steps are the same almost everywhere - only the labels differ a little. Find your DNS settings, add one record, and paste in the values Droply shows you. ## Steps 1. Sign in to wherever you bought or manage your domain (your registrar or DNS host). 2. Find the DNS settings, often called **DNS**, **DNS Records**, **Manage DNS**, or **Zone file**. 3. Click **Add record** (or **Add New Record**) and choose the **Type** Droply shows you (**CNAME** or **TXT**). 4. Put the **Name** in the host/name field and paste the **Value** Droply shows you (the one above) into the value/target field. 5. Save the record and wait a few minutes. ## Notes - If the provider already fills in your domain, enter only the part before it (e.g. `blog`), not the whole thing. - Use `@` (or leave the name blank) when the record is for your root domain. - Most providers do not allow a CNAME on the root domain. If yours refuses, point a subdomain like `www` instead, or contact us and we will help. - DNS changes can take a few minutes to a few hours to spread across the internet. --- Source: https://droply.host/docs # Documentation ## API Deploy from scripts, CI, and your own tooling over HTTPS. - [API reference](https://droply.host/docs/api): Endpoints, authentication, and copy-paste examples for deploying sites programmatically. - [OpenAPI spec](https://droply.host/api/v1/openapi.json): The machine-readable spec, for client generators and API tools. - [API tokens](https://droply.host/dashboard/api-tokens): Create and revoke the tokens every integration and script signs in with. ## Guides Getting your files into a shape Droply can publish. - [Building and editing pages with the AI builder](https://droply.host/docs/ai-builder): Describe a page and publish it, or tell the builder what to change on a live site. What it costs and what it refuses. - [Publishing a project from an AI builder](https://droply.host/docs/build-your-project): Lovable, bolt.new, v0 and Cursor give you source code. One export step turns it into a site. ## Integrations Set up the tools that deploy to Droply for you. - [Publish from Claude](https://droply.host/docs/integrations/claude): Connect Claude and let it publish pages and sites to your account, on every plan. - [Deploy from VS Code](https://droply.host/docs/integrations/vscode): Zip the current folder and publish it without leaving your editor. - [Capture a page from Chrome](https://droply.host/docs/integrations/chrome): The browser extension that snapshots the page you are on and hosts it. - [Automate with Zapier](https://droply.host/docs/integrations/zapier): Deploy from thousands of apps with no code. - [Deploy from ChatGPT](https://droply.host/docs/integrations/chatgpt): Ask the Droply GPT to build and publish a page for you. ## Connect a custom domain Point a domain you own at your site: one DNS record, step by step at your provider. - [How it works](https://droply.host/guides/connect-domain): The universal explainer: which record to add and why, at any provider. - [Cloudflare](https://droply.host/guides/connect-domain/cloudflare): Add the DNS record at Cloudflare, click by click. - [GoDaddy](https://droply.host/guides/connect-domain/godaddy): Add the DNS record at GoDaddy, click by click. - [Namecheap](https://droply.host/guides/connect-domain/namecheap): Add the DNS record at Namecheap, click by click. - [Squarespace (Google Domains)](https://droply.host/guides/connect-domain/squarespace): Add the DNS record at Squarespace (Google Domains), click by click. - [Hostinger](https://droply.host/guides/connect-domain/hostinger): Add the DNS record at Hostinger, click by click. - [AWS Route 53](https://droply.host/guides/connect-domain/route53): Add the DNS record at AWS Route 53, click by click. - [Porkbun](https://droply.host/guides/connect-domain/porkbun): Add the DNS record at Porkbun, click by click. - [IONOS](https://droply.host/guides/connect-domain/ionos): Add the DNS record at IONOS, click by click. - [Another provider](https://droply.host/guides/connect-domain/other): Generic steps that work at any provider not listed here. ## Resources More ways to get a site live faster. - [Templates](https://droply.host/templates): Ready-made sites you can deploy in one click and edit afterwards. - [Free web tools](https://droply.host/tools): Formatters, validators, and converters that run in your browser. # Blog --- Source: https://droply.host/blog # Droply blog Guides and comparisons on static hosting, file sharing and publishing. - [The Best Free Static Site Hosting in 2026](https://droply.host/blog/the-best-free-static-site-hosting-in-2026): Discover the best free static site hosting in 2026. Compare Droply, GitHub Pages, Netlify, and Vercel for simple, fast static website hosting. - [The 6 best Netlify Drop alternatives in 2026](https://droply.host/blog/best-netlify-drop-alternatives): Six Netlify Drop alternatives compared on claim windows, updates and price. Every figure comes from the provider and carries the date it was read. - [How to Host Multiple Static Sites Under One Account](https://droply.host/blog/how-to-host-multiple-static-sites-under-one-account): Learn how to host multiple static sites under one account, with a step-by-step comparison of Droply and other options for freelancers and agencies. - [How to Host a ZIP File of a Static Site](https://droply.host/blog/how-to-host-a-zip-file-of-a-static-site): Learn how to host a zip file of a static site with no server setup. Upload your zip, pick a name, and get a live link in seconds with Droply. - [How to Host a One Page PDF Brochure | Fast Comparison](https://droply.host/blog/how-to-host-a-one-page-pdf-brochure-fast-comparison): How to host a one page PDF brochure with a real link you can share. Compare Droply, Google Drive, Dropbox, and email attachments. - [Droply vs Vercel: Which Should You Use for a Static Site?](https://droply.host/blog/droply-vs-vercel-which-should-you-use-for-a-static-site): Droply vs Vercel for a static site: compare workflow, speed, and use cases so you can pick the right host for your next project or prototype. - [How to Share a Figma Prototype Export](https://droply.host/blog/how-to-share-a-figma-prototype-export): How to share a Figma prototype export as a real link instead of a screen-share, including how to publish an exported HTML build with Droply in seconds. - [How to Host Your Lovable Site for Free](https://droply.host/blog/how-to-host-your-lovable-site-for-free): Learn how to host your Lovable site for free in minutes. Export your project, deploy static files, and get a live HTTPS URL without git or builds. - [Droply vs GitHub Pages: Which Should You Use?](https://droply.host/blog/droply-vs-github-pages-which-should-you-use): A fair comparison of Droply and GitHub Pages for hosting static sites and documents. See which fits drag-and-drop publishing vs full build pipelines. - [How to Publish AI-Generated HTML from ChatGPT, Claude, or Lovable](https://droply.host/blog/how-to-publish-ai-generated-html-from-chatgpt-claude-or-lovable): A practical guide to turning HTML from ChatGPT, Claude, or Lovable into a live URL you can share in seconds, no git, no build step. - [The Fastest Way to Ship an Event Page](https://droply.host/blog/the-fastest-way-to-ship-an-event-page): How to take an event page from HTML or ZIP to a live HTTPS link in minutes using Droply, and why it beats the usual hosting routes. - [Free HTML and Static Site Hosting: What to Look For](https://droply.host/blog/free-html-and-static-site-hosting-what-to-look-for): Compare free HTML and static hosting options, learn what to look for, and find the fastest way to ship a static site or PDF online. - [The Fastest Way to Ship a Documentation Site](https://droply.host/blog/the-fastest-way-to-ship-a-documentation-site): The fastest way to ship a documentation site: pick a static generator, build locally, and deploy the output to a live HTTPS URL in minutes. - [Cloudflare Pages Alternative for Simple Static Hosting](https://droply.host/blog/cloudflare-pages-alternative-for-simple-static-hosting): Looking for a simpler Cloudflare Pages alternative? Droply hosts pre-built static sites instantly with no git, no build step, and a live URL in seconds. - [Best Ways to Deliver Client Work with Branded Microsites](https://droply.host/blog/best-ways-to-deliver-client-work-with-branded-microsites): How freelancers and agencies use branded microsites to deliver client work cleanly, win approvals faster, and look more professional doing it. - [The Fastest Way to Ship a Resume Online](https://droply.host/blog/the-fastest-way-to-ship-a-resume-online): A practical guide to publishing your resume as a live HTTPS link in under a minute using Droply, with no git, builds, or server setup. - [Netlify Alternative for Simple Static Hosting](https://droply.host/blog/netlify-alternative-for-simple-static-hosting): Looking for a simpler Netlify alternative? Droply hosts pre-built static sites instantly with no build step, no git, just a drag and drop. - [How to Host an HTML File Online Without GitHub, Netlify, or a Server](https://droply.host/blog/how-to-host-an-html-file-online-without-github-netlify-or-a-server): A practical guide to publishing an HTML file online fast. No git, no build step, no server config. Get a live HTTPS URL in seconds. - [How to Upload a PDF Online and Share It as a Link](https://droply.host/blog/how-to-upload-a-pdf-online-and-share-it-as-a-link): Learn the fastest ways to upload a PDF online and get a clean shareable link, plus when to use a dedicated host instead of email or cloud drives. - [The Fastest Way to Ship a Portfolio](https://droply.host/blog/the-fastest-way-to-ship-a-portfolio): A practical guide to going from portfolio files to a live HTTPS link in under a minute, without git, builds, or server config. - [The Fastest Way to Ship a Client Prototype](https://droply.host/blog/the-fastest-way-to-ship-a-client-prototype): A practical guide to going from static files to a live client preview link in under a minute using Droply. No git, no build step, no server config. - [The Fastest Way to Ship a Landing Page](https://droply.host/blog/the-fastest-way-to-ship-a-landing-page): A practical guide to going from HTML files to a live, HTTPS landing page in under a minute using Droply, no git, no build step, no server config. --- Source: https://droply.host/blog/the-best-free-static-site-hosting-in-2026 # The Best Free Static Site Hosting in 2026 Published Sep 10, 2026 by The Droply Team. Looking for the best free static site hosting in 2026? Let's be honest: most "free" static hosting comes with strings attached. Hidden limits, confusing build processes... In 2026, the landscape has shifted. While the usual suspects still dominate developer circles, a new approach is winning over designers, freelancers, and anyone who just wants their work online without the headache. Here's why **Droply.host** deserves a spot at the top of your list! --- ## The Problem with Traditional Free Hosting GitHub Pages, Netlify, and Vercel are powerful, no question. But they all share a fundamental assumption: **you're a developer comfortable with Git, build tools, and the command line**. What if you're not? - What if you're a designer with a finished HTML file? - What if you just generated something cool in Claude or v0? - What if you're a student submitting a project in 10 minutes? - What if you need to share a client preview *right now*? The traditional workflow (commit, push, build, deploy) adds friction where there should be none. --- ## Enter Droply: Zero Git, Zero Config, Zero Friction Droply takes a radically different approach: **Drag. Drop. Done.** Here's what that actually means in practice: ### 1. Upload Anything, Instantly Droply accepts **HTML files, ZIP folders, PDFs, images, or even raw JSX/TSX files**. A React component from ChatGPT? Drop it. A full static site built with Astro? Zip it and drop it. A single landing page? Drop the HTML file. **The result?** A secure HTTPS link in seconds. No terminal, no Git commands, no configuration files. ### 2. The Same URL, Every Time Here's a frustration many hosts ignore: every time you update, you get a new URL. Not with Droply (unless your really want). Each upload creates a **new deployment at the same link** . Share that URL once, and it always points to your latest version, or roll back to a previous version with one click (on paid plans) . ### 3. Built for the Way You Actually Work - **For AI-generated code**: Tools like Claude, v0, and Lovable spit out single `.jsx` or `.tsx` files. Droply renders them in the browser without requiring a build step . - **For client previews**: Password protection is available on paid plans . Need it to expire? Set it for 6 hours, a week, or a specific date . - **For agencies**: Custom domains and automatic SSL on Pro plans and higher . ### 4. Analytics Without the Bloat Every site gets privacy-friendly visitor analytics built in. You see how many people opened your link without sending data to Google or adding tracking scripts. --- ## The Free Plan: What You Actually Get Let's clear up the incorrect information from earlier. Here's the **real** Droply Free plan: | Feature | What You Get | | :--- | :--- | | **Sites** | **1 site** | | **Storage** | **25 MB** | | **Visits** | **10,000 visits / month** | | **Bandwidth** | **10 GB / month** | | **Subdomain** | `droply.id` subdomain | | **Link-in-bio** | Included | You can see all features and plan comparisons [HERE](https://droply.host/pricing) --- ## Who Is Droply Really For? Droply's founder puts it simply: *"If you can drop a file, it is for you."* Here's who's actually using it: - **Designers** sending portfolios, case studies, and mockups that open instantly - **Freelancers** shipping prototypes and client previews without the back-and-forth - **Students** submitting assignments, projects, and slides - **AI users** putting Claude/v0 creations online in seconds - **Marketers** sharing campaign pages and one-pagers - **Real estate agents** turning brochures and floor plans into shareable links - **Recruiters** sending job pages and hiring packs If you've ever wanted to share something without making someone download a file, this is for you. --- ## The Verdict: When to Choose Droply **Choose Droply if:** - You want to put something online **right now** - You're not a Git wizard and don't want to become one - You work with AI tools that generate code - You need to share temporary previews with expiration dates - You want built-in analytics without adding third-party scripts **Choose traditional platforms if:** - You're building a long-term open-source project - You need complex CI/CD pipelines - You're already deeply embedded in the Git ecosystem - You have high-traffic needs beyond 10 GB/month --- ## Your Next Link is One Drop Away In 2026, free static hosting doesn't have to be complicated. Droply proves that simplicity isn't a compromise, it's a feature. Whether you're sharing a PDF, deploying a React app from ChatGPT, or publishing your portfolio, you can go from file to live URL in seconds. **No Git. No build. Just a link.** Try it free at [droply.host](https://droply.host) (no credit card required). --- Source: https://droply.host/blog/best-netlify-drop-alternatives # The 6 best Netlify Drop alternatives in 2026 Published Sep 9, 2026 by The Droply Team. Netlify Drop is a good tool with one property that surprises people: a drop made without signing in creates a temporary project you have to claim within one hour, and until you claim it the project URL is protected with a temporary password. If you found this post an hour and five minutes after dropping something, that is why. The other reason people look around is that Drop is a doorway. Netlify's own documentation points you at the CLI for larger projects and at the Git integration for anything ongoing, because Drop exists to get you onto the platform rather than to be the platform. Here are six alternatives, sorted by what happens to the link after the drop rather than by price. Every figure was read from the provider's own pages on 8 September 2026. We make the first one. The rest are here on merit. ## 1. Droply **Best for:** a link that is yours from the first second, and updates that land on the same URL. There is no anonymous drop, which is the point: you sign in first, so there is no hour to beat, no claim step and no temporary password to relay to the person you are sending it to. Re-uploading publishes a new immutable version at the same address, so a link you already sent shows the current version rather than the one you were embarrassed by. It takes a single HTML file, a folder, a ZIP, a single `.jsx` or `.tsx` with no build step, a PDF, an image or an office document. Every publish is read for a committed `.env`, a `.git` directory, a private key or an API key left in a bundle, on every plan including free. What it will not do is build your project. Netlify Drop will; Droply never runs a build, so you run it locally and upload the output. If that is the feature you came for, stay where you are. **Price:** free plan, no card, nothing to claim. Paid tiers start at $5 a month, below every other paid host on this list, and add custom domains, password protection, rollback and expiring links; see [pricing](/pricing) or the row-by-row [Netlify Drop comparison](/netlify-drop-alternative). ## 2. Cloudflare Drop **Best for:** the fastest possible look at a folder, and the largest free tier once claimed. No account at all to start. Drag a folder or a ZIP and it is live, which is one step fewer than Netlify. The preview lasts one hour, and then the deployment and the throwaway account created for it both disappear, so the claim problem is the same problem in a shorter dress. Claim it and it becomes a Cloudflare Pages project on the free tier: 20,000 files per site, 500 builds a month and up to 100 custom domains per project, at no cost. Limits: 1,000 files per upload, 25 MiB per file, static assets only, public by default, and no API at launch. **Price:** free. More in the [Cloudflare Drop comparison](/cloudflare-drop-alternative). ## 3. Vercel Drop **Best for:** a framework project you want built for you, once. Vercel Drop takes a file, a folder or a `.zip`, detects the framework and builds it. For a Next.js project that is real work you are not doing. It also needs an account, so nothing here expires while you are looking for it. The limitation is that each drop creates a new project and Drop cannot redeploy into an existing one, so every update produces a new URL. Vercel's own docs say so plainly. If the link is going to anyone who will look at it twice, plan for that. Note too that the free Hobby plan is "for personal, non-commercial use" per Vercel's pricing page. **Price:** Hobby free for personal use; Pro $20 a month plus $20 a month per developer seat. [Vercel Drop comparison](/vercel-drop-alternative). ## 4. Tiiny Host **Best for:** documents and one-off files, from the product that has been doing this longest. Tiiny accepts HTML, ZIP, PHP, PDF and most image, document, PowerPoint and Excel formats, which is a wider net than any of the drop tools. Its free plan is one site with 3 MB per project (0.5 MB for a PDF), 5,000 visits and 5 GB of bandwidth a month. Worth knowing before you pick a tier: custom domains and password protection both start on Solo, $18 a month or $13 a month billed annually, and its entry tier is $9 a month against $5 here. **Price:** Tiny $9 a month ($5 billed annually), Solo $18, Pro $38, Pro Max $89, each with a 7-day money-back guarantee. [Tiiny Host comparison](/tiiny-host-alternative). ## 5. Static.app **Best for:** cheap multi-site hosting when your uploads are always ZIPs. $5 a month or $60 a year for two sites with a custom domain, rising to thirty sites for $15 a month. It is the cheapest paid tier in this list per site. Its own Claude hosting page says a loose `.html` file is not accepted and must be zipped, and that React-based artifacts need converting to self-contained HTML first. Password protection is not listed on any of its plans. [Static.app comparison](/static-app-alternative). ## 6. GitHub Pages **Best for:** anything that is already a repository, at no cost. Not a drop tool at all: publishing means a commit, a branch or folder setting and often an Actions workflow. In exchange it is free, includes a custom domain with HTTPS, and has no site count to run out of. Its usage limits forbid using Pages as a free web-hosting service to run an online business, an e-commerce site or a commercial SaaS, and a private Pages site requires GitHub Enterprise Cloud. Sites are capped at 1 GB with a soft 100 GB of bandwidth a month. **Price:** free. [GitHub Pages comparison](/github-pages-alternative). ## The question that actually decides it Not price. Ask what has to be true of the link a week from now: - **It must be yours immediately.** Rule out anything with a claim window: Netlify Drop and Cloudflare Drop both delete an unclaimed deploy after an hour. - **It must show the current version.** Rule out Vercel Drop, where each drop is a new project at a new address, unless you are going to connect a repository afterwards. - **It must not be public.** Password protection is a Pro feature on Netlify at $20 a month, a $150 a month add-on on Vercel Pro, undocumented on Cloudflare Drop, and a Solo feature on Tiiny at $18 a month. Price that in before you compare anything else. If you arrived here from Tiiny Host rather than from an expired Netlify deploy, the [best Tiiny Host alternatives](/blog/best-tiiny-host-alternatives) list scores the same hosts on document hosting and free-plan limits instead, which are the two things that usually decide that one. Every figure here was read from the provider's own documentation on 8 September 2026, and this category changes fast. Check the source before you spend anything. --- Source: https://droply.host/blog/how-to-host-multiple-static-sites-under-one-account # How to Host Multiple Static Sites Under One Account Published Sep 7, 2026 by The Droply Team. The fastest way to host multiple static sites under one account is to use a platform built for uploading, not building: drag each site's files in, give it a name, and get a live link. No server to configure, no separate accounts to manage, no build pipeline to babysit for every client project. This matters more than it sounds. If you're a freelancer with eight client landing pages, or an agency spinning up a new prototype every week, the real cost isn't hosting one site. It's managing ten of them without losing track of logins, renewals, or which project lives where. Below is a ranked look at your options, starting with the simplest. ## 1. Droply: drag, name, done Droply (droply.host) is built specifically for this. One account holds every site you upload, and each one gets its own address at `.droply.id` with no extra setup. Here's the actual flow: 1. Sign in to your Droply account. 2. Drag your HTML file, a ZIP (a compressed folder holding your whole site) of a static site, or a PDF onto the upload area. 3. Pick a name, like `client-acme` or `portfolio-draft2`. 4. Your site is live at `client-acme.droply.id` in seconds. Need to host a second site? Repeat the same three steps under the same login. There's no per-site signup, no separate dashboard to remember, and no server config to duplicate. Updating a site later is just as simple: re-upload the new file or ZIP, and the same URL updates in place, so any links you've already shared keep working. This is the important limit to know: Droply hosts static output only (pre-built HTML, CSS, JS, images, PDFs). It doesn't run builds or execute server-side code. If your project is a plain static site, a design portfolio, a client landing page, a set of exported PDFs, or a static site generator's output (Hugo, Jekyll, Eleventy, or similar, built locally first), this is exactly the job Droply does well. If you need a live database or server-side logic, you'll want a different tool for that piece. Paid plans add custom domains (so `client-acme.droply.id` can become `www.clientdomain.com`) and remove the "powered by Droply" banner, which agencies reselling sites to clients usually want. Check current plan details at [/#pricing](/pricing). ## 2. A traditional web host with subdomains or subfolders Shared hosting providers (the kind that host WordPress sites) can technically hold multiple static sites too, usually via subdomains or subfolders in a single control panel. This works, but it was built for dynamic sites with databases, so you're carrying overhead you don't need: PHP settings, MySQL databases, security patches, all for files that are just HTML and CSS. It's a reasonable choice if you're already paying for hosting and have unused space, but setting up a new subdomain usually means logging into a control panel, configuring DNS (the system that points a domain name to a server), and waiting for propagation. That's minutes to hours per site, not seconds. ## 3. A cloud storage bucket per site Services like Amazon S3 or Google Cloud Storage can serve static files if you enable "static website hosting" on each bucket. It's cheap and reliable, but each site needs its own bucket, its own permissions setup, and often a content delivery network (a system that speeds up loading by serving files from servers near the visitor) layered on top for HTTPS. Multiply that setup by ten client sites and you've built yourself a part-time job. This makes sense if you're a developer comfortable with cloud infrastructure and want fine-grained control. For most freelancers and agencies, it's more plumbing than the task calls for. ### Quick comparison | Option | Setup time per site | Non-developer friendly | Custom domain support | |---|---|---|---| | Droply | Seconds | Yes | Yes (paid plans) | | Shared web host | Minutes to hours | Somewhat | Yes | | Cloud storage bucket | 30+ minutes | No | Yes, manual setup | ## 4. Git-based deploy platforms Tools like [Netlify](/alternatives) or Vercel are excellent if your workflow involves a code repository and a build step (compiling source files into a finished site). They handle multiple sites well and are a genuinely better fit if you're already committing code to GitHub and want automatic deploys on every push. But if your "site" is just a folder your design tool exported, or a one-page HTML file a client sent you, setting up a git repository and a build pipeline is extra work with no payoff. That's the gap Droply fills: no repo, no build, just the finished files. ## Do / Don't for managing multiple sites **Do:** - Use one account and a clear naming convention (`clientname-project`) so sites stay easy to find. - Re-upload to the same name when a site updates, so shared links never break. - Keep a simple spreadsheet or note of which name maps to which client, even with a tidy naming system. **Don't:** - Create a separate account or login for every client site. It's the fastest way to lose track of what's live. - Mix draft and final versions under the same name without warning collaborators first. - Assume you need a database or server just because a site "feels" complex. Most client sites and prototypes are static. ## Which option should you actually use If every site you're hosting is a finished set of files (exported from a design tool, a static site generator, or just plain HTML), Droply is the most direct path: one account, one simple upload flow, a live link in seconds, and no per-site setup to repeat. Save git-based deploy tools for projects with an active codebase and build step, and save cloud storage buckets for cases where you specifically need that level of infrastructure control. For the freelancer or agency juggling five, ten, or twenty small static projects, the winning move is removing friction, not adding infrastructure. [Drag your file onto Droply](/) and it's live in seconds. --- Source: https://droply.host/blog/how-to-host-a-zip-file-of-a-static-site # How to Host a ZIP File of a Static Site Published Sep 1, 2026 by The Droply Team. The fastest way to host a zip file of a static site is to drag it onto Droply, name it, and get a live HTTPS link immediately. No server setup, no command line, no build step: Droply unpacks the zip and serves it at `.droply.id` in seconds. That's the short answer. But there are real questions worth answering before you upload, especially if this is your first time shipping a static site (a site made of plain HTML, CSS, and images with no server-side code running behind it). ## What counts as a "static site" I can zip and host? A static site is just a folder of pre-built files: an `index.html`, maybe a `style.css`, an `images` folder, perhaps a bit of JavaScript for animations or a contact form that posts to a third-party service. If your site was made with a static site generator (a tool like Hugo or Eleventy that turns templates into plain HTML files), an export from a design tool, or hand-written HTML, it qualifies. What doesn't qualify: anything that needs a server to run code while someone visits it, like a PHP site, a Node.js app with an API, or a WordPress install with a database. Those need actual server hosting, not static file hosting. Droply, and static hosts generally, only serve files exactly as they are; nothing runs on the server side. ## How do I zip a static site correctly? Zip the contents of your site folder, not the folder itself, so that `index.html` sits at the top level of the archive. This is the single most common mistake people make, and it's an easy one to check before you upload. Here's the difference: - **Wrong**: `mysite.zip` contains a folder called `mysite`, and inside that folder is `index.html`. - **Right**: `mysite.zip` opens straight into `index.html`, `style.css`, `images/`, and so on. If the host looks for `index.html` at the root of the zip and instead finds a subfolder, it won't know where your homepage is, and visitors will see an error or a blank page instead of your site. > Pro tip: before you upload anywhere, double-click your zip file and confirm `index.html` is the first thing you see, not a folder. Ten seconds of checking saves a confused support ticket later. ## How do I actually host the zip file with Droply? Go to Droply, drag your zip file onto the upload area, and type in the name you want for your site. Droply extracts the archive automatically and publishes it at `https://.droply.id`, live and reachable over HTTPS immediately, with no separate "deploy" or "build" button to click. Concretely, the flow looks like this: 1. Zip your static site folder (contents at the root, as above). 2. Drag that zip file onto Droply's upload area, or click to browse and select it. 3. Type a name, like `client-proposal` or `launch-page`. 4. Wait a few seconds while Droply extracts the files. 5. Get your live link: `client-proposal.droply.id`. If you need to fix a typo or swap in a new version later, re-upload the zip under the same name. The content updates in place and the URL stays exactly the same, so any link you've already shared (in an email, a Slack message, a client proposal) keeps working. ## What if I only have a single HTML file, not a whole site? You don't need to zip anything for a single file. Droply also accepts a lone [HTML file](/html-hosting) or a PDF directly, no compression required, so if your "site" is really just one page or one document, skip the zip step entirely and drag the file straight in. This is common for freelancers sharing a one-page pitch, a design mockup exported as HTML, or a signed contract as a PDF. The same naming and live-link process applies either way. ## Can I use a custom domain instead of the droply.id subdomain? Yes, but it requires a paid plan. The free flow gives you a working `.droply.id` link right away; if you want your own domain, like `sitename.com`, pointing at the same hosted files, that's a feature on Droply's [paid plans](/pricing), which also remove the "powered by Droply" banner shown on free sites. For a quick client preview or an internal draft, the free subdomain is usually enough. For a real client-facing launch, a custom domain looks more professional and is worth the upgrade. ## When should I use something other than Droply? Droply is built for exactly one job: taking pre-built static files (HTML, a zipped site, or a PDF) and making them live instantly, and it does that job with almost no setup. If your project needs a database, user logins, server-side code, or a build pipeline that runs every time you push a change, you need a different kind of host, such as a platform that runs your build process for you. Be honest with yourself about which category your project falls into. If you already have an `index.html` sitting in a folder, or your generator already produced one, you're in static-site territory, and that's where Droply is the fastest path from files to a working link. ## Quick checklist before you call it done Run through this once your site is live: - Your zip file's contents sit at the root level, with `index.html` visible immediately when opened, not buried in a subfolder. - You uploaded to Droply and got back a working `https://.droply.id` link. - You opened that link in a browser and clicked through the main pages to confirm images, styles, and links all load correctly. - If you'll be updating the site later, you know to re-upload under the same name rather than creating a new one. - If this is for a client or public launch, you've decided whether you need a custom domain from the [pricing page](/pricing). Hosting a zipped static site shouldn't take longer than building it did. [Drag your zip onto Droply](/) and it's live in seconds. --- Source: https://droply.host/blog/how-to-host-a-one-page-pdf-brochure-fast-comparison # How to Host a One Page PDF Brochure | Fast Comparison Published Jul 31, 2026 by The Droply Team. ## The short answer If you want a clean link you can put on a business card, in an email signature, or in a text message, use Droply: drag the PDF in, pick a name, and you get a live link at `.droply.id` in seconds. If the brochure is only ever going to one or two people and you don't care about the link looking professional, a Google Drive or Dropbox share link works too, but it comes with a login wall, a preview screen, and a URL full of random characters. Here's how to host a one page PDF brochure without any of that friction, plus when another option actually makes more sense. ## Quick comparison | Option | Link looks like | Login/ads required | Setup time | Best for | |---|---|---|---|---| | Droply | `yourbrand.droply.id` | No | Under a minute | Sharing publicly, on a card or in a signature | | Google Drive | `drive.google.com/file/d/xyz123.../view` | Sometimes (viewer prompt) | 2-3 minutes | Internal team sharing | | Dropbox | `dropbox.com/s/xyz.../brochure.pdf` | No, but shows a Dropbox page first | 2-3 minutes | Quick one-off shares | | Email attachment | No link, a file download | No | Instant | Direct, one-time delivery | | Your own web host | `yoursite.com/brochure.pdf` | No | Hours (if you don't already have hosting) | You already run a full website | ## Why the link itself matters A brochure is a sales tool, and the link is part of the pitch. A URL like `drive.google.com/file/d/1a2B3c9XyzAbc/view` looks like an accident, not something a business sent on purpose. It also often shows a "you need permission" screen if the sharing settings aren't exactly right, which kills the moment right when someone's ready to look. A link like `northpine-design.droply.id` reads like a real destination. It's short enough to say out loud, easy to put on a printed card, and doesn't ask the visitor to sign in to anything. ## Worked example: getting a brochure online Say you run a small landscaping business and just finished a one page PDF called `northpine-2024-brochure.pdf`, built in Canva and exported as a PDF. Here's the flow on Droply: 1. Go to Droply and drag `northpine-2024-brochure.pdf` onto the upload area (no account setup maze, no file size surprises for a single-page PDF). 2. Pick a name, something like `northpine`. This becomes part of your link. 3. Within a few seconds, Droply gives you a live HTTPS link: `northpine.droply.id`. 4. Open that link in a browser tab. The PDF loads directly, no download prompt, no "request access" screen. 5. Put that link in your email signature, on your Google Business profile, or in a text to a prospective customer. If you update the brochure later (new pricing, new photo, fixed typo), you re-upload the new PDF under the same name. The link stays exactly the same, so anything you've already printed or sent keeps working. ## When another option is genuinely better Droply is built for exactly this kind of static file (a PDF, an HTML page, a ZIP of a small site), so a one page brochure is squarely what it's for. But it's worth being honest about the alternatives: - **Google Drive or Dropbox** make more sense if the brochure is an internal draft you're circulating for feedback among coworkers who already live in that ecosystem. Comments and version history matter there, and a plain hosted link doesn't do that. - **Email attachment** is fine if you're sending the PDF directly to one person and you know they'll open the email. There's no link to manage at all, but it doesn't scale if you want to reuse the same brochure across a website, business card, and signature. - **Your own web host** makes sense only if you already have a full website with hosting set up. Spinning up server hosting just to serve one PDF is a lot of overhead for a single-page file. For the common case (a small business, a freelancer, or an agency that wants a shareable brochure and doesn't want to think about hosting again) Droply is the simplest fit: no server config, no code, and it's still just a static file being served, not a server running your code. ## Checklist: confirm your brochure link is ready - The PDF opens directly in a browser tab, no download prompt forcing a save first - The link is short enough to read aloud or type from memory - Opening the link on a phone shows the PDF cleanly, not a "open in app" wall - You've tested the link from a different device or browser (not just the one you uploaded from) - You know how to update the file later without changing the link (re-upload replaces content in place) ## Try it now A one page PDF brochure doesn't need a website project behind it, just a link that works. [Drag your file onto Droply](/) and it's live in seconds. --- Source: https://droply.host/blog/droply-vs-vercel-which-should-you-use-for-a-static-site # Droply vs Vercel: Which Should You Use for a Static Site? Published Jul 29, 2026 by The Droply Team. If you have a folder of HTML, CSS, and JS sitting on your desktop, the question is simple: what is the fastest, most reliable way to put it online? Two options come up often, Droply and [Vercel](/vercel-alternative). This droply vs vercel comparison walks through how each platform actually works, where each one shines, and how to decide based on your project rather than hype. Both can host a static site. But they are built around very different assumptions about who you are and what you are shipping. ## The short version - **Droply** is a drag-and-drop host for static sites, single HTML files, and PDFs. You drop a file or ZIP, pick a name, and get a live HTTPS URL at `.droply.id`. No git, no build step, no config. - **Vercel** is a full frontend platform built around git and framework builds. You connect a repo, and Vercel builds and deploys your app, with serverless functions, edge middleware, previews per pull request, and a large ecosystem. If your output is already built and you just need a URL, Droply is faster. If you are building a Next.js app with serverless APIs, Vercel is the natural home. ## How the workflows actually differ ### Droply's workflow 1. Drag an HTML file, a ZIP of a static site, or a PDF into the browser. 2. Pick a subdomain. 3. Copy the live URL. That is the whole loop. Re-uploading replaces the content in place, and the URL never changes. There is no CLI to install, no repo to create, no build to configure. Droply is static only, it hosts pre-built output and never runs builds or server-side user code. ### Vercel's workflow 1. Push your code to GitHub, GitLab, or Bitbucket. 2. Import the repo into Vercel. 3. Vercel detects the framework, runs the build, and deploys. 4. Every push triggers a new deployment; every pull request gets a preview URL. Vercel is optimized for teams that live in git and want CI/CD as the default. The build system supports dozens of frameworks and adds serverless functions, edge functions, image optimization, analytics, and more. ## When Droply is the better fit ### You already have built output If you have a `dist/`, `build/`, or `_site/` folder, from Astro, Hugo, Eleventy, Vite, or a hand-written HTML file, you do not need a build platform. You need a host. Droply takes the ZIP and serves it. You skip the "connect a repo, wait for a build, debug an environment variable" loop entirely. ### You are sharing a one-off page or PDF Sending a proposal, a landing page mock, a design spec, or an event invite? Droply gives you a clean URL in seconds. Vercel can technically do this, but the setup cost, a repo, a config, a build, is out of proportion to the task. ### You are shipping a client prototype Freelancers and agencies often need to show a client something clickable today, not tomorrow. With Droply, you drop the exported prototype and send the link. On paid plans you can attach a custom domain and remove the "powered by" banner so it looks like your own. ### You want a stable URL that never changes Because re-uploading replaces content in place, you can send a link once and keep updating what lives behind it. Handy for living documents, evolving demos, or pages you iterate on with a client over a week. ### You do not want a build pipeline If your site is plain HTML and CSS, a build pipeline is overhead. Droply removes it. ## When Vercel is the better fit ### You are building a dynamic frontend app Next.js with server-rendered pages, API routes, middleware, or ISR, this is exactly what Vercel is built for. Droply cannot run any of it, because Droply does not execute server-side code. ### You need serverless functions If your project depends on backend endpoints, auth, form handling, database calls, third-party API proxies, Vercel's serverless and edge functions solve that in the same platform. On Droply, you would need to host those endpoints somewhere else. ### You want git-based CI/CD Teams that already work in pull requests benefit from Vercel's preview deployments. Every PR gets its own URL for review. If your review process depends on this, Vercel is a strong default. ### You want framework-specific optimizations Vercel's image optimization, font handling, and edge caching are tuned to specific frameworks. If you are deep in that ecosystem, you will feel the benefit. ## Where the two overlap Both platforms: - Serve static assets over HTTPS with a global CDN. - Support custom domains on paid plans. - Give you a working URL without touching a server. For a plain static site, either will get the job done. The real question is how much machinery you want between your files and the live URL. ## A practical decision guide Ask yourself these questions in order: 1. **Does my project need server-side code or serverless functions?** If yes, use Vercel. 2. **Is my project a Next.js app or similar framework-heavy application?** If yes, use Vercel. 3. **Do I already have built static output, or a single HTML file or PDF?** If yes, Droply is faster. 4. **Am I sharing a one-off page, prototype, or document?** If yes, Droply is faster. 5. **Do I want to avoid git, builds, and CLI tools for this project?** If yes, Droply is the point. There is no rule that says you must pick one for everything. Many people use Vercel for their production app and Droply for the dozen small pages, prototypes, and shared documents that do not deserve a repo. ## What about cost? Both platforms have free tiers and paid plans. Pricing changes often, so check each provider directly. For Droply, paid plans add custom domains and remove the "powered by" banner, see [pricing](/pricing) for details. Compare based on what your project actually needs: bandwidth, custom domains, team seats, and build minutes are the usual variables. ## The honest summary Droply and Vercel are not really competitors so much as tools for different jobs. Vercel is a frontend cloud. It is powerful, opinionated, and built around git and framework builds. If you are shipping a real application with dynamic behavior, it is a strong choice. Droply is a static file host with a drag-and-drop interface. It exists for the moments when you have a finished thing, a static site, a PDF, a prototype, and you need it online now, without ceremony. If you find yourself opening a terminal to deploy a two-page marketing site or a client mockup, that is the moment to try Droply. Drag the file in, pick a name, send the link. --- Source: https://droply.host/blog/how-to-share-a-figma-prototype-export # How to Share a Figma Prototype Export Published Jul 27, 2026 by The Droply Team. The fastest way to share a Figma prototype export is to upload the exported files somewhere that gives you a live web link, so anyone can open it in a browser without a Figma account. Figma's own share link works too, but it requires the viewer to log in or accept an invite, which is friction you don't need when you're sending something to a client at 6pm on a Friday. This guide covers both routes: sharing directly from Figma, and exporting your prototype as static files (plain HTML pages that don't need a server to run) and hosting them with a tool like Droply so you get a permanent, no-login link. ## What's the difference between a Figma share link and an exported build? A Figma share link opens the prototype inside Figma's own viewer, which means the person needs a Figma account (or at least a free guest login) and an internet connection to Figma's servers. An exported build is a set of static files (HTML, images, CSS) generated by a plugin, which you can host anywhere and open like any normal website, no Figma account required. Share links are best for quick internal feedback with people already on your team. Exported builds are better when you're sending a prototype to a client, a stakeholder outside your company, or anyone who might be annoyed by a login wall. ## How do I export my Figma prototype as static files? Figma doesn't have a native "export as website" button, but community plugins fill the gap. Two common ones: - **Figma to HTML** style plugins that export frames as a navigable HTML site with clickable hotspots matching your prototype flow. - Manual export of frames as PNG/SVG plus a simple HTML wrapper if you want full control. Run the plugin, export, and you'll get a ZIP file (a compressed folder) containing an index.html file and any assets it needs. That ZIP is what you'll upload to get a live link. ## How do I turn that export into a link I can send? Once you have the ZIP or the HTML file, drag it onto [Droply](/), pick a name, and your prototype is live at yourname.droply.id in seconds. There's no git (a code versioning tool), no build step, and no server setup: Droply just hosts the file exactly as exported and serves it over HTTPS. The exact flow: 1. Export your prototype from Figma as a ZIP (or a single HTML file if that's all the plugin gives you). 2. Go to Droply and drag the file onto the upload area. 3. Type a name, like "acme-onboarding-v2". 4. Copy the link: acme-onboarding-v2.droply.id, and paste it into your email or Slack message. If you update the prototype later, export again and re-upload with the same name. The URL never changes, so you don't have to re-send a new link every round of feedback, which matters a lot when a client has already bookmarked the old one or pasted it into a deck. ## What if my export won't work as a hosted site? If your exported HTML relies on Figma's own viewer scripts to work (some plugins do this), it may not render correctly outside Figma. Check by opening the exported index.html file locally in your browser first: if it looks right, it'll work fine once hosted. If it doesn't render, fall back to exporting flat images (PNG or PDF) of each screen and hosting those instead, or stick with Figma's built-in share link for that particular prototype. Droply also hosts PDFs directly the same way, drag it on, name it, done, which is a solid backup if the interactive export is being difficult. ## Quick reference: which sharing method fits your situation | Situation | Best option | |---|---| | Quick feedback from teammates already in Figma | Figma share link | | Client or external reviewer, no Figma account | Exported HTML hosted on Droply | | Prototype has custom fonts or complex interactions | Test locally first, then host if it renders | | You just need to show static screens, no clicks | Export as PDF, host on Droply | | You want a permanent link that survives re-exports | Droply (URL stays the same on re-upload) | ## Do I need a developer to host an exported prototype? No. Hosting a static export doesn't require writing code or configuring a server, it's just uploading files. Tools built for this, like Droply, are designed for exactly this drag-and-drop use case, so a designer or founder can do it without pulling in engineering time. If you're already comfortable with git and command lines, you could push the export to [GitHub Pages](/github-pages-alternative) or a similar service, but for a one-off client share, that's a lot of extra steps for the same result. ## FAQ **Can I password-protect a shared prototype?** Figma's own share links support view permissions and access controls within Figma. If you're hosting an exported static build elsewhere, check whether your host offers that; otherwise, treat the link as unlisted rather than fully private, and avoid sending it anywhere public. **Will the exported version look exactly like the Figma prototype?** Mostly, but interactions that depend on Figma's live rendering engine (like some smart animate transitions) may not translate perfectly to static HTML. Always preview the exported file locally before sending it out. **Can I use my own domain instead of a droply.id link?** Yes, paid Droply plans support custom domains and remove the "powered by" banner. See [pricing](/pricing) for details. **What happens if I need to send an updated version after feedback?** Re-export from Figma and re-upload to Droply using the same project name. The link stays identical, so anyone with the old URL automatically sees the latest version. Drag your exported prototype onto [Droply](/) and it's live in seconds, ready to send to anyone without a Figma login in the way. --- Source: https://droply.host/blog/how-to-host-your-lovable-site-for-free # How to Host Your Lovable Site for Free Published Jul 15, 2026 by The Droply Team. Lovable is great for going from idea to working prototype fast. But once you've built something, you need a way to share it, with a client, a teammate, a hiring manager, or the internet. The good news: if your Lovable project is a static front-end, you can host your Lovable site for free without touching git, servers, or build pipelines. This guide walks through the fastest path: export the built output from Lovable, then drop it on a static host that gives you a live HTTPS URL in seconds. ## What "hosting a Lovable site" actually means Lovable generates a front-end app, typically a React/Vite project. When you export or build it, you end up with a folder of static files: `index.html`, some JavaScript bundles, CSS, and assets. That folder is the entire site. Any static host can serve it. There are two things to be clear about before you pick a host: - **Static vs. server code.** If your Lovable project only calls external APIs (Supabase, Stripe, OpenAI, your own backend), it's purely static and can be hosted anywhere. If you added a custom Node server, you'll need a platform that runs Node, that's a different problem. - **Environment variables.** Any keys baked into the build are shipped to the browser. Use public/anon keys only, and put sensitive logic behind an API you control. Assuming you're in the common case, a static Lovable front-end talking to Supabase or similar, you can host your Lovable site for free in under five minutes. ## Step 1: Export your Lovable project Inside Lovable, connect the project to GitHub (or use the built-in export) so you have the source code locally. Then, in a terminal: ``` npm install npm run build ``` This produces a `dist/` folder (Vite's default) containing your production site. That's the folder you'll upload. If your `package.json` uses a different output directory, check the `build` script, it'll be `dist`, `build`, or `out` in almost every case. Quick sanity check before uploading: - Open `dist/index.html`, it should exist and reference hashed JS/CSS files. - Preview locally with `npx serve dist` and click through the app. If it works here, it'll work when hosted. - If your app uses client-side routing (React Router), make sure your host supports SPA fallback to `index.html`, or configure hash-based routing. ## Step 2: Pick a free static host There are several ways to host your Lovable site for free. The right choice depends on how much setup you're willing to do. ### Option A: Droply (drag-and-drop, no git) If you just want a URL right now, zip your `dist/` folder and drop it on [Droply](https://droply.host). You pick a name, and your site goes live at `yourname.droply.id` over HTTPS in a few seconds. No git, no build config, no CLI. This is a good fit when you want to: - Share a Lovable prototype with a client or stakeholder immediately. - Publish a landing page, portfolio, or one-off microsite. - Push updates by re-uploading, the URL never changes, so links you've shared keep working. - Host a PDF spec, pitch deck, or design doc alongside the site under the same account. Paid plans add custom domains and remove the "powered by" banner. See [/#pricing](/pricing) for details. ### Option B: Netlify or Vercel (git-based) Both offer generous free tiers for static hosting and integrate with GitHub. You connect the repo, they run `npm run build` on their servers, and deploy the output. Great if you want auto-deploy on every push and you're comfortable with CI-style workflows. Trade-off: you need a GitHub repo, a working build config, and you'll spend more time on setup than on shipping. If Lovable already handles the build for you, running it again in CI is redundant. ### Option C: GitHub Pages or Cloudflare Pages Also free, also static. [GitHub Pages](/github-pages-alternative) is fine for personal projects but has quirks around SPA routing and custom domains. Cloudflare Pages is faster and more flexible but has a similar git-first workflow to Netlify/Vercel. ### Which should you pick? - **You want it live in 60 seconds:** Droply. Drag, drop, done. - **You want automatic redeploys from a repo:** Netlify, Vercel, or Cloudflare Pages. - **You want the deepest free tier for a long-term project with build steps:** Netlify or Vercel. For most Lovable users, especially designers, founders, and freelancers sharing work, the drag-and-drop path wins because the build already happened on your machine. ## Step 3: Deploy ### Deploying via drag-and-drop 1. Run `npm run build` in your Lovable project. 2. Zip the `dist/` folder (or upload it as-is if your host accepts folders). 3. Drop the file on the host, pick a subdomain name, and wait a few seconds. 4. Open the URL and test the app end-to-end. To update the site later, re-upload. On Droply, re-uploading replaces the content in place, so the URL stays the same, send it to a client once and keep iterating behind it. ### Deploying via git 1. Push your Lovable project to GitHub. 2. Connect the repo to Netlify, Vercel, or Cloudflare Pages. 3. Set build command to `npm run build` and output directory to `dist`. 4. Trigger the first deploy. Future pushes redeploy automatically. ## Step 4: Handle the details A few things that catch people out when they host their Lovable site for free: - **API keys.** Anything in `import.meta.env.VITE_*` ends up in the browser bundle. Use public keys only. - **CORS.** If Lovable calls your own backend, make sure that backend's CORS allow-list includes the new production URL. - **SPA routing.** If you get a 404 when refreshing a deep link, configure the host to fall back to `index.html` for unknown routes. - **Assets.** Large images and videos count against bandwidth on free tiers. Compress before shipping. - **Custom domain.** Free subdomains are fine for prototypes. When you're ready to put the site on your own domain, most hosts (including Droply on paid plans) support it with a DNS record. ## Beyond the Lovable site Once you have a fast, free static host wired up, it becomes the default place to put anything you need to share: - A standalone `index.html` mockup you're prototyping outside Lovable. - A PDF proposal or case study you want to send as a link instead of an attachment. - A ZIP export from Figma, Framer, Webflow, or any other tool that produces static output. That's the whole point of static hosting: one workflow, many outputs. Build in Lovable, export, drop it on a host, share the link. The less time you spend on infrastructure, the more time you spend on the work itself. --- Source: https://droply.host/blog/droply-vs-github-pages-which-should-you-use # Droply vs GitHub Pages: Which Should You Use? Published Jul 7, 2026 by The Droply Team. If you need to put a static site, prototype, or PDF on the internet, both Droply and [GitHub Pages](/github-pages-alternative) will get the job done. They take very different paths to get there, though, and the right choice depends on how you work, not which one is "better" in the abstract. This is an honest look at where each one fits. ## The short version - **Use GitHub Pages** when your project lives in a Git repository, you want builds tied to commits, and you're comfortable with the GitHub workflow. - **Use Droply** when you have a finished file or folder and want it live in seconds without touching Git, CI, or config. Both host static content over HTTPS. Neither runs server-side code. The differences are about workflow, speed to publish, and what you're hosting. ## How publishing actually works ### GitHub Pages GitHub Pages is tied to a Git repository. You push your site's source or built output to a branch, configure Pages in the repo settings, and GitHub serves it from a `github.io` subdomain or a custom domain you point at it. If your site needs a build step, a Jekyll site, a React app, a static site generator, you typically wire up GitHub Actions to build on every push and deploy the output. This is excellent if you already use Git. Every change is versioned, rollbacks are a `git revert` away, and collaborators can open pull requests against your site. The build pipeline is part of the platform. The trade-off is setup. You need a repo, a branch strategy, and, for anything non-trivial, a working Actions workflow. First-time deploys can take a few minutes once you account for build and propagation. ### Droply Droply takes the opposite approach. You drag an HTML file, a ZIP of a static site, or a PDF onto the page, pick a name, and you get a live HTTPS URL at `.droply.id` in seconds. No repo, no build step, no YAML. Re-uploading replaces the content in place, the URL stays the same. That means you can share a link once and update what's behind it as many times as you want. The trade-off: Droply hosts pre-built output. It doesn't run a build for you. If you use a static site generator, you run `npm run build` (or whatever your tool uses) locally, zip the output folder, and drop it on Droply. ## Where GitHub Pages is the better fit **You already work in Git.** If your site source is in a repo and you're comfortable with branches and PRs, Pages slots into the workflow you already have. **You want builds tied to commits.** Continuous deployment from a `main` branch is a clean model. Every commit is a deploy; every deploy is a commit. You get a clear audit trail for free. **You need PR previews or team review workflows.** GitHub Actions plus Pages (or third-party Pages-adjacent setups) can give you per-PR preview URLs and review gates. That's a real win for teams shipping marketing sites or docs. **Your project is open source.** Hosting docs for an open source project next to the code on GitHub is the path of least resistance and signals trust to contributors. **You want version history of the site itself.** Git already gives you that. Rolling back to last Tuesday's version is one command. ## Where Droply is the better fit **You have a finished file or folder to ship right now.** A client deliverable, a landing page, a one-pager, a portfolio export from Webflow or Framer, a PDF proposal. Droply is built for the "I just need this online" case. **You don't want to manage a Git repo for a one-off.** Not every static asset deserves a repository, a README, and a deploy workflow. Sometimes you just want a URL. **You're sharing a PDF.** Droply hosts PDFs as first-class content. On GitHub Pages, you'd commit the PDF to a repo and link to it, workable, but heavier than it needs to be. **You want a stable URL that follows the content, not the file name.** Re-uploads on Droply replace the content in place. You can send a proposal link to a client on Monday, update the PDF on Thursday, and the link still works. **You're not technical, or you're handing this to someone who isn't.** Drag, drop, done is easier to teach than `git push origin main`. **You want speed to first publish.** From "I have a ZIP" to "here's a live URL" is measured in seconds, not minutes. ## Where they're roughly even - **HTTPS by default.** Both serve over HTTPS. - **Static hosting.** Both serve pre-built static files. Neither runs your server-side code. - **Custom domains.** GitHub Pages supports custom domains on free plans. Droply supports custom domains on paid plans, see [pricing](/pricing) for details. - **Branding.** GitHub Pages doesn't add a banner. Droply's free tier shows a small "powered by" banner; paid plans remove it. ## Common scenarios **"I built a React app and want it online."** Either works. GitHub Pages is natural if your source is already on GitHub and you want CI to build on every push. Droply is faster if you just want to `npm run build` locally, zip the `dist` folder, and ship it. **"I'm sending a client a proposal PDF."** Droply. The drag-and-drop flow, stable URL on re-upload, and PDF-as-first-class support match the use case exactly. **"I'm hosting docs for an open source library."** GitHub Pages. Keeping docs next to code is the convention, and Pages integrates cleanly with documentation generators via Actions. **"I exported a site from Figma, Webflow, or Framer."** Droply. You have a pre-built folder; you want it online. There's no build pipeline to wire up. **"I'm a team of five shipping a marketing site with review workflows."** GitHub Pages, probably. The PR-based review model is hard to replicate with drag-and-drop. **"I built a quick prototype and want to send a link to three people."** Droply. Setting up a repo for a prototype is overkill. ## How to decide Ask one question: **does your project benefit from being in Git?** If yes, because you want version history, CI builds, PR reviews, or you're already living in GitHub, use GitHub Pages. It's a strong, mature option, and the workflow integration is the whole point. If no, because you have finished output, you're moving fast, you're sharing a document, or Git is friction you don't need, use Droply. It's built for the moment between "this is done" and "here's the link." Both tools are good at what they do. They're just aimed at different points in the workflow. --- Source: https://droply.host/blog/how-to-publish-ai-generated-html-from-chatgpt-claude-or-lovable # How to Publish AI-Generated HTML from ChatGPT, Claude, or Lovable Published Jul 6, 2026 by The Droply Team. AI tools are great at producing a full HTML page in one shot. You ask ChatGPT for a landing page, Claude for a pricing table, or Lovable for a small app prototype, and you get back a working file. The awkward part is what comes next: turning that file into a real URL someone else can open. This guide walks through the practical steps, getting clean, self-contained HTML out of each tool, sanity-checking it locally, and putting it online fast. ## Step 1: Get clean, self-contained HTML out of the AI tool The biggest mistake people make is copying half the output. You want a single, complete document that starts with `` and ends with ``. If the AI splits things across multiple files or assumes a build step, you'll have a bad time deploying it. ### Prompting ChatGPT ChatGPT will often default to React snippets or framework-specific code. To get a deployable file, be explicit: > "Give me a single self-contained `index.html` file. Inline all CSS in a `