Rename, copyright, geo, keywords, rating, title. Six metadata fields, applied before Lightroom opens. Locally on your laptop. No AI, ever.
Tag a full shoot in seconds. Rename, copyright, geo, keywords, rating, and title applied in one pass.
From card ingest to web-ready delivery. Never leave the browser, never upload a file. Click any step for details.
Wedding pros, stock contributors, wildlife and travel shooters. Different workflows, same six-field metadata pass.
Your first ten keywords do most of the selling. Jade GT holds the order you build and writes one clean IPTC every platform reads. Less keyboard, more viewfinder.
Type the venue and the couple once. Jade GT stamps rename, copyright, geo, keywords, rating, and title on every frame before the cull.
Run your logger. Shoot the trip. Jade GT matches GPX, corrects drift, and stamps place, date, and keywords on every frame. Findable five years out.
Turn your phone into a GPS tracker. Free forever. Record tracks locally on your phone, export as GPX. Pro users pair their phone to their desktop for instant track sync the moment the walk-through ends.
Only GPX tracks sync between paired devices. Encrypted in transit. Nothing stored on our servers.
Read metadata from 500+ formats. Full editing on the web-ready formats your clients actually see. RAW files get a hybrid strategy: XMP sidecars for full Lightroom compatibility, plus direct EXIF where it works.
Instant metadata analysis for almost any camera made. Full editing available for web-ready formats.
Every file leaves with written metadata. How it's saved on disk is your call. Pick the path that fits your workflow.
Stop pinning photos one-by-one. Drop a .gpx from your tracker. Jade GT matches every photo to its exact coordinate along the path. Camera clock off by twenty minutes? Fixed automatically.
Matches photos to your path in seconds and corrects camera clock drift. GPS data is scientifically accurate, not approximate.
Build filenames that actually mean something. Tokens pull from EXIF, your event metadata, and your schema. A wedding's 2,000 frames rename in one pass, reset sequence counter and all.
{city} {date} {index} {original} {country} {year} {month}
Convert full batches to AVIF or WebP. Up to 50% smaller files, same visual quality. All your IPTC and XMP metadata preserved through the conversion.
Encoding happens on your machine. Nothing uploaded. Client galleries load fast because the files stay small.
Getty and Adobe Stock are strict. Missing a scene code or using a trademarked word will result in a rejection and a lost sale. Jade GT audits your metadata against real agency rules as you type.
Catch missing codes and trademark risks before you hit export. Fewer rejections mean faster payouts.
Your preset handles copyright and creator. You still type venue, couples, GPS, and title. Jade GT runs all six before Lightroom opens, then saves the schema for the next wedding.
IPTC Title holds the couple, venue, and year. Search "Smith Key West" next year. Any IPTC-reading catalog finds them.
Your logger knows where. Your camera knows when. Cameras drift seconds a day, so the two disagree by trip's end. Jade GT reads both, corrects the drift across the set, and writes coordinates into every frame. No hotspot, no login, no 60 GB upload from the lodge.
Every frame carries coordinates and a corrected timestamp. Locations stay offline. Tracks stay offline. The trip stays on your laptop.
Modern cameras quietly bake GPS coordinates and unique serial numbers into every file. Sharing an unwashed photo can share your home address or identify your exact camera. Scrub it in one pass, locally, before anything goes out the door.
Instantly strip camera serials, technical logs, and private location data. 100% local. Sensitive originals never touch the web.
Your camera names files DSC_4521.CR3. Six months later, you can't find anything. Tokens let you name files by what they actually are: couple, venue, date, sequence number. Type the pattern once, and every frame in the batch follows it. Works the same whether you're naming ten files or two thousand.
Build a rename template once, save it, and reuse it on every wedding. The sequence counter resets cleanly between batches so you never overwrite a file.
Yes, if you ever want a photo to trace back to you. Social platforms strip the visible watermark, but most of them leave the copyright field alone. Stock sites read it. So do clients who right-click to check a file. Jade GT stamps your studio name, artist credit, and usage terms into every photo in the batch.
Save your studio info once. Jade GT applies it automatically on every batch going forward, so a photo found anywhere on the internet still points back to you.
For a private wedding: maybe not, and Jade GT lets you skip the couple's home address in one click. For everything else, usually yes. Lightroom's Map module only shows photos that have coordinates. Stock agencies filter submissions by city. And for your own archive five years from now, location is what you'll actually remember.
Pick whichever matches the shoot. A phone GPX for a ceremony-to-reception walk, a single pin for a studio session, or a venue name for a quick batch. City and country fields fill in automatically.
So Lightroom opens to a filterable library instead of a pile of files. Keywords let you pull up every ceremony frame, every ring detail, every dress shot without scrolling for twenty minutes. Apply your full keyword set to the whole batch at once, then let Lightroom's Smart Collections build themselves on import.
Build a set for weddings, another for engagements, another for editorial. Apply the whole set to a batch in one tap. Keywords are the difference between a searchable archive and a folder you never open again.
You can flag obvious keepers and obvious skips during the metadata pass. Five stars on your favorites. One star on frames you already know are duds. When Lightroom imports the batch, those ratings are already there, so your library filter works from the first second.
Most photographers spend their first Lightroom pass flagging rejects. Do it here instead. By the time the import finishes, the rejects are already filtered out of view.
Anything you want searchable and human-readable. Most photographers use it for the event and the couple: "Smith Wedding, Riverside Farm." The title shows up in Lightroom's grid view, on stock platforms, and in most gallery platforms' caption output. Writing it once during the batch beats typing it fifty times as you deliver.
Set the title on the batch, and every downstream tool picks it up. Your Lightroom grid shows it under the thumbnail. Your gallery platform uses it for the page caption. Your stock listing uses it as the headline.
A camera writes almost nothing into your files: the shutter-assigned filename, the exposure data, maybe GPS. Title, keywords, creator, copyright, usage terms all stay blank. That blankness is cheap at ingest and gets expensive everywhere downstream.
Six months in, you need the Chen engagement shots. Every file is DSC_####.CR3 in folders named by date. Without titles or keywords in the file itself, the only way back is memory or a spreadsheet you kept outside the catalog.
Every import turns into a setup ritual. Apply a metadata preset, run the Map module to geocode, add keywords per folder, type titles per export. Minutes compound to hours across a year of weddings.
The moment a photo is shared to Instagram, a printer, or a wedding blog, a file with no embedded © or creator travels without you. Platforms that preserve IPTC have nothing to preserve. You're attribution-less the second it leaves your hands.
Everything you skipped at ingest gets paid back, with interest, every time the file gets used.
When a file arrives at Lightroom, Capture One, Photo Mechanic, or a cloud DAM already carrying its metadata, everything downstream shifts. Today the workflow gets faster. In ten years the archive stays usable.
Lightroom reads your Title into the grid, drops GPS pins on the Map module, and merges your IPTC keywords into the Keyword tree. Automatically, at import. Client galleries pull titles as captions with zero setup. Stock submissions to Adobe Stock or Getty ship with required fields already filled.
Metadata lives in the file, not in Lightroom's catalog. When you migrate to a new DAM, rebuild after a crash, or hand the archive off, your decade of titles, keywords, GPS, and copyright comes with the photos. A catalog is rented. The file is yours.
Embedded © and creator survive most platforms that strip EXIF. Embedded capture date, GPS, and camera body are real authenticity signals as AI-generated images flood the market. An archive tagged at ingest is evidence, not just storage.
A few minutes per batch at ingest. A searchable, portable, provenance-carrying archive for the next decade.
Rename, copyright, geo, keywords, rating, and title. These are the fields your Lightroom catalog actually sorts by, the ones stock agencies check before they accept a submission, and the ones gallery platforms use to build captions. Miss one and something downstream shows up blank. Do all six before you import, and Lightroom opens to a library that already works the way you want it to.
A full shoot gets all six metadata fields written before Lightroom finishes importing the folder.
No. Most web tools upload your files to a server so the server can do the work. Jade GT does the work right inside your browser window, using your own laptop's power. Your photos stay on your laptop from start to finish.
Load Jade GT, then disconnect from the internet. It still works. That's your proof your photos aren't going anywhere.
AI image models learn by looking at millions of photos scraped from the internet. A photo that passes through a cloud-based tool can end up in that pile. Jade GT never receives your photos, so they can't be saved, studied, or fed to any model. This isn't a policy we promise to follow. It's how the app is built.
"The tool I use to tag your photos never uploads them." True, because the tool has nowhere to upload to. Couples who ask about AI get a clean answer before the contract is signed.
One tool. Your workflow. Your files.
| Feature | Hobbyist | Pro |
|---|---|---|
| Interactive map + GPS editing | ✓ | ✓ |
| EXIF / IPTC viewer | ✓ | ✓ |
| Keywords, description, copyright, artist | ✓ | ✓ |
| Privacy EXIF scrub | ✓ | ✓ |
| Mobile GPS logger | Local only | Desktop pairing |
| Photos per batch | 10 | Unlimited |
| Daily photo edits | 20 | Unlimited |
| Direct save to disk | · | ✓ |
| GPX track matching | Up to 10 photos | Full batches |
| RAW file support (CR3, ARW, NEF…) | · | ✓ |
| Stock compliance engine | · | ✓ |
| Metadata templates | Up to 10 photos | Full batches |
| WebP / AVIF export | Up to 10 photos | Full batches |
| Priority support | · | ✓ |
Everything working photographers tend to ask on day one.
Never. Jade GT runs entirely in your browser. Your files never leave your machine. Nothing trains an AI on your work, because we can't see it either.
That's the Pro use case. Speed depends on your machine, not our servers. Most pros tag a full 2,000-photo shoot in under two minutes on a modern laptop.
Yes. CR3, ARW, NEF, and more, for Pro. Jade GT writes an XMP sidecar for full Lightroom compatibility while applying direct EXIF where supported.
Yes. Drop a pin on the venue, apply to all selected photos, done. Or use the Mobile GPS Logger on your phone next time. Free forever.
Yes. The privacy scrub removes GPS coordinates, camera serial numbers, and other identifying EXIF data in one pass. Useful before posting photos of kids, homes, or sensitive locations. Free tier included, runs locally in your browser.
Yes. Jade GT is deterministic. No ML, no face recognition, no generative fill. Everything runs locally in your browser, so nothing about your clients trains anyone's model.
More: What to tell clients who ask arrow_forwardStill have questions?
Visit the user guide arrow_forward