Skip to main content

Media and binary

Binary data (images, audio, video) can come from online Data, local Data, base64 in Resources, or a path picked with FilePicker.

Media

AutoPlay may be blocked by browser policy; playback may need a user interaction first.

Image

Binary resources

Binary under Resources is a base64 literal:
The binding yields { Url, Base64, Mime, Size }. Url is a Blob URL generated at runtime and released when the widget unmounts.

FilePicker

Lets the user pick a local file and writes the path into {Inputs.<Name>}:
  • Filter is a comma-separated list of extensions.
  • The result is a path, not binary content; to play it, read it with Data Source="File" or handle it in a script.
  • The browser debug environment has no native file paths; the Tauri desktop environment may be required.

Local path rules

  • Absolute paths are used as-is;
  • Relative paths are based on the widget file directory (local import) or the launcher data directory (URL import);
  • Binary file limit 8MB;
  • The editor information panel shows the resolved absolute path.

Example: local music card

Data’s Path is currently a static string and cannot be bound to {Inputs.TrackPath}; Media.Volume is also only read at load time and has no two-way binding. For “pick a file then play it / change the volume immediately”, wait for a later version or implement it through a plugin API/command action.

Limits

  • Static image/media domains also need confirmation in the editor.
  • Online binary 8MB, local binary 8MB; larger files raise an error.
  • Blob URLs are only valid for the current widget instance; do not write them into persisted data.