Tuxia

图匣Live

An image management and hotlinking service that runs on Cloudflare Workers.

What it is

Tuxia is an image-hosting service running on Cloudflare Workers, with built-in R2, personal/shared S3, content deduplication, a public gallery, API tokens, email verification, and user permissions. The front end is a React SPA; the back end is a Hono Worker plus D1.

Screenshots

Tuxia home page: a hero headline and capability cards — Home: upload, hotlinks, multi-storage, and an open API

Tuxia public gallery: community-shared images — Public gallery: community-shared images

Tuxia login: email/password sign-in with an image captcha — Login: email/password with an image captcha

What it does

Multiple storage backends

Built-in R2, or connect personal / admin-shared S3-compatible storage.

Content deduplication

Deduplicate by content hash — identical images keep just one object.

Public gallery

Publish images to a public gallery, or keep them private to yourself.

API tokens

Issue tokens for scripts or third-party clients to upload, with scoped permissions.

Accounts & permissions

Email verification and user permission management, built on Better Auth.

Edge direct links

With an R2 public domain configured, file requests 302 straight to the object, bypassing the Worker proxy.

Why I built it

Image hosts are plentiful, but many are crowded with ads, may disappear without warning, or keep your files in infrastructure you cannot control.

Tuxia takes a different approach: run the image host in your own Cloudflare account. You own the storage, database, and authentication while benefiting from edge delivery at very low cost.

Architecture

Tuxia combines a Hono Worker with a React SPA:

Hono Worker provides the REST API and Better Auth endpoints
React + React Router + Ant Design power the client application
TanStack Query manages request caching, retries, and loading states
D1 + Drizzle ORM store users, image metadata, storage settings, and tokens
R2 / S3-compatible storage holds image objects
Workers Static Assets serves static files; only /api/* invokes the Worker

Highlights

Multiple storage backends: built-in R2 or personal and shared S3 storage
Content deduplication: identical images are stored only once
Public gallery or private files: choose visibility per image
API tokens: controlled access for scripts and third-party clients
Edge direct links: redirect file requests to a public object URL

Who it is for

Developers and writers who want a controlled, low-cost image host
People already using Cloudflare who want to reuse R2 and D1
Toolchains that need automated image uploads through an API