A new name · MetaScope is becoming Parergon Read more
Parergon Copyright · IPTC · Templates
Stock submissions, client deliveries and archives all expect the same IPTC copyright, creator and credit on every image. Parergon saves your rights as a reusable profile and applies it to a whole shoot in one action, written straight into the files.
The problem
Typing copyright into files one at a time does not scale, and small differences between images (a missing credit line, an inconsistent notice) cause real problems downstream. You want the same rights on every file, correct to the standard.
01 · Build it once
Enter your Copyright Notice, Creator, Credit Line and Usage Terms once and save them as a profile. Dynamic tokens (such as the capture year) keep a notice current without editing it every time.
02 · Apply to the whole shoot
Select the full set and apply the profile once. Parergon shows exactly how many files will be updated, then writes the same rights block into every one, so nothing is left half-tagged.
See the step by step →
03 · Keep it consistent
Transformation rules build a credit line from the creator, or copy the copyright notice into the credit field, so the same logic runs on every import. Controlled vocabularies keep the wording identical from file to file.
About transformation rules →
| Field | Before | After |
|---|---|---|
| IPTC:CopyrightNotice | (empty) | © 2026 Your Studio |
| IPTC:Creator | (empty) | Your Name |
| IPTC:CreditLine | (empty) | Your Studio |
| XMP:UsageTerms | (empty) | All rights reserved |
| Image pixels | Original | Unchanged |
Good to know
Questions
Yes. Parergon writes the IPTC and XMP rights fields that stock agencies, clients and digital asset managers expect, including Copyright Notice, Creator, Credit Line and Usage Terms.
You decide. A profile only sets the fields you put in it, so you can add a credit line without touching other metadata, or replace the full rights block across a selection.
Copyright Notice, Creator, Credit Line, Usage Terms, Web Statement of Rights and contact fields, among others. You can also keep them consistent across files with controlled vocabularies and transformation rules.
No. Parergon writes the rights metadata in place. The pixels are not re-encoded, so quality is identical to the original.
