> For the complete documentation index, see [llms.txt](https://support.skylum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.skylum.com/luminar/working-with-iphone/system-requirements-for-iphone.md).

# System Requirements for iPhone

Review the necessary system specifications for Luminar Mobile to run smoothly on iPhone, ensuring compatibility with your device’s capabilities.

**Luminar requires IOS 17 to run.**

The amount of Random Access Memory (RAM) on your device plays a crucial role in determining the size of images you can edit comfortably. RAM acts as a temporary workspace for your device, and having more RAM allows you to handle larger and more complex images without encountering performance issues. 

**Supported RAM capacities:**

<table data-full-width="false"><thead><tr><th width="226">RAM</th><th width="249">iOS</th><th>iPadOS</th></tr></thead><tbody><tr><td>16GB</td><td>-</td><td>8000px</td></tr><tr><td>8GB</td><td>6000px</td><td>8000px</td></tr><tr><td>6GB</td><td>6000px</td><td>8000px</td></tr><tr><td>4GB</td><td>4000px</td><td>6000px</td></tr><tr><td>3GB</td><td>4000px</td><td>6000px</td></tr><tr><td>2GB</td><td>-</td><td>1500px</td></tr></tbody></table>

{% hint style="info" %}
For a seamless image editing experience, especially when working with large or complex images, it's recommended to use a device with more than 4GB of RAM. If you frequently edit high-resolution photos or create intricate graphic designs, consider using a device with 6GB or 8GB of RAM for the best performance.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.skylum.com/luminar/working-with-iphone/system-requirements-for-iphone.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.