Skip to content
Dropkit Docs

Folders and share links

Folders are a way to group files inside a project from the dashboard. They are not exposed on the SDK or the /v1/* API. Files are still addressed by <id> everywhere; the folder is just metadata for the dashboard’s own view.

If you want folder support in the API, open an issue. We added the data model first to ship the dashboard UX without locking ourselves into a wire format.

Creating folders

Files tab, top of the page. Click New folder, type a name, hit return.

Files always live somewhere: either in a folder, or at the project root. Switch views with the Root / All files / <folder> pills above the file list.

Drag-drop or click-to-upload while a folder is selected and the file lands inside that folder. Move existing files in via the per-file move icon.

Deleting a folder

Hover the folder pill, hit the trash icon. Files inside the folder are not deleted: they fall back to the project root. The deletion is irreversible for the folder itself.

Open a folder, the share panel sits above the upload zone. Toggle Create link and you get a URL of the shape:

https://dash.dropkit.app/share/<projectSlug>/<shareSlug>

The slug auto-fills from the folder name. You can edit it before submitting; it must be unique within the project.

The page lists every public file in the folder, with thumbnails for images. Private files are skipped, so you can keep an internal screenshots/ folder where most files are public and a few are private without leaking the private ones.

Expiry

Pick 7 days, 30 days, 90 days, 1 year, or Never expires. Past the expiry, the URL returns 410 Gone. There is no manual extension yet: re-create the link.

Click Unshare in the share panel. The slug is freed up immediately and the public URL starts returning 404.

What is not in v1

  • Custom domains for share pages. You can already point a custom hostname at the CDN for the underlying file URLs; share pages only ever live at dash.dropkit.app/share/....
  • Theming the share page. The page is intentionally minimal: project name, folder name, file grid. No logos, no branding, no analytics.
  • Password-protected links.
  • Nested folders. The schema has a parent_id column reserved for this, but the dashboard renders folders flat.
  • Folder support in the SDK / /v1/* API.

If you need any of these, open an issue and tell us why. The current scope is what we’d actually maintain ourselves; everything else is opt-in based on real demand.

Blur-hash placeholders

When you upload an image from the dashboard, the browser computes a small blurhash for it before the upload completes. The hash is stored next to the file and used as a low-bandwidth placeholder behind thumbnails on both the dashboard and any public share page.

Uploads through the SDK or REST API don’t compute a blur-hash today: there’s no canvas in a server runtime. Re-upload from the dashboard if you want the placeholder. Or open an issue and we’ll consider adding a worker-side encoder.