Media blocks
Media blocks put pictures and video on the page — a single photo, a gallery, an embedded video, a before/after slider. They pull from your Media Library.
The blocks
| Block | What it puts on the page |
|---|---|
Image | A single image. The workhorse of most storefronts. |
Avatar | A small circular image, for a person — an author, an instructor, a testimonial face. |
VideoEmbedRoot | A video from an external host, embedded in the page. |
ImageGalleryRoot | A group of images shown together as a gallery. Add the images inside it. |
VideoGalleryRoot | Several videos shown together. |
BeforeAfterRoot | Two images with a slider between them. Made for transformations — the strongest proof you can show for a service. |
Marquee | A row of content that scrolls sideways continuously. Eye-catching; tiring if the page has more than one. |
Icon | A single icon, for a feature list or to sit beside a heading. |
What happens — and what doesn't
- Media blocks use files from your Media Library — upload once, place anywhere.
- Image blocks have aspect-ratio and fit controls in the inspector, so a photo crops the way you want.
- Some blocks come in a "Root" plus item form (a gallery root holds images) — that's how the builder nests a collection inside a container.
- A secure media file never displays on a pre-payment page; access follows entitlement.
Where do the images in a media block come from?
From your Media Library. Upload a file once and place it in any image, gallery, or video block across your store.
Why do some media blocks have a 'Root' version?
A Root block is the container that holds a set of items — a gallery Root holds image items, for example. It's how the builder groups a collection inside one block.
What this screen looks like in every state
| State | When you'll see it | What you see, and what to do |
|---|---|---|
| Empty | You haven't created anything here yet | “No pages found” — with a shortcut to create the first one. Nothing is wrong; there's just nothing to show yet. |
| Loading | The screen is fetching your data | A skeleton in the shape of the finished page. It should be brief — if it persists, the load has failed rather than stalled. |
| Error | The data couldn't be loaded | A message with a retry. Retry first: most of these are a dropped request, not a broken store. If it repeats, the outage is upstream and reloading won't help. |
| No access | Your role doesn't include this screen | A permission notice instead of the page. An owner or admin can grant access under Settings → Team. |
When something goes wrong
These are the messages this screen can show you, and what each one means.
| If you see | What to do |
|---|---|
| "…" is reserved for a built-in store page (like cart or checkout). Choose a different slug. | Retry the action. If it keeps happening, contact support with what you were doing. |
| Cannot delete the shop page. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |
| Delete the product to remove this page. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |
| Page title is required. | A required field is blank. Fill it in and save again. |
| This page is protected and cannot be deleted. | The change didn't save. Retry — if it keeps failing, the request isn't reaching the server. |