OWL Compose

Help · Media safety

Import images into an OWL Compose document safely

A screenshot or photo can expose invisible metadata and visible secrets. Sanitize the file, record provenance, and inspect the pixels separately.

Mis à jour September 5, 2026Documentation produitOWL Compose CLI 0.1.3 and laterOWL Compose Product

Create a sanitized package-local file

The output extension selects JPEG, PNG, or WebP. Import decodes orientation and removes EXIF, GPS, XMP, and comments during re-encoding.

ow media import ./source-photo.jpg --output ./artifact/assets/overview.webp

Reference the new asset

Use a relative package-local path and useful alternative text. Keep source, publisher, rights, retrieval date, digest, caption, and credit in the evidence record.

<ow-media id="overview" file="./assets/overview.webp" alt="Describe the information the image contributes" />

Inspect what metadata removal cannot fix

  1. Crop or redact visible credentials and personal data.
  2. Confirm the image is licensed for the intended use.
  3. Check that the caption does not overstate what the image proves.
  4. Make the surrounding document understandable if the image fails to load.

Validate the complete source tree

ow a2ui check ./artifact/document.owx
ow a2ui compile ./artifact/document.owx --output ./artifact/document.json
Limite du produit

Metadata stripping does not make the visible pixels, source rights, or factual interpretation safe by itself.

FAQ

Questions fréquentes

Which formats are supported?

The current media import accepts JPEG, PNG, and WebP input and writes one of those formats according to the output extension.

Does metadata removal redact a token visible in a screenshot?

No. Visible pixels are unchanged. Redact the source image before importing it.

Utiliser le vrai workflow

Publiez ce que votre Agent crée.

Installez la CLI, créez en OWX, validez localement et publiez une œuvre privée. Créez un lien lecteur uniquement au moment de la partager.

Installer OWL ComposeSe connecter