Review & Commit

Summary

Jade GT never writes changes as you type. Every edit waits in a staged list. The Review Hub is the dialog where you confirm those edits per category, check the time estimate, and write the batch to disk.

• One toggle per category

  GPS, Tags, Clock, Rename, Scrub, and Compress each get their own card with its own toggle. Commit some now, leave the rest staged for later.

• Time estimate

  Big AVIF batches can run several minutes. The footer shows an estimate so you can pick a good time to start.

• Resume a half-finished commit

  If you closed the tab mid-save in Direct Save mode, Jade GT spots the half-finished save next time you open the Hub and offers to pick up where it left off.

The Review Hub. Every staged change in one place, grouped by category, ready to write.

Opening the Review Hub

Two ways in, same dialog.

• Commit button in the right-panel header. Shows a running count of staged edits and a pulsing dot whenever you have anything queued.
• Ctrl+S from anywhere (Mac: Cmd+S). Opens the Hub even while a text field is focused. A keystroke with nothing staged shows a small "No staged changes to commit" notice.

Inside the Hub, Ctrl+Enter fires the same path as the Write Changes to Disk button, so a keyboard-first save is two keystrokes: Ctrl+S to review, Ctrl+Enter to confirm.

Spotting staged work without opening the Hub

Each tab (Tags, Location, EXIF Info, and so on) shows a pulsing dot when it has pending edits. The Pending Save card on the Preview tab lists every staged change for the current photo without making you open the Hub.

The Field Changes panel

The top of the Hub shows a flat list of exactly which fields will change, summed across the whole batch. It lives above the category cards so the first thing you read is the answer to "what is this save actually doing?"

A typical line looks like one of these:

• +12 · -3 keywords across 8 photos: twelve new keywords added, three removed, spread across eight photos. List fields (keywords, subject codes, private keywords) collapse to a plus/minus count so an unintended keyword purge stands out before you click Write.
• Copyright set on 8 photos: a single-value field that was empty before and now has a value. "Set" only shows the first time a field gains content.
• GPS coordinates updated on 5 photos: counts photos where latitude or longitude changed. Altitude or direction changes ride along on the same write, so they don't count separately here.
• Capture time shifted on 12 photos: clock corrections from the EXIF Info Shift Time picker.

The panel reflects category toggles. Switch the Tags card off and every IPTC line disappears from this list because Jade GT will not write those fields.

What "preserved" actually means

The footer line under the panel reads "Fields not listed above are preserved as-is on every photo." Jade GT only writes the fields you staged. Develop settings, ratings you did not touch, embedded thumbnails, maker notes, and every other EXIF field stay exactly as they were across the save.

The category cards

The Hub groups every staged change into one card per category. Each card shows an icon, a count, and a one-line description.

One category card. Icon, label, count-aware description, and a toggle that controls whether this category commits.

Card	What it covers
Privacy Scrub	Photos with a total metadata strip staged from EXIF Info
GPS Updates	New or moved coordinates from the Location tab
Tagging & Metadata	Keywords, captions, descriptions, ratings, and IPTC fields from the Tags tab
Clock Corrections	Capture-time shifts from the EXIF Info Shift Time picker
Batch Renaming	New filenames from the Rename tab
Format & Compression	Format and quality changes from the Compress tab

Cards only appear when their category has at least one staged photo. A clean tab does not clutter the Hub.

Partial commits

Each card has its own toggle. Toggle a card off and Jade GT skips that category for this save; the edits stay staged for next time.

Toggle a card off and it dims. The Include All link flips every toggle back on.

• Include All

  A small link at the top of the section turns every toggle back on at once.

• Faded cards stay staged

  Toggle a card off and it dims. The pulsing dot on the tab that owns those edits stays lit.

• Pick your order

  A clean way to ship GPS today and come back to keywords tomorrow, without losing either set of edits.

What gets written, in order

Inside a single commit, Jade GT writes the categories in this order: Scrub, GPS, Tags, Clock, Rename, Compress. Jade GT skips the rest.

Compress extras

Two extra controls appear inside the Format & Compression card when they apply.

The Format & Compression card with both extras visible: Keep Originals (left it on to write next to the original) and the AVIF slow-encode warning.

