Why Luxii
What IPTC/XMP Metadata Actually Is — and Why Luxii Beats Typing It In by Hand
If you've ever checked Lightroom's “Export IPTC as XMP” box and still gotten a photo with no title, no caption, and no keywords, you're not imagining it — that checkbox doesn't do what most people think it does. This page covers what IPTC, XMP, and EXIF metadata actually are, why a normal Lightroom export leaves the descriptive fields blank, and an honest comparison of typing that metadata in by hand versus letting Luxii write it — including where hand-typing is still the right call.
The root confusion
IPTC vs. XMP vs. EXIF: What Your Metadata Actually Is
“Metadata” gets talked about like it's one thing. It isn't — a photo file carries at least three separate kinds, written by different tools for entirely different reasons, and mixing them up is the single most common reason photographers think a photo is tagged when the fields that actually matter are empty.
EXIF
Camera-written, read-only in practice. Exchangeable Image File data — shutter speed, aperture, ISO, lens, focal length, date/time, sometimes GPS — gets embedded automatically by the camera the instant you press the shutter. You never type it, and neither does Lightroom; it's already there before the file hits your memory card. It's technical, not descriptive — nothing in EXIF says what the photo is of.
IPTC
The older descriptive-field standard. Named for the International Press Telecommunications Council, which defined it in the 1990s for photojournalism and wire services: title, headline, caption, keywords, creator, copyright, location — fields built to answer what a photo is of, who made it, and how someone would search for it. IPTC is a vocabulary — a list of field names and meanings — not a file format on its own.
XMP
Adobe's modern container for it. The Extensible Metadata Platform is the XML-based structure that actually holds IPTC's fields (and others) inside a file, or a sidecar .xmp file next to a RAW, so Lightroom, Photoshop, and other applications can read and write the same values consistently. XMP is the delivery mechanism; IPTC is most of what's riding inside it.
This is where Lightroom's Export dialog checkbox comes in: “Include: Export IPTC as XMP.” All it does is tell Lightroom to write whatever is currently sitting in your catalog's IPTC fields — title, caption, keywords, and the rest — into the exported file's XMP data. That's the entire job. It has no generative ability of its own: it doesn't look at the photo, it doesn't invent a caption, it doesn't suggest keywords. If Title and Caption are empty in your catalog, checking that box exports a photo with an empty Title and Caption, because there was nothing there to export in the first place. That's the confusion the rest of this page is built around — “Export IPTC as XMP” sounds like a metadata feature, and it is one, but it's a plumbing setting, not a content generator.
The gap
Why Lightroom Exports Leave You With Blank Metadata
Lightroom Classic has no built-in way to generate a title, caption, alt text, or keyword list from what's actually in the frame. There's no vision model running in the Library module, no auto-captioning — nothing that looks at a photo of a bride and groom on a beach and writes a real caption into the Caption field. What Lightroom gives you instead is a text box — the Keywording panel, the IPTC section of the Metadata panel — and the expectation that you'll type into it yourself, one photo at a time, or copy one photo's metadata across a marked selection with Sync Metadata, which copies the same wording onto every photo in that selection whether it fits or not.
Meanwhile, EXIF is writing itself the entire time, silently, with zero input from you. Every export carries shutter speed, lens, and date — real data, sitting right there in the file — which is exactly why so many photographers assume their metadata is “fine.” It's not that they're wrong that data exists; it's that EXIF and IPTC answer completely different questions, and the one people actually care about — what Google, a screen reader, or a stock platform reads to know what the photo is of — was never filled in.
This isn't a knock on Lightroom. It was built as a catalog and develop tool, and hand-typing five descriptive fields per photo, at scale, across every shoot, was never going to be something Adobe solved inside the core app — it's a real enough gap that a small category of Lightroom plugins, Luxii included, exists specifically to close it.
The honest version
Manual Tagging vs. Luxii: An Honest Comparison
Typing metadata by hand isn't wrong — it's just slow, and it gets worse exactly when you can least afford it: at real shoot volume. Here's a specific comparison, using the same example we use everywhere on this site — a 500-photo wedding gallery — because round, invented numbers don't help anyone decide anything.
| Manual tagging | Luxii | |
|---|---|---|
| Time cost (a 500-photo wedding gallery) | Typing a title, caption, and keyword list by hand across 500 photos — even at a disciplined 30–45 seconds per photo — runs 4 to 6+ hours. Most photographers never actually do it; they do keywords only, or skip it. | Select the folder, run Tag Selected Photos once. 500 credits, a few minutes of processing, zero hands-on typing. |
| Consistency across the catalog | Wording quality drops as fatigue sets in — captions get shorter, keywords get repetitive, some photos get skipped outright once patience runs out. | Every photo gets the same five-field treatment, generated fresh from what's actually in that frame — photo 1 and photo 500 get equal attention. |
| Full five-field coverage | Realistically: keywords, maybe. Title and headline are usually the first things skipped, and Alt Text — even where the field exists — is rarely typed at all. | Title, headline, caption, alt text, and keywords, written together in the same call, every time. |
| Survives re-export | Yes — as long as it was actually typed into the catalog in the first place. “As long as” is doing most of the work in that sentence. | Yes. It's written into the catalog the same way anything you type is, so every future export carries it. |
None of this means manual entry is wrong. For a handful of portfolio hero shots — a dozen images you've hand-picked for a homepage or a print, where you want to spend real, specific attention on each one — typing it yourself is genuinely the better call; there's no volume to fight and the extra care shows. Where it breaks down is volume: a full wedding gallery, a multi-day event, a stock submission batch, a real-estate shoot with dozens of listings a week, or any gallery running into the hundreds of images. That's the line — not photo quality, not subject matter, just how many photos are waiting for five fields each.
Who Luxii Is For (and Who It Isn't)
Luxii earns its keep at volume: wedding and event photographers delivering hundreds of images per shoot, stock contributors submitting in batches, real estate photographers turning around listings weekly — anyone regularly handing over more photos than they have time to hand-type five metadata fields into, one at a time. If that's not your workflow — you're an occasional hobbyist with a handful of vacation shots, or a portfolio with two dozen hero images you already enjoy captioning yourself — Luxii probably isn't worth the credits. Hand-typing a dozen photos well beats running software to save yourself fifteen minutes.
Not a competitor — a different job
Luxii vs. Other Lightroom Classic Plugins
Luxii isn't the only Lightroom Classic plugin that touches AI, and it's worth being specific about where it sits, because most of what gets called “a Lightroom AI plugin” solves a different problem entirely.
Tools like Excire Search and Excire Foto are built for finding and organizing what you already have — AI-powered search across your own catalog by subject, face recognition, similarity matching, keyword suggestions to speed up your own culling and sorting. That's a real, useful job, and it's aimed inward: helping you locate a photo inside your own Lightroom catalog faster.
Luxii is aimed outward. It doesn't help you find your own photos — it writes standardized IPTC/XMP metadata (title, headline, caption, alt text, keywords) directly into the file, so systems outside Lightroom entirely — Google Images, a client's browser, a stock platform's search, a screen reader — can read what the photo is of once it leaves your catalog. Different input, different output, different job.
That also means they're not competing tools. A photographer could reasonably run a culling/search plugin first to pick the keepers out of a shoot, then run Luxii on that final selection to write the outward-facing metadata before delivery or export — the two slot together rather than against each other.
Among the smaller category of plugins that do write outward-facing metadata specifically, the differences are mostly about field coverage: in Luxii's own June 2026 comparison of every Lightroom AI metadata plugin it could find — MetaMagic, LrGenius, LrTag, PhotoTag.ai, PhotoKeyworder, Excire, AnyVision — none of them wrote a headline field, and none wrote alt text. Luxii writes both, alongside title, caption, and keywords, in the same single call.
At submission scale
Why This Matters More at Stock-Submission Scale
Everything above matters more, not less, once photos are headed to a stock platform. Stock reviewers and search algorithms weight keyword and title completeness directly — a submission with a thin, generic, or missing keyword list reads as low-effort at review, and even once accepted, it won't surface in buyer search results that are matched against exactly those keywords. A technically strong photo with an empty title field is functionally invisible in that search, regardless of how good the photo actually is.
The part that trips people up: stock platforms, like Google Images and Flickr, read the metadata embedded in the file itself — the IPTC/XMP fields riding inside it — not a separate database entry inside some other app. That's an important distinction from AI vision tools that only display tags in their own interface: if the words never get written into the file's actual metadata layer, they don't travel with the photo when it's uploaded anywhere else. They stay trapped in the app that generated them.
Luxii writes directly into the catalog's real IPTC/XMP fields — the same fields any export carries — so the keywords, title, and caption a stock platform (or Google, or Flickr) reads are the same ones sitting in the file, not a second, disconnected set living somewhere else. At submission volume, that's the difference between a keyword list that actually does its job and one that never left your hard drive.
Luxii is a $39 one-time license with 500 credits included — never a subscription.
See the full pricing breakdownLuxii only ever writes metadata — it never touches Develop, crop, ratings, or flags.
Full list on FeaturesFAQ
Questions about metadata and Luxii
What's the difference between IPTC, XMP, and EXIF?+
They're three different things people lump together as one “metadata.” EXIF is technical data your camera writes automatically — shutter speed, aperture, ISO, lens, date/time — and it writes itself whether you touch it or not. IPTC is the older descriptive-field standard: title, headline, caption, keywords, creator, copyright — the fields that actually say what a photo is of and who made it. XMP is Adobe's modern container that holds IPTC's fields (and others) inside a file or a sidecar, so different applications can read and write the same data consistently. Short version: EXIF describes the camera, IPTC describes the photo, and XMP is how IPTC's fields actually get stored.
What does Lightroom's “Export IPTC as XMP” checkbox actually do?+
It tells Lightroom to write whatever is already sitting in your catalog's IPTC fields — title, caption, keywords, and the rest — into the exported file as XMP data. That's the entire job. It has no generative ability: if those fields are empty in the catalog, checking the box exports a photo with empty fields, because there was nothing there to export. It's a serialization setting, not a metadata generator, even though it's easy to mistake it for one.
My Lightroom export still has no metadata. Why?+
Because nothing was ever typed into the IPTC fields to begin with. Lightroom Classic doesn't generate a title, caption, alt text, or keyword list from what's actually in the frame — it gives you blank text fields and leaves the writing to you. Meanwhile EXIF data writes itself silently at capture, so an export can look like it “has metadata” at a glance while the descriptive fields Google, screen readers, and stock platforms actually read were never filled in.
Is Luxii a replacement for Lightroom's own Keywording/Metadata panel?+
It fills the same panels you already use — Luxii writes directly into Lightroom's own Keywording and IPTC/Metadata fields, so there's nothing new to learn or manage.
See the five fields Luxii writes on FeaturesHow is Luxii different from Excire or other Lightroom AI tools?+
Differently, on purpose. Excire and similar tools are built for finding and culling — AI-powered search across your own catalog, face recognition, similarity matching. Luxii doesn't help you find your own photos; it writes standardized IPTC/XMP metadata into the file so things outside Lightroom — Google, a stock platform, a client's browser — can read it. They're not competing: a lot of photographers could reasonably cull with one and tag the keepers with the other.
Is manual metadata entry in Lightroom good enough?+
For a handful of portfolio hero shots — a dozen images you're hand-picking and want to spend real attention on — yes, typing it yourself is genuinely fine. It breaks down at volume: a full wedding gallery, an event shoot, a stock submission batch, anything running into the hundreds of images. That's where consistency drops, fields get skipped, and the time cost turns into hours nobody actually has.
Does Luxii edit or retouch my photos?+
No — Luxii only writes metadata. It never touches Develop, crop, ratings, or flags.
Full list of what Luxii doesn't do