FAQ
Frequently Asked Questions
Quick answers for creators, collectors, and teams who need a clear understanding of what PixlKey does, what it produces, and how verification-ready outputs fit into real-world sharing and licensing.
General
What PixlKey is, what it isn’t, and what “provenance-ready outputs” means in practice.
Artists
Watermarking, metadata, licensing artefacts, and how to share derivatives while keeping originals private.
Collectors
What to ask for, what to keep, and how to validate a work using PixlKey identifiers and artefacts.
Organisations
For studios, agencies, and teams: repeatable outputs, internal workflows, and “who gets what” deliverables.
Common questions (fast answers)
- Does PixlKey prevent theft? No — it’s not DRM. It helps your work carry attribution, licensing context, and verification artefacts.
- What files do I share publicly? Typically derivatives (preview/social sizes) with visible attribution/QR, while originals stay private.
- What does PixlKey generate? Consistent exports: watermarked images, metadata-embedded derivatives, licensing/certificate artefacts, and identifiers.
- Who is PixlKey for? Artists, photographers, studios, print partners, and collectors who need a repeatable provenance trail.
- Can collectors verify later? That’s the idea — verification flows use PixlKey identifiers and the artefacts produced during processing.
- Is the public site the app? No — the site explains the workflow; the app is the secure workspace for processing and account actions.
Still not seeing your scenario? Send it our way and we’ll point you to the right answer (or add it to the FAQ). Contact us.