PixlKey
Documentation & Information — The App Does the Work

How it works

From artwork to artefacts — end to end

PixlKey turns a single upload into a consistent set of outputs: watermarked derivatives, embedded metadata, licence/certificate artefacts, and identifiers you can use later to support verification and provenance checks.


1) Register the work

Capture the essentials (creator, title, notes, edition context) so the processing run has a clear record to bind to.

2) Configure protection

Choose watermark intent and placement. If enabled, add a QR overlay that points back to verification or record details.

3) Embed metadata

PixlKey embeds attribution and licensing-related metadata into the derivative outputs so the work carries context beyond the caption.

4) Generate identifiers

Create fingerprints/identifiers tied to the processed outputs — designed to support later validation and provenance checks.

5) Export a clean bundle

Export what you actually need: a signed master where applicable, previews, social-ready sizes, and supporting artefacts.

6) Share derivatives, keep originals private

The practical approach: distribute what you intend to be public, and let PixlKey outputs act as the paper trail layer.

What comes out of a PixlKey run

A typical run produces a distribution-ready set: watermarked images (optionally with QR), metadata-embedded derivatives, and licence/certificate-style artefacts — plus identifiers intended for future verification workflows.

Note: PixlKey can’t prevent misuse — it strengthens attribution and provenance by producing consistent, repeatable outputs that are easier to reference, verify, and explain.