> For the complete documentation index, see [llms.txt](https://docs.overflowcms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overflowcms.com/webflow-integration/images-and-media.md).

# Images & Media

## Images & Media

### Uploading

Image fields upload directly from the item editor to Cloudflare Images (a direct creator upload — the file goes straight from your browser to Cloudflare, not through OverflowCMS's own servers). You can also paste an external image URL instead, if you'd rather not upload.

### What actually gets stored

An image (or video) field's value is a small object, not a bare URL:

```json
{
  "mediaId": "...",
  "url": "https://imagedelivery.net/.../w=1280,fit=scale-down",
  "srcset": "...1280w, ...960w, ...640w",
  "alt": "...",
  "width": 1280,
  "height": 720
}
```

This is baked in at authoring time — content-api serves it verbatim, it doesn't compute anything at read time. `srcset` is generated across five widths (320/640/960/1280/1920) as `w=<n>,fit=scale-down` Cloudflare Images delivery URLs.

### How the embed script uses it

Bind it to a real `<img>` element:

```html
<img data-oc-field="cover" alt="" />
```

The script sets `src`, `srcset`, and `alt` from the stored object, and adds `sizes="100vw"` automatically if a width-descriptor srcset is present and you haven't set your own `sizes` attribute. Binding an image field to a non-`<img>` element (a `<div>`, say) sets nothing — only real `HTMLImageElement`s get `src`/`srcset`/`alt` written.

### Plan tiers

Basic media CDN is included on every paid plan; **full media CDN** (the complete srcset set + on-the-fly transforms) requires Pro or above — see Plans & Billing.

### Video

Video fields exist in the field-type registry (Pro+) and store the same MediaRef shape, but ingestion is currently URL-based rather than a direct-upload pipeline into Cloudflare Stream — adaptive streaming via Stream is on the roadmap, not yet wired end-to-end.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.overflowcms.com/webflow-integration/images-and-media.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.