> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useshareable.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Multi-page decks
> Publish a set of linked HTML files — plus their images, CSS, and JS — as one page.
A Shareable page is usually a single HTML file, but it can also be a **bundle** of
HTML files that link to each other — an investor deck, a presentation, a clickable
prototype, or a small multi-page site — along with the **assets** they reference.
## Publish a bundle
Drop a **folder** or a **`.zip`** (or select several files at once). The file named
`index.html` becomes the entry page; the others are reachable by their filenames.
Non-HTML files in the folder ship with the deck as assets:
* **Images** — PNG, JPG, WebP, GIF, SVG, ICO
* **Stylesheets and scripts** — CSS, JS
* **Fonts** — WOFF, WOFF2, TTF, OTF
* **Data** — JSON
Reference them from your HTML with relative paths (``,
``) — exactly as they sit in the folder. Anything outside
these types is skipped, and the uploader tells you what was left out.
## Linking between pages
Use **relative links** between files — `href="team.html"`, `href="deck/02.html"` —
and they resolve within your page's namespace automatically. Root-relative paths
(`/style.css`) work too.
## How it behaves
* One **access setting**, one **link** — sharing, password, or email gating applies
to the whole bundle, **assets included**: an image in a password-protected deck is
just as protected as its pages.
* One entry URL (`/p/your-slug`); visitors click through the internal links.
* [Analytics](/guides/analytics) and [version history](/guides/version-history) work
across the bundle (version history covers the HTML; assets are not versioned).
## Limits
* Up to **60 HTML files** and **60 assets** per deck
* **2 MB** per HTML file, **5 MB** per asset
* **12 MB** total per deck (HTML + assets combined)
Assets are stored privately and served only through your page's link — they're
never publicly listable, and access control is enforced on every request.
One bonus of bundled assets: your deck's
[link preview](/guides/publish-a-page#custom-link-previews-unfurls) can use one —
set `` in the entry page and
the card in iMessage/Slack shows your image instead of the generic Shareable one.
`,
``) — exactly as they sit in the folder. Anything outside
these types is skipped, and the uploader tells you what was left out.
## Linking between pages
Use **relative links** between files — `href="team.html"`, `href="deck/02.html"` —
and they resolve within your page's namespace automatically. Root-relative paths
(`/style.css`) work too.
## How it behaves
* One **access setting**, one **link** — sharing, password, or email gating applies
to the whole bundle, **assets included**: an image in a password-protected deck is
just as protected as its pages.
* One entry URL (`/p/your-slug`); visitors click through the internal links.
* [Analytics](/guides/analytics) and [version history](/guides/version-history) work
across the bundle (version history covers the HTML; assets are not versioned).
## Limits
* Up to **60 HTML files** and **60 assets** per deck
* **2 MB** per HTML file, **5 MB** per asset
* **12 MB** total per deck (HTML + assets combined)