`video` element

A video file with optional poster and controls.

Renders

<video>

Required

source (or binds.source).

Native apps

Web, and server-driven native apps

Syntax

video element

{ "type": "video" }

An element lives in a screen's sections, another element's elements, a layout slot or a component root.

Properties

Property	Type	Description
`source`	`string`	image/video/audio/svg URL or assets path
`poster`	`string`
`muted`	`boolean`
`controls`	`boolean`
`fit`	`"cover""contain""fill""none"`
`autoplay`	`boolean`
`loop`	`boolean`

Plus the properties every element accepts: id, className, style, responsive, states, animation, visible, ariaLabel, attributes and more.

Example

video example

{
  "type": "video",
  "source": "/assets/workshop.mp4",
  "poster": "/assets/lamp.svg",
  "controls": true,
  "muted": true
}

autoplay also mutes, as browsers require. For adaptive (HLS) streaming use the @iwc/video-player widget.

Expected output

The HTML IWC rendered for the example above (inside the page's content wrapper). Class names such as i807b63fc are generated per element for its scoped CSS.

Rendered HTML

<div class="iwc-page ipage" id="iwc-content">
  <video class="iwc-video i2e0fe33a" src="/assets/workshop.mp4" poster="/assets/lamp.svg" muted controls playsinline preload="metadata">
  </video>
</div>

Data, conditions & styling

Conditional rendering: "visible": {"auth": "signed-in"}, {"roles": ["admin"]} or an expression such as "=product.stock > 0". Decided on the server: hidden elements are never sent.
Data binding: bind takes text from data (name, user.name, props.title, params.slug, state.cart.count); binds binds attributes. Containers become data-driven with data + item. See data binding.
Styling: className for your stylesheets, style for CSS in JSON, states for hover/focus/active, animation for entrance motion. See the style property reference.
Responsive behaviour: responsive applies CSS at or below a breakpoint ({"mobile": {"padding": "12px"}}); grids also take responsiveColumns.