Help · Media safety

Import images into an OpenWiki document safely

A useful screenshot or photo can carry invisible metadata that does not belong in a shared artifact. The media command creates a new package-local image before it is referenced by the draft.

Updated August 3, 2026Product documentation

Import a source photo

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

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

Add the package-local asset

Use ow a2ui draft media to connect the sanitized file to a sourced, responsive presentation node. Run its live --help for the current argument contract.

ow a2ui draft media --help

Write useful alternative text

  1. Describe the information the image contributes.
  2. Do not repeat the caption word for word.
  3. Avoid filename-only or decorative alt text for functional screenshots.
  4. Keep secrets and personal data out of the pixels as well as the metadata.

Validate the complete package

ow a2ui draft check ./artifact
ow a2ui draft build ./artifact
Product boundary

Metadata stripping does not prove that the visible image is safe to publish. Inspect the pixels and source rights separately.

FAQ

Frequently asked questions

Which image formats can ow media import?

The current command accepts JPEG, PNG, and WebP input and writes JPEG, PNG, or WebP according to the output extension.

Does removing EXIF remove visible secrets from a screenshot?

No. Metadata removal does not redact text or UI visible in the pixels. Review the image itself before publishing.

Use the real workflow

Publish what your agent creates.

Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.