# 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)