Documentation
Learn the workflow. Know the outputs.
PixlKey is built as a repeatable processing pipeline: watermarking, metadata embedding, licensing artefacts, and verification-ready identifiers. This hub is your “why” and “how” — the concepts behind the buttons.
Watermarking
How PixlKey applies visible attribution and optional QR overlays, and why derivatives (not originals) are the safest thing to share publicly.
Metadata
What gets embedded, where it lives, and how metadata supports attribution, licensing context, and long-term provenance hygiene.
Licensing
A practical overview of attaching licence terms to a specific work and generating certificate-style artefacts for collectors, clients, or your own archive.
Verification
How PixlKey outputs identifiers and fingerprints you can use later to validate a file’s relationship to a registered work and its intended distribution trail.
Glossary
Short definitions for PixlKey terms (artefacts, derivatives, identifiers, provenance) so you can read the docs without decoding them.
Recommended reading order
If you’re new to PixlKey: start with Watermarking, then Metadata, then Licensing, and finish with Verification.
Practical rule: treat the app as your workshop. Share the derivatives you intended to distribute, and keep originals private. PixlKey’s job is to keep the receipts attached.