Skip to main content
Participant
August 4, 2026
Question

Problems with Exporting JPGs

  • August 4, 2026
  • 1 reply
  • 19 views

Hello,

I am experiencing a persistent and reproducible problem when trying to export or convert photos from my Lightroom cloud library, and I would appreciate your help investigating it.

Summary of the issue

When I select a large batch of photos (several hundred to several thousand) and run "Export Originals," the process regularly stalls partway through — sometimes after only a few dozen images, sometimes after several hundred. The progress indicator simply stops advancing, with no error message and no further disk or network activity after a short time.

The problem is specific to JPEG-sourced images. RAW files export without any issues, both with and without GPU acceleration enabled. It is not limited to a handful of individual files — it recurs across entire series of JPEGs (in my case, digitized scans from negatives and slides, all processed the same way), which rules out isolated file corruption as the cause.

I have also tried "Render to DNG" as a workaround, since DNG output does not appear to be affected by the same issue. However, this too has now started stalling, specifically during the "Preparing to Render to DNG" phase, before any actual rendering begins.

What sometimes helps (temporarily)

Manually opening one of the images that the export/render process appears to be stuck on, in full-size Detail view, sometimes causes the batch process to resume for a short while before stalling again on a later image. This is not a practical workaround at the scale of thousands of images, but it does suggest the issue is related to how the app fetches or renders full-resolution image data in the background during batch operations, rather than to any single damaged file.

If I cancel a stalled export, Lightroom reports "The file appears to be unsupported or damaged" for the files that were still queued at the time of cancellation. I do not believe this message reflects the actual condition of those files — it appears to be a generic result of interrupting the export mid-queue, since the same files display and open normally elsewhere in the app.

Troubleshooting already performed

  • Updated Lightroom to the latest version (Creative Cloud auto-updates are enabled, so the app is always current)
  • Updated AMD graphics drivers to the latest version, then restarted the computer
  • Tested with "Use Graphics Processor" set to both Auto and Off — no difference in behavior
  • Reset Lightroom preferences (renamed the .agprefs file to force a fresh one) — no difference
  • Checked Windows Event Viewer (Application log) around the time of the hangs — no relevant errors or warnings logged by Lightroom
  • Ran chkdsk on all relevant drives — no disk errors found
  • Confirmed via the sync/activity panel that the source photos are fully "Synced and Backed Up" in the cloud, so this does not appear to be a sync-completeness issue on the affected assets

Additional related issue

Separately, I have noticed that the "Local Storage" location I configure in Preferences (moved from the default location to a secondary internal drive) periodically reverts back to the default drive on its own, without any action on my part. I have to re-set it after this happens. I am not certain whether this is related to the export/render hangs, but wanted to mention it in case it is relevant.

System information

  • OS: Windows
  • Graphics: AMD Radeon 780M (integrated)
  • Library size: approximately 75,000+ photos, cloud-based (Lightroom, not Classic)
  • Affected content: JPEG images, largely digitized scans from negatives and slides, imported and edited over an extended period without prior issues

Request

Could you please help identify why batch export/render operations stall specifically on JPEG-sourced assets, and why this happens consistently across otherwise unremarkable files? I am happy to provide asset IDs, additional logs, or reproduce the issue with specific instructions if that would help your investigation.

Best regards, Per

    1 reply

    Srishti Bali
    Community Manager
    Community Manager
    August 4, 2026

    Hi ​@PerHomann ,

    Thank you for the detailed write-up and for taking the time to perform such extensive troubleshooting. The information you've provided is extremely helpful.

    Based on your observations, this appears to be related to how Lightroom (cloud) retrieves full-resolution originals during batch operations. The fact that opening one of the images in Detail view temporarily allows the export or DNG render queue to continue suggests Lightroom may be encountering an issue while fetching or preparing the full-resolution asset in the background.

    I'd recommend trying the following:

    1. Pre-cache the affected images
    Before starting a large export, open the affected images in Detail view and browse through them to encourage Lightroom to download and cache the full-resolution data locally. While this isn't practical for very large libraries, if it consistently allows the export to complete, it would help confirm that the issue is related to background retrieval of cloud assets rather than the image files themselves.

    2. Verify your Local Storage configuration
    Since you've noticed the Local Storage location occasionally reverting to the default drive, please verify which location is currently configured before starting the export. Also ensure that the selected drive has plenty of available free space (ideally 50 GB or more), as Lightroom needs local space to cache originals during export and rendering.

    3. Try exporting in smaller batches
    As a temporary workaround, try exporting 50–100 images at a time instead of several hundred or thousands. This reduces the number of simultaneous cloud retrieval requests and may help avoid the pipeline stalling.

    4. Capture Lightroom logs after reproducing the issue
    After the export stalls, please go to:

    Help > Troubleshooting > Save Logs to Desktop

    These logs capture rendering and sync activity and can provide valuable information about where the export pipeline is stopping.

     

    Regarding the "The file appears to be unsupported or damaged" message, you're correct that this is most likely a generic message shown after canceling an export and does not necessarily indicate that the original files are actually damaged.

     

    Please let us know the outcome after trying these steps, and if possible, share the generated logs. We'll be happy to continue investigating with you.

    Thanks, Srishti Bali | Community & Engagement Strategist, Digital Imaging | Adobe