Publishing

Publish a library to book.cloud

Give a library its own web address and share it with the people you choose. Or self-host it and serve from infrastructure you run.

How it works

From your app to a shareable link

Publishing takes a library you keep on your device and gives it a home on the web that you can hand to others.

Publish from the app

Open a library and choose Publish. Your local copy stays put — publishing adds a served copy on book.cloud.

Get a book.cloud address

The published library gets its own book.cloud address: a link you can send to whoever you decide should have it.

Update or take it down

Edit the library in the app and publish again to change what readers see. Unpublish when you want it gone.

You choose who can see it

You set the audience for every library you publish, from a single invitee to the open web, and you can change it later.

Private

Only the people you invite can open it. A good fit for a draft, a client, or a small group.

A chosen audience

Share with specific people, or with a signed-in group, without opening the library to everyone.

Public

Anyone with the link can read it. For work you want out in the open.

Why an account

Publishing needs an account

An OpenBook account is required to publish a library on book.cloud. This allows us to detect abuse and prevent fraud.

The requirement applies only to publishing. Keeping a library on the device needs no account: writing, editing and working offline ask nothing of you.

Prefer not to use an account? Self-host.

book.cloud is the hosted option. Self-host instead and serve libraries from infrastructure you control, no account required.

Share a library when you're ready

Publish to a book.cloud address when it suits, or keep everything on the device.