The IPTC standard separates who made an image from how that image should be credited when published, and the distinction is more than academic. The Creator field (also called By-line) names the actual individual \u2014 the photographer or, for text, the writer \u2014 and By-line Title can record their role, such as “Staff Photographer” or “Freelance Contributor.” Credit Line, by contrast, is the exact string a publisher displays, which might combine the individual’s name with an agency or publication name in a specific format the license requires, and doesn’t necessarily match the Creator field verbatim.<\/p>
Creator identifies who made the image. Credit Line specifies how it should be attributed when published. A DAM that conflates the two loses one function to save the other.<\/p><\/blockquote>
A DAM that treats these as one interchangeable attribution field breaks two separate downstream processes. Contributor-level reporting \u2014 figuring out how many images a specific freelance photographer has in the library, for payment reconciliation or usage tracking \u2014 depends on the Creator field being populated correctly and consistently, since that’s what such reports are built to query. Meanwhile, published attribution depends on Credit Line matching whatever string the licensing agreement actually requires, which sometimes differs from the photographer’s name alone. Populating only one of the two fields, even with technically correct information, quietly breaks whichever process depends on the field that was left empty.<\/p>","protected":false},"excerpt":{"rendered":"
Byline metadata is the IPTC Creator (By-line) and By-line Title fields identifying who made an image or wrote a story, distinct from the Credit Line, which records the crediting organization or attribution string.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Is the Creator field the same as the Credit Line field?","answer":"No \u2014 Creator identifies the individual who made the image, while Credit Line is the specific attribution string a publisher displays, which can combine the creator's name with an agency or organization name in a format the license requires."},{"question":"Why does By-line Title matter separately from the Creator's name?","answer":"By-line Title records the creator's role or job position, not just their name \u2014 for example \"Staff Photographer,\" \"Contributing Photographer,\" or \"Freelance.\" This matters because it signals the creator's employment or contractual relationship with the publication, which affects how an asset can be licensed and reused. Staff and freelance work often carry different rights and payment terms, so licensing and payment workflows read By-line Title alongside Creator to apply the correct terms for that status."},{"question":"What breaks if only the Credit Line is populated and Creator is left blank?","answer":"Any workflow that searches or reports by individual contributor \u2014 such as a freelance payment reconciliation or a \"find all images by this photographer\" search \u2014 fails to surface those assets, since it queries the Creator field specifically."},{"question":"Does byline metadata apply to written articles as well as photos?","answer":"Yes \u2014 the same Creator\/By-line concept applies to written content, identifying the author, though the specific field names and standards used can differ between a photo metadata system and a CMS or article management system."},{"question":"Can a single image have multiple people credited in the Creator field?","answer":"The IPTC standard supports multiple creator entries where more than one person contributed (for example, a photographer and a separate photo editor), though most systems primarily populate it with the principal photographer."},{"question":"Should Creator be locked from editing once an image is ingested?","answer":"It's generally good practice to restrict who can edit the Creator field after ingest, since an incorrect change could misattribute the work and break both payment tracking and moral-rights attribution for the original photographer."}],"checked_date":"2026-08-11","sources":[{"statement":"The Creator field holds the name of the photographer, and this is distinct from the Credit Line field, which specifies the exact attribution text a publisher should display.","source_name":"LegalClarity, \"IPTC Photo Metadata Standard: Attribution and Rights\"","url":"https:\/\/legalclarity.org\/iptc-photo-metadata-standard-attribution-and-rights\/","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"Byline metadata: IPTC Creator fields vs the credit line","seo_description":"","noindex":false,"related":[],"definition":"Byline metadata is the IPTC Creator (By-line) and By-line Title fields identifying who made an image or wrote a story, distinct from the Credit Line, which records the crediting organization or attribution string.","why":"Byline and credit line are frequently conflated into one free-text field, but they serve different functions: Creator identifies the individual photographer or writer \u2014 needed for contributor payment tracking and correct moral-rights attribution \u2014 while Credit Line is the specific string a publisher is contractually required to display. A DAM that only populates one of the two loses the ability to correctly generate freelance payment reports or to correctly attribute a republished image per whatever the original wire service or license actually requires.","example_rows":[{"field":"Creator (By-line)","values":"Jane Doe"},{"field":"By-line Title","values":"Staff Photographer"},{"field":"Credit Line","values":"Jane Doe\/AP"},{"field":"Used for","values":"Creator \u2192 contributor search\/payment; Credit Line \u2192 published attribution"}],"mistake":"An ingest workflow maps a photographer's name only into the Credit Line field and leaves Creator blank, so any contributor-payment report or photographer-level search \u2014 both of which typically query the Creator field specifically \u2014 misses those assets entirely even though the name is technically present somewhere in the metadata.","deep_link":""},"silo":[24],"class_list":["post-3032","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/3032","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/glossary"}],"version-history":[{"count":1,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/3032\/revisions"}],"predecessor-version":[{"id":3369,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/3032\/revisions\/3369"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=3032"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=3032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}