Story Builder documentation

Images

Pictures attached to a project — character portraits, reference art, the map you drew — and the storage they use.

Where images come from

Anywhere a record takes a picture: a character's portrait, a map's base image, a cover for a published story. Every upload also lands in the project's image library, so a picture used in one place can be found and reused in another rather than uploaded twice.

Limits

Limit Value
One file 20 MB
Everything in a project 50 MB

Every picture belongs either to a project or to your account: an avatar is yours, and everything uploaded inside a project counts against that project's allowance.

The storage meter in the images module shows how much of the project's allowance is used. When it fills, the answer is usually to delete a few large reference images rather than to shrink what you are keeping — a portrait at a sensible size costs very little, and one unresized photograph can cost more than a hundred of them.

Images are re-encoded on upload, so what is stored is generally smaller than what you sent.

Who can see them

An image in an unpublished project is private to the people who can open the project. It is served through a link that expires and is renewed while you are looking at it, so a URL copied out of the page does not become a permanent public address for private work.

An image in a published story is public, deliberately and permanently, because that is what publishing means. Think of the difference as: private work gets a key that keeps changing, published work gets an address.

Deleting

Deleting an image removes it from the library and from anything using it. Unlike records, an image is not held in the archive — once it is gone the file is gone, so check what uses it first.