The codec the export would use right now.
The RFC string the export would actually ENCODE with right now: the user-forced string when it
is supported, otherwise the first supported rung of the built-in ladder (the same fallback the
export worker performs, with a warning). null when nothing is supported.
Whether the WebCodecs encoding path can produce an alpha channel. Always false: VideoEncoder
has no alpha support (the spec option was never implemented), so transparent output is only
available through the software encoder path (useWebCodecsVideoEncoder: false, VP8/VP9 webm).
Per-codec support across every codec the pipeline knows (h264, vp8, vp9).
Dry-run outcome — null unless requested via ExportSupportProbeOptions.dryRun.
true when a forced RFC string was set but is unsupported — the export would fall back to the ladder with a warning.
The user-forced RFC string from settings, if any (may differ from activeCodecRFCString when it is unsupported and fell back).
The export configuration the probe ran against.
Whether an export would succeed with the CURRENT configuration (active codec incl. any forced RFC string, probed size/framerate/bitrate) — including the encoder's runtime fallback ladder (bitrate-mode swap and hardware-acceleration downgrades), so this mirrors what the export pipeline would actually conclude. When a dry run was requested, this reflects its outcome.
Whether the WebCodecs VideoEncoder API exists in this environment.
Full export-capability report for the WebCodecs encoding path.