pixeldrive

Sharing

The listing is unpublished until you opt in. Share a whole project, or one folder, without putting every JSON listing on the internet. On a public project the files themselves are already in public storage. Private projects never publish a listing — use an API key.

How visibility works

  • Off by default. Undefined means private.
  • A project listing is public only when that project’s share toggle is on.
  • A folder listing is public if that folder or any ancestor (parent folders, then the project) is shared. Sharing a folder exposes its subtree even when the project stays private.
  • Ids are unguessable so listings can’t be enumerated. The share flag is still the gate for JSON — not for the bytes.

Where to flip it

  • Project — Settings → Public API. Copy https://api.pixeldrive.dev/v1/projects/…
  • Folder — open the folder in the file browser. Same toggle, folder URL.
  • API key — A key lists its project even when sharing is off, and is the only way to list a private project. Write keys can POST /v1/upload. Shown once at creation.

Revoking a listing

Turn sharing off, or rotate the public id. Project rotation lives in settings; folder rotation is in the folder overflow menu. Rotation mints a new unguessable id; every old listing URL 404s. File CDN URLs do not change — they use the file’s own id.

What sharing does not do

  • It does not keep public-project uploads private. Those files are written to a public, unencrypted bucket at upload time.
  • It does not hide bytes already on the CDN. See File URLs.
  • A Bearer API key can list a public project even when sharing is off, and is required for private projects.
  • Listings cache for 60 seconds, so a toggle may take a minute to show up at the edge.
API reference