• Keep Originals toggle

  Shows up when Compress is on and your saving strategy is Direct Save. Leave it on (the default) and Jade GT writes the new file next to the original. Turn it off and the original gets replaced. In Export mode the ZIP keeps both automatically, so the toggle is hidden.

• AVIF slow warning

  An amber strip appears at the bottom of the Compress card when any AVIF photo is in the batch. AVIF can take one to three minutes per large photo. WebP gets you similar file sizes in seconds.

Time estimate

The footer shows a rough time estimate and a per-format breakdown when the batch is more than a few seconds of work.

The Review Hub footer. Discard All on the left, an estimate plus format breakdown below it, and the primary Write Changes to Disk button on the right.

The estimate is based on the format mix in the batch:

• AVIF: roughly 90 seconds per pair of photos (the slowest format).
• WebP: roughly 6 seconds per three photos.
• JPEG: roughly 2 seconds per three photos.
• Metadata-only edits (GPS, Tags, Clock, Rename, Scrub): about 1 second per photo.

Real-world time depends on your CPU, the photo sizes, and what else your browser is doing. The estimate is a guide, not a guarantee.

Writing changes to disk

Click Write Changes to Disk in the footer to start the save. What happens next depends on your saving strategy:

• Direct Save

  Jade GT overwrites the original files in place (or writes the converted file next to them, with Keep Originals on). A progress bar shows photos saved over total. You can cancel mid-run; photos already saved stay saved.

• Export Mode

  Jade GT builds a ZIP file with every modified photo and offers it as a download. The source folder stays untouched. On iOS, the ZIP goes through the Web Share sheet so you can save it to Files or send it to an app.

Committed changes cannot be undone in Jade GT

Once a save finishes, the file on disk has the new contents. The Undo history does not reach across a commit. For destructive operations (Privacy Scrub, in-place rename, in-place compress), keep a backup or work in Export mode.

The no AI training flag

Every saved photo can carry a "do not use for AI training" note that other apps can read. Use it to back up the promise you make to clients about their photos.

The No AI Training toggle sits in the Photos column header next to the saving strategy. It is on by default. The Command Palette (Cmd+K or Ctrl+K) has the same toggle if you prefer to find it by search.

Leave it on for client deliveries, gallery uploads, and stock submissions. Turn it off only when you want to release a photo with no restrictions.

What it does, in plain terms

When the toggle is on, every saved photo carries a tag that tells other apps "the rights holder does not allow this photo for AI training." Apps that read photo metadata (Adobe Lightroom, Bridge, Capture One, most stock agency intake systems, and AI scrapers that honor the standard) pick the tag up and treat the photo accordingly.

The tag travels inside the photo file. A ZIP export, an AirDrop, or an upload to a metadata-preserving cloud service all carry it forward. Your client never has to do anything.

What this is, and what it isn't

The flag is a clear signal anyone reading the photo's metadata can find. It is not a lock. A bad actor who strips the metadata can still feed the pixels to a model. The flag does its job against tools and services that follow the standard. That covers the major stock agencies and the AI training pipelines that publicly honor it.

For the curious: the exact fields written

Three rights fields cover three different reading conventions, so whatever software the recipient runs, at least one will register. You never need to type any of these by hand. Jade GT writes them for you when the toggle is on.

Field	Value	Who reads it
plus:DataMining	DMI-PROHIBITED-AIMLTRAINING	PLUS Coalition tools, most stock agencies
c2pa:trainingMining	notAllowed	Adobe Content Credentials
xmpRights:Marked	True	Long-standing rights-asserted hint

After the commit

When the save finishes, a toast appears with the result and the dialog closes. The exact wording depends on the outcome.

• All photos saved

  "Successfully processed N photos." The staged dots clear and the Commit button drops to zero.

• Some failures

  "Saved N photos · M failed, see staged list." Photos that failed stay marked so you can fix them and try again.

• You cancelled

  "Cancelled. N of M photos processed." Saved photos keep their edits; the rest stay staged.

Why a photo might fail

The most common reasons: the file was moved or deleted between open and save, the browser ran out of disk space, you revoked folder permission, or another tool (Lightroom, Bridge, Finder) saved over the file after you opened it. The failure card on the photo tells you which one, and the Preview tab Re-read button gets you a clean slate to retry.

Working with other tools

If you open a photo in Jade and then edit it in Lightroom, Bridge, or Finder before committing, Jade spots the outside change. It warns you so it does not overwrite the other tool's work.

The warning appears as a yellow banner at the top of the Review Hub, above the Field Changes panel, whenever Jade spots a write outside the app. The banner counts the affected photos and names the likely culprits (Lightroom, Bridge, Finder). It offers two buttons: Skip changed photos and Overwrite anyway.

Jade checks for outside writes in two places:

• When the Review Hub opens. Jade re-reads each staged photo's modification time on disk and compares it to the time it saw at load. If anything drifted, the banner appears above the Field Changes panel.
• Just before each photo writes. A second check catches files another tool edited mid-commit (rare but real if Lightroom is auto-saving in the background). Jade GT skips the photo and notes the conflict on its failure card.

• Skip changed photos (recommended)

  Drops the conflicted photos from this commit. They land on the failure list with a "conflict" record so you can reopen them from disk to pull in the external edits, then re-stage your Jade-side changes on top.

• Overwrite anyway

  Use this only when you know your Jade edits are the ones to keep. Saves run as if the outside write never happened. Any pending Lightroom or Bridge edits to those files are lost.

How to recover from a conflict

The cleanest path: drop the conflicted photos from your batch (click the X on each conflict card, or use Discard All if every photo conflicted), then reopen the folder. Jade reads the current file off disk, Lightroom changes and all. Stage your Jade edits on top and commit.

Export mode skips this check

Export mode writes a ZIP next to your originals and never touches the source files. A Lightroom edit during an Export session has no conflict to detect. The banner only appears in Direct Save mode.

Resuming an interrupted commit

If you close the tab or crash mid-save in Direct Save mode, Jade GT writes a small recovery record. The next time you open the Review Hub, a banner at the top offers to pick up where it left off.

• Banner shows progress

  "X of N photos were saved. Y remain." Click Resume to continue from photo X+1, or close the banner to discard the record and start over.

• Export ZIPs cannot resume

  A partial ZIP file is not useful, so Export sessions cannot resume. The banner says so, and the full batch runs again if you continue.

• Records expire

  Recovery records older than a few days are cleaned up automatically so you do not see stale banners.

Discard all

A small Discard All link sits in the footer next to the Commit button. Click it to drop every staged change in one shot.

Discard cannot be undone

A confirmation dialog asks first, because there is no in-app way back. Every photo's metadata, GPS, name, and compression returns to the original state. Use Discard All for a fresh start, not as a casual reset.

Daily limits (free tier)

Free accounts cap at 20 photos per day. The footer shows how many you have left.

• Counter resets at midnight local time

  The count is per-device and resets at midnight in your time zone.

• Pro lifts the cap

  A Pro subscription removes the daily limit and unlocks Direct Save, RAW support, and unlimited batches. See the Pro Features page for details.

Troubleshooting

The Commit button is greyed out

Nothing is staged. Edit a photo on any tab and the count next to Commit ticks up. The button enables when there is something to commit.

A category card I expected is missing

Cards only appear for categories with at least one staged photo. If you remember staging a keyword change but the Tags card is missing, the change probably never made it past the field; reopen the Tags tab and try again.

The time estimate seems way off

The estimate assumes a typical desktop CPU. A laptop on battery or a slower phone can run two or three times longer. AVIF is the biggest swing; if your batch is mostly AVIF, plan for the long end of the estimate.

The Resume banner keeps coming back

The recovery record points to a folder you no longer have permission for, or one that was moved or unplugged. Click the banner's close button to discard the record. You can re-stage the edits from the original photos when they are reachable again.

Hit the daily limit mid-batch

Free tier caps at 20 photos per day. The Hub commits as many as fit, then stops; the rest stay staged. Either wait for the midnight reset or upgrade to Pro to finish the batch now.

Related guides

• Tags tab

  Source of the Tagging & Metadata category.

• Location tab

  Source of the GPS Updates category.

• EXIF Info tab

  Source of the Clock Corrections and Privacy Scrub categories.

• Compress tab

  Source of the Format & Compression category, including the Keep Originals toggle that shows up in the Hub.

• Rename tab

  Source of the Batch Renaming category.

• Preview tab

  The Pending Save card on Preview shows the same per-photo summary the Hub shows for the full batch.