<!--
{
  "availability" : [
    "iOS: 8.0.0 -",
    "iPadOS: 8.0.0 -",
    "macCatalyst: 13.1.0 -",
    "macOS: 10.11.0 -",
    "tvOS: 10.0.0 -",
    "visionOS: 1.0.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "PhotoKit",
  "identifier" : "/documentation/Photos/PHContentEditingInput/fullSizeImageURL",
  "metadataVersion" : "0.1.0",
  "role" : "Instance Property",
  "symbol" : {
    "kind" : "Instance Property",
    "modules" : [
      "Photos"
    ],
    "preciseIdentifier" : "c:objc(cs)PHContentEditingInput(py)fullSizeImageURL"
  },
  "title" : "fullSizeImageURL"
}
-->

# fullSizeImageURL

The URL to a file that contains the full-sized image data.

```
var fullSizeImageURL: URL? { get }
```

## Discussion

Typically, your app or extension does not need to load a full-sized image for use in an editing UI. Instead, use the [`displaySizeImage`](/documentation/Photos/PHContentEditingInput/displaySizeImage) property to retrieve an image suitable for screen display. You can then load the full-sized image on a background queue so that it will be ready by the time the user finishes editing the display-size image. At that time, apply the user’s adjustments to the full-sized image and then use the [`PHContentEditingOutput`](/documentation/Photos/PHContentEditingOutput) class to commit the edit to the photo library.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)