Files
FileHost/docs-site/en/guide/storage.md
T
O96u 8408d01197
GitHub Release / release (push) Canceled after 0s
ci / ci (22, ubuntu-latest) (push) Canceled after 0s
Publish Docker image / build (linux/amd64, ubuntu-latest, amd64) (push) Canceled after 0s
Publish Docker image / build (linux/arm64, ubuntu-24.04-arm, arm64) (push) Canceled after 0s
Publish Docker image / merge (push) Canceled after 0s
release: v1.2.6 — 新 UI 体验优化与存储标识规则
2026-09-01 21:31:02 +08:00

2.7 KiB

Storage

PicHost supports local disk and S3-compatible object storage (Cloudflare R2, Tencent COS, Alibaba OSS, AWS S3, etc.). Admins manage backends at Storage (/storage); new uploads go to the default backend. The page shows a storage overview (total, used, remaining, usage rate, capacity chart) plus per-backend cards and supported backend types.

Storage management

Layout (local)

/data
├── pichost.db          # SQLite: users, sessions, settings, storage_backends, images index
└── images/             # All files when using local backend
  • New uploads: images/randomId.webp or images/YYYY/MM/randomId.webp (flat mode in Settings)
  • Migrated legacy: images/blog/... and similar
  • With cloud backends, blobs live in the bucket; index stays in SQLite images

All keys start with images/. The upload API does not accept a folder parameter.

Adding a backend

  1. Sign in as admin → Storage → Add backend.
  2. Choose local disk or S3-compatible (R2 / COS / OSS presets).
  3. Enter connection details (bucket, endpoint, keys).
  4. Set as default so new uploads use it.

New object-storage backends get an auto-generated storage ID prefix: local for disk; r2-* for R2; cos-* for COS; oss-* for OSS; s3-* for AWS S3 and custom S3-compatible endpoints (immutable after creation; the image index references this ID).

Cloudflare R2

Field Value
Endpoint https://<account_id>.r2.cloudflarestorage.com
Region auto
Bucket Your R2 bucket name
Keys R2 API token access / secret

The cloudflare branch streamlines R2-only deploys; see branch notes on the docs overview.

Environment variables (optional)

Some installs seed a default S3 backend via STORAGE_BACKEND=s3, S3_ENDPOINT, S3_BUCKET, S3_ACCESS_KEY, S3_SECRET_KEY, S3_REGION. UI-configured backends live in SQLite alongside env-based defaults.

URL modes

Mode Behavior
proxy Serve via PicHost (GET /images/...)
public 302 redirect to bucket/CDN public URL

Copied links use IMAGE_BASE_URL. “Hide folder prefix” may shorten URLs; the server resolves by path or basename.

  • Per-backend usage on the Storage page
  • Gallery filters by storage backend and upload source; grid/list view toggle

Backup

Back up data/images/, data/pichost.db, and bucket objects.

Upgrading from v1.1.x with parallel folders: v1.2 migration.

See also