Documentation
Metadata
PixlKey treats metadata as part of the deliverable — not an afterthought. When you process a piece, PixlKey helps you attach creator and licence context to the exports you actually share, so the work carries its identity and intent as it moves.
What PixlKey captures
Metadata starts with creator-provided fields — the human truth of the work — and is carried forward into derivative outputs intended for distribution.
- Creator/artist identity and attribution details
- Title, edition/variant notes, and descriptive fields
- Licensing context (what’s allowed, what’s not)
- Processing context needed for verification workflows
Where metadata appears
PixlKey is designed so you can keep originals private and share derivatives confidently. Metadata is applied where it matters: the outputs you hand to the world.
- Signed/distribution-ready exports
- Preview and social-ready derivatives
- Licence/certificate artefacts generated alongside the work
- Verification identifiers used later to validate provenance
Why it matters
Metadata doesn’t prevent misuse — but it strengthens the “receipts”. The goal is a consistent, repeatable record that travels with the work and supports later proof.
- Clear attribution after reposting or redistribution
- Licence clarity for buyers, clients, and collaborators
- Audit-friendly outputs for later dispute or verification
- Better continuity across versions, sizes, and platforms
Recommended workflow
- Enter the creator/title/licence essentials before processing.
- Process the file to generate your signed master and shareable derivatives.
- Export only what you intend to distribute (keep originals private where possible).
- Verify later using PixlKey identifiers and provenance artefacts.
Practical tip: treat metadata like labelling a specimen — do it once, do it consistently, and let the label follow every derivative you share.