QuickLookAR shares the actual USDZ model instead of the original website URL — critical copyright and data leak issue on iOS 26

QuickLookAR shares the actual USDZ model instead of the original website URL — critical copyright and data leak issue on iOS 26

Since iOS 26, QuickLookAR (or ARQuickLookPreviewItem) no longer preserves the original web URL when sharing a model. Instead of sending the link to the hosted file, the system directly shares the actual USDZ model file with the recipient.

This is a critical regression and a severe breach of intellectual property protection, as it exposes proprietary 3D models that must never be distributed outside of the controlled web environment.

In earlier iOS versions (tested up to iOS 18), QuickLookAR correctly handled sharing — the share sheet would send the website link where the model is hosted, not the file itself. Starting with iOS 26, this behavior has changed and completely breaks the intended secure flow for AR experiences.

Our project relies on allowing users to view models in AR via QuickLook, without ever transferring the underlying 3D assets. Now, the share operation forces full file sharing, giving end users unrestricted access to the model file, which can be copied, rehosted, or reverse-engineered.

This issue critically affects production environments and prevents us from deploying our AR-based solutions.

  1. Implement a standard QuickLookAR preview with a USDZ file hosted on your web server (e.g., via ARQuickLookPreviewItem). 2. Open the AR view on iOS 26. 3. Tap the Share icon from QuickLookAR. 4. Send via any messenger (Telegram, WhatsApp, etc.). 5. Observe that the actual .usdz model is sent instead of the original website URL.

Expected behavior: QuickLookAR should share only the original URL (as in iOS 17–18), not the file itself. This ensures that intellectual property and licensed 3D models remain protected and controlled by the content owner.

Actual behavior: QuickLookAR shares the entire USDZ file, leaking the model content outside of the intended environment.

Impact: • Violation of copyright and confidential data policies • Loss of control over proprietary 3D assets • Breaking change for all existing web-based AR integrations • Critical blocker for AR production deployment

Environment: • iOS 26.0 and 26.1 (tested on iPhone 14, iPhone 15) • Safari + QuickLookAR integration • Works correctly on iOS 17 / iOS 18

Notes: This regression appears to have been introduced in the latest iOS 26 system handling of QuickLookAR sharing. Please escalate this issue to the ARKit / QuickLook engineering team as it directly affects compliance, IP protection, and usability of AR features across production applications.

Additional Notes / Verification:

Please test this behavior yourself using the CheckAR test model on my website: https://admixreality.com/ios26/

•	If the login page appears, click “Check AR” and then “View in Your Space”.
•	On iOS 18 and earlier, sharing correctly sends the website URL.
•	On iOS 26, sharing sends the actual USDZ model file.

This clearly demonstrates the regression and the security/IP issue.

Answered by DTS Engineer in 872534022

Thanks for the clarification. I’ve updated your bug (FB20753534) with these details.

Beyond that, there’s no much I can do for you. The correct path for this is Feedback Assistant, and you’re already on that path. I can confirm that your bug is being looked at by the right folks, and they’ll need to make a call as to how to address it.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

You’ve written your post like a bug report, which suggests you are in the wrong place. The Apple Developer Forums are here for developers to get help using Apple APIs, developer tools, and so on. For cases like this, where you’d like to request a change to Apple systems — well, a change back — the place to go is Feedback Assistant.

See Bug Reporting: How and Why? for lots of info on how to use that tool effectively.

Once you’re done, please post your bug number, just for the record.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thank you, Quinn. I actually filed a report for this issue back on October 20, 2025. Feedback ID: FB20753534 We are asking for your assistance because this is a critical blocker for our business. The bug forces the distribution of copyright-protected source files, which we are legally not allowed to share. This violates security and privacy standards, meaning we cannot support any users on iOS 26 or later. This situation is severely impacting our reputation and operations. We would be incredibly grateful for any help in escalating this issue to find a solution.

Hey @White_Nebel,

I'd like to point out that AR Quick Look does not provide DRM functionality. If AR Quick Look can display your model at all from a remote url, that means your model is publicly accessible on the internet.

For example, it is possible to download the model from your example site without ever involving AR Quick Look on iOS.

-- Greg

FB20753534

Thanks for that. I took a quick look [pun intended :-] and there’s nothing to report on that front.


With regards Greg’s point, I guess that your key concern is that:

  • On iOS 26 it’s trivial for users to grab your AR content.
  • On iOS 18 it was still possible — there are a bazillion apps on the App Store that let you download files from the Internet — but it wasn’t trivial.

Is that an accurate summary?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Yes, users can ultimately obtain the file in both cases. The difference lies in how this happens. Prior to iOS 26, obtaining the USDZ required user workarounds or third-party tools, while Quick Look itself shared the canonical web URL. Starting with iOS 26, the OS-level Share action in Quick Look directly exports and distributes the USDZ asset, ignoring canonicalWebPageURL. This turns asset distribution into a first-class, system-supported behavior and breaks the previously supported web-based access and licensing flow. At this stage, it would be sufficient for us if the behavior reverted to how it worked on iOS 18 and earlier. We would greatly appreciate any guidance or assistance in resolving this issue.

Thanks for the clarification. I’ve updated your bug (FB20753534) with these details.

Beyond that, there’s no much I can do for you. The correct path for this is Feedback Assistant, and you’re already on that path. I can confirm that your bug is being looked at by the right folks, and they’ll need to make a call as to how to address it.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

QuickLookAR shares the actual USDZ model instead of the original website URL — critical copyright and data leak issue on iOS 26
 
 
Q