Repository navigation
3. Metadata Support
Image MetaHub indexes media files and extracts generation metadata when available.
Metadata support depends on what the original generator saved into the file.
- PNG
- JPG
- JPEG
- WEBP
- GIF
- MP4
- WEBM
- MKV
- MOV
- AVI
- MP3
- WAV
- FLAC
- OGG
- OGA
- M4A
- AAC
- OPUS
- AIFF
- AIF
- WMA
For video and audio, Image MetaHub can use container metadata and ffprobe when available to extract information such as duration, codec, frame count, resolution, sample rate, channels, and bit rate.
Audio files can still be indexed even when Chromium/Electron cannot play a specific codec.
Image MetaHub can read metadata from:
- Stable Diffusion / Automatic1111
- ComfyUI
- InvokeAI
- SD.Next
- Forge
- Fooocus
- SwarmUI
- Draw Things
- Midjourney / Niji Journey
- Other tools that embed generation parameters into PNG, JPEG, WebP, sidecar, EXIF, XMP, comment, or JSON-like payloads
Different generators save metadata in different formats.
Image MetaHub attempts to normalize useful fields such as:
- Prompt
- Negative prompt
- Model/checkpoint
- LoRAs/resources
- Seed
- Steps
- CFG scale
- Sampler
- Scheduler
- Width
- Height
- Batch size
- Generation mode
- Source image information
- Denoise strength
- Telemetry
- Workflow data
The viewer can also show raw metadata.
Raw metadata is useful for debugging, parser improvements, and checking fields that were not normalized.
ComfyUI support includes embedded workflow and prompt graph parsing.
Image MetaHub can inspect:
- Workflow graphs
- Prompt graphs
- Node types
- Node inputs
- LoRAs
- Models
- Samplers
- Schedulers
- Source image links
- Workflow-native regeneration data
The best ComfyUI experience comes from using the MetaHub Save Node.
The companion ComfyUI node is available here:
https://github.com/LuqP2/ImageMetaHub-ComfyUI-Save
It helps Image MetaHub ingest:
- Full workflow payloads
- Prompt payloads
- Tags and notes saved by the workflow
- GPU and timing analytics
- Verified telemetry
- Explicit lineage metadata
- Better future-proof parsing
Images generated without the Save Node can still be parsed when useful metadata is embedded, but the Save Node gives the most complete result.
Images created with compatible MetaHub Save Node workflows can include verified telemetry.
Verified telemetry can power filters and analytics such as:
- Generation time
- GPU/device information
- Performance comparisons
- Speed and VRAM-related summaries
- Telemetry coverage
Image MetaHub can detect transformation workflows such as:
- img2img
- inpaint
- outpaint
When possible, the viewer shows the source image, generation type, denoise context, and derived image relationships.
If the source image cannot be recovered with confidence, Image MetaHub should show that clearly instead of implying a weak match.