feat(media): extract image EXIF metadata (sanity.imageExifTags) on asset upload

[stipsan]

Ports sanity-io/sanity-plugin-media#293 by @am0wa into the monorepo.

Problem

metadata.image (sanity.imageExifTags) is never extracted because 'image' is missing from the upload extract array, and the GROQ projection also omits it — so even assets that already have the data won't return it.

Changes

• Add 'image' to the asset upload extract list (src/utils/uploadSanityAsset.ts).
• Add image to the asset GROQ projection so the data is returned for existing assets (src/modules/assets/index.ts).
• Auto-populate image.ImageDescription into the DialogAssetEdit Description field as a fallback, for image assets only (src/components/DialogAssetEdit/index.tsx).

Review follow-ups

Addressed Copilot review comments:

• Validate ImageDescription with a runtime typeof === 'string' check (no unsafe cast).
• Preserve intentionally empty localized description strings (locale.id in field) so EXIF does not refill cleared values.
• Let react-hook-form own the Description field default (removed asset-derived defaultValue override).
• Added DialogAssetEdit tests for EXIF prefill, non-override of existing description, and empty localized preservation.

Notes

• Commits are authored by the original contributor (@am0wa) and the changeset credits them via an author: directive.
• The change is non-breaking, so the changeset is a minor bump.

  

[changeset-bot]

🦋 Changeset detected

Latest commit: 5c66deb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
sanity-plugin-media	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
plugins-studio	Ready	Preview	Jul 30, 2026 8:19pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
plugins-e2e-test-studio	Ignored		Jul 30, 2026 8:19pm

[Copilot]

Pull request overview

This PR ports the Media plugin enhancement to extract and surface sanity.imageExifTags (metadata.image) on image uploads, and uses EXIF ImageDescription as a fallback to prefill the asset Description field in the asset edit dialog.

Changes:

• Requests image metadata extraction during asset uploads.
• Extends the assets GROQ projection to include metadata.image.
• Adds an EXIF-based fallback for initializing the Description field in DialogAssetEdit.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
plugins/sanity-plugin-media/src/utils/uploadSanityAsset.ts	Adds image to the upload extract list so EXIF tag metadata is generated on upload.
plugins/sanity-plugin-media/src/modules/assets/index.ts	Updates GROQ projection to return metadata.image for existing assets.
plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx	Prefills Description from metadata.image.ImageDescription when no description exists.
.changeset/media-image-exif-metadata.md	Adds a minor changeset documenting the new extraction + UI behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[am0wa]

@stipsan thanks for port 🙌
Unfortunately I have no write permission to rebase onto latest main and fixup auto-review comments.

So guys lets decide: whether you fix it up (its non braking change) or I'd need to create a fresh fork and PR...

[github-actions]

✅ E2E Tests

🟢 24 passed • view full report • view run

Studio: https://plugins-e2e-test-studio-kzkwru5q2.sanity.dev

Datasets: pr-1115-chromium-30578570363, pr-1115-firefox-30578570363

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	31.4%	5009 / 15948
🔵	Statements	31.11%	5271 / 16941
🔵	Functions	26.8%	1281 / 4779
🔵	Branches	22.56%	2526 / 11192

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
plugins/sanity-plugin-media/src/components/DialogAssetEdit/Details.tsx	69.23%	75%	83.33%	81.81%	14, 16-17
plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx	68.84%	57.93%	64.7%	71.66%	32, 91, 116-117, 156, 168-171, 178-183, 190, 200, 209-237, 244, 266-270, 283, 299-301, 308-313, 369, 415
plugins/sanity-plugin-media/src/modules/assets/index.ts	81.48%	42.62%	78.62%	81.22%	117-119, 135-137, 150, 169, 176, 321, 334-335, 357-366, 389, 410, 455-481, 490, 499-504, 509, 516-520, 525, 531-534, 552-555, 600, 630-639, 671-680, 734-742, 770
plugins/sanity-plugin-media/src/utils/uploadSanityAsset.ts	26.66%	22.22%	6.66%	26.66%	12-15, 19-30, 36-37, 48-49, 60-90

Generated in workflow #8393 for commit 5c66deb by the Vitest Coverage Report Action

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx:112

• When locales are disabled but the stored field value is a localized object (e.g. {en: '', fr: ''}), flattenField() now returns the EXIF fallback because it searches for the first truthy value. That re-fills intentionally cleared localized values in the locales-disabled path, contradicting the goal of preserving empty strings.

Consider only applying the EXIF fallback when the localized object has no keys (i.e. truly missing), and preserve '' when keys exist but are empty.

      const flattenField = (field: unknown, fallback = ''): string => {
        if (typeof field === 'string') return field
        if (typeof field === 'object' && field !== null) {
          const values = Object.values(field as Record<string, string>)
          return values.find((v) => v) || fallback

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx:88

• locale.id in field will also match inherited/prototype keys (e.g. toString, __proto__), which can cause non-string values to be assigned into the localized form object. Using an own-property check plus a typeof === 'string' guard keeps the “preserve empty string” behavior without risking prototype leakage.

            // Prefer key presence over truthiness so an intentional empty string
            // (e.g. `{en: ''}`) is preserved and does not fall through to EXIF.
            if (typeof field === 'object' && field && locale.id in field) {
              obj[locale.id] = field[locale.id] ?? ''
            } else if (typeof field === 'string') {

plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx:114

• In the flattenField locale-normalization path, applying the EXIF fallback when field is an object can unintentionally refill a description that was explicitly localized-but-empty (e.g. {en: '', fr: ''}) when locales are later disabled. Treat a non-empty object as “explicit value present” and only use the fallback when the object has no values at all.

        if (typeof field === 'object' && field !== null) {
          const values = Object.values(field as Record<string, string>)
          return values.find((v) => v) || fallback
        }
        return fallback

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b3a4020. Configure here.}

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx:117

• flattenField will apply the EXIF fallback when asset.description is a localized object whose keys exist but all values are empty/null (e.g. after locales were previously enabled and descriptions were cleared). In that case, the presence of the object should still be treated as an intentional “no description”, otherwise EXIF can refill cleared values when locales are later disabled.

      const flattenField = (field: unknown, fallback = ''): string => {
        if (typeof field === 'string') return field
        if (typeof field === 'object' && field !== null) {
          const values = Object.values(field as Record<string, string>)
          return values.find((v) => v) || fallback

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx:75

• imageDescription is typed as string | undefined but is passed as the fallback argument to helpers that expect a string. When imageDescription is undefined (most common case), this can lead to undefined being written into the generated default values object (and will also fail type-checking in strict mode).

      let imageDescription: string | undefined
      if (asset && isImageAsset(asset)) {
        const raw = asset.metadata?.image?.['ImageDescription']
        if (typeof raw === 'string') {
          imageDescription = raw

plugins/sanity-plugin-media/src/components/DialogAssetEdit/index.tsx:117

• When locales are not configured, flattenField() will apply the EXIF fallback if a localized object exists but all its values are empty/null. This can cause an intentionally-cleared localized description (e.g. {en: ''} or {en: null} from sanitizeFormData) to be refilled from EXIF when locales are later disabled.

      const flattenField = (field: unknown, fallback = ''): string => {
        if (typeof field === 'string') return field
        if (typeof field === 'object' && field !== null) {
          const values = Object.values(field as Record<string, string>)
          return values.find((v) => v) || fallback