
On Lightroom for iPhone or iPad, a batch export with Content Authenticity can remain on Rendering — This may take a while when the network connection is poor. Adobe lists this issue in its iOS/iPad section and recommends exporting one image at a time. Match those conditions before treating every long rendering operation as the same fault.
Key Takeaways
- This documented case is specific to Lightroom for mobile on iOS/iPad.
- Poor connectivity and Content Authenticity are part of the reported conditions.
- Try individual exports while retaining the agreed provenance requirement.
Check the platform and export context
Record the device, Lightroom version, whether you selected several photos and whether Content Authenticity was enabled. The Lightroom known-issues page contains multiple platform sections even though its URL includes desktop. The relevant batch-export entry is under Lightroom for mobile (iOS/iPad).
The page does not supply a universal waiting time after which rendering has failed. A large file or another export issue may also take time. Use the matching configuration as a reason to try the documented workaround, rather than diagnosing the network from the word Rendering alone.
Export a representative picture individually
Keep the original set and its approved edits available. Before repeatedly launching the whole batch, identify which files have already finished so you do not confuse duplicates with missing deliveries.
- Note the selected photos and intended export settings.
- Check whether connectivity is currently poor or interrupted.
- Try exporting one representative image with the intended settings.
- Open the completed output and confirm it is the correct photo.
- If the individual route works, proceed one picture at a time and record which files are complete.
Adobe's documented workaround changes the batch size. It does not direct you to remove the Content Authenticity requirement, strip metadata or publish a credential record more widely. Avoid solving a processing delay by silently changing the client's disclosure decision.
Preserve the agreed provenance scope
A delivery can require provenance information as well as visible image quality. Keep that requirement with the export notes and inspect what the output actually contains. The provenance-survival guide distinguishes a field being present from a credential validating and from a platform accepting the file.
If the project also uses Lightroom Classic, its credential storage choices address a separate question: attachment and public cloud publication have different consequences. Those desktop choices are not mobile troubleshooting commands, and this workaround does not authorize changing publication scope.
Reconcile the full delivery set
For a proposed six-photo delivery, maintain a simple list of six intended outputs and mark each only after the actual file opens and its required information has been checked. The example is a suggested control, not a reported export test.
Use an approved-version handoff record to connect each delivered file with the reviewed edit. An export counter or an earlier preview is not enough to confirm the recipient received every required picture.
If a single-image export also remains blocked, retain the working assets and report the device, version, settings and observed message to support. The listed batch workaround does not explain every export fault or guarantee that an individual attempt will succeed.
Related tasks
- Lightroom Content Credentials: Attach Privately or Publish to the Cloud?
- How Do I Keep AI Image Provenance Metadata Through Editing and Delivery?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Known issues in Lightroom: In the Lightroom for mobile (iOS/iPad) section, Adobe lists batch export with Content Authenticity staying on Rendering when the network connection is bad. Its workaround is exporting one image at a time.
Read the supplied known-issues article and verified the issue is under Lightroom for mobile (iOS/iPad), not the general desktop Exporting subsection. Captured October 29, 2026. No export or connection test was performed. No elapsed-time threshold or automatic success is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.