Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Troubleshooting

If an upload fails or the published site is blank, first inspect the finished static folder before uploading it: it needs an index.html entry page and every local file that page references. Then open the published link and use the browser Console and Network panels to tell an upload problem from a browser loading problem.

Start with the complete static bundle

For a multi-file site, upload the complete folder or ZIP—not only index.html. This is a working shape for a static project:
my-site/
├── index.html
├── styles/
│   └── main.css
├── scripts/
│   └── app.js
└── images/
    └── logo.svg
The references in index.html must match those paths:
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>My site</title>
    <link rel="stylesheet" href="styles/main.css">
    <script src="scripts/app.js" defer></script>
  </head>
  <body>
    <img src="images/logo.svg" alt="My site logo">
  </body>
</html>
Relative paths such as these are the safest choice. Dropley preserves the project structure and also rewrites supported root-relative HTML asset paths such as /styles/main.css; do not use paths to files on your own computer such as file:///Users/.... For a one-file page, use how to share an HTML file online; for the complete ZIP requirements, see how to publish a static website.

Identify the problem

index.html is missing

Rename the page you want visitors to open to exactly index.html, then include it in the loose-file, folder, or ZIP upload. If the project contains several index.html files, Dropley uses the shallowest one, so put the intended entry page nearest the top of the project structure.

The page publishes, but local CSS, JavaScript, images, or fonts are missing

Compare every href, src, CSS url(...), and JavaScript asset path with the uploaded tree. Upload the referenced folders alongside index.html; a local reference cannot load a file that was left on your computer. Open the published URL once and use the browser Network panel to find the specific missing request before changing the path.

A file type is unsupported

Dropley serves only the supported static file types. Files with other extensions are not included in the published artifact, so remove the dependency, convert it to a supported format, or use a static export that does not require it. Also check the current file, path, and upload limits.

The project needs a server, database, private API, or build command

Dropley serves finished static files in a browser; it does not run Node.js, PHP, Python, server-side rendering, server-side includes, or a database. Build or export the project first, then upload the output only when it contains an index.html and can work without those services. A public external service can still be a separate browser dependency, so test it from the published link.

The Console shows a CSP or network error

A successful upload does not guarantee that every browser request can load. Dropley applies Content Security Policy to published artifacts. In the browser Console, a CSP message identifies a blocked request; revise the page or dependency so it works under that policy. In the Network panel, check the request URL and status code: a failed remote request can instead be caused by that service being unavailable, requiring authentication, or rejecting the browser request. These are runtime dependency issues, not evidence that the upload failed.

Upload failures

The ZIP is too large

ZIP uploads are limited to 50 MB and 1,000 files. Optimize images, remove unused files, and review service limits before trying again.

Upload hangs or times out

Check your internet connection, try a smaller complete static bundle, and retry after a moment. If the upload completes but the page is broken, use the asset and browser checks above rather than uploading the same files repeatedly.

Expiration issues

My artifact expired before I expected

Check the expiry selected in the manage panel shown under your URL right after publishing. The default is 3 days, and the countdown starts immediately after successful publishing.

Can I extend an expired artifact?

No. Once expired, the artifact is permanently deleted. Upload it again to create a new link.

Machine-Facing API Errors

If you call the Dropley API programmatically (from a script or AI agent), failures on /api/* paths return JSON instead of an HTML page. The body is a flat object with four fields: error, code, message, and hint.
Requesting an unknown API path returns 404 Not Found with "code": "NOT_FOUND". Requesting a known API path with a disallowed HTTP method returns 405 Method Not Allowed with the same shape, plus an Allow header listing the supported methods.
The full request and response contract lives in the API Reference.

Still stuck?

Check the FAQ for common product questions. When the finished bundle is ready, publish the corrected static site.
Dropley Docs
Powered byHolocron