---
title: What Studio makes
description: The three kinds of artifact (deck, page, HTML page), who owns and sees them, the limits, and where Studio keeps what you make.
section: studio
order: 10
audience: [user, operator, builder]
sources: [services/nodejs-cloud/lib/studio/store.ts, services/nodejs-cloud/lib/studio/model.ts, services/nodejs-cloud/migrations/0320_studio.sql, docs/adr/0083-venom-studio.md]
features: []
---

## The three kinds

- A **deck** is an ordered list of slides, up to 100. Each slide picks one of the [thirteen layouts](/docs/studio/layouts-and-themes.md)
  and fills its slots (a title, some bullets, a chart). It can carry speaker notes.
- A **page** is an ordered list of [blocks](/docs/studio/blocks.md), up to 300: headings, text, tables, charts, diagrams. Use it for a
  report, a one-pager or a dashboard.
- An **HTML page** is one HTML file you write yourself: a mockup, a prototype, a landing page, an interactive tool, anything
  where the layout itself is the point. It is always shown in a sandbox, with no network and no access to your session
  ([why](/docs/studio/sharing.md#html-pages-are-sandboxed)), so its CSS, scripts, fonts and images are all inline. It can take your
  organisation's theme with one tag ([themed HTML pages](/docs/studio/layouts-and-themes.md#themed-html-pages)).

Every slide and every block has an id. Ids are stable: you choose them, or Venom gives each a short one such as `s_k3x9aa`, and
they are what [edits](/docs/studio/edits.md) point at.

## Ownership and who sees it

An artifact belongs to the person (or agent) that made it, and is private until they share it.

| Visibility | Who can see it |
|---|---|
| private | only the owner |
| team | the members of one org team, subteams included |
| org | every member of the organisation |

`shared_level` says what people other than the owner may do with a shared artifact: `view` (the default) or `edit`. The
owner can always edit, share and delete it. An org owner or admin can also rename, share differently, and delete artifacts that
are shared with the org or a team, but never someone's private ones. Anyone who can see an artifact can duplicate it to get a
private copy of their own.

A role that only reads (a viewer or billing member, or a read-only API key) reads what is shared with it and changes nothing.

## Limits

| What | Limit |
|---|---|
| Slides in a deck | 100 |
| Blocks in an artifact | 300 (columns and slides count) |
| One artifact's content | 1 MB of JSON |
| One HTML page | 512 KB |
| Versions kept | the newest 100 |
| Public links per artifact | 5 |
| Edits in one batch | 100 |

A request over a limit is refused with the number and what to do, and nothing is changed.

## What Venom keeps

Content, versions and share links are stored in your organisation's database. Rendering draws everything from the stored data
with the system fonts, so a deck looks the same with the network unplugged. Image blocks point at an `https` address or hold a
small `data:` image; Studio fetches nothing itself. Deleting an artifact moves it to the trash for 30 days (its public links
stop at once), then removes it with its versions.
