> 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-for-web/about-luminar-on-web/supported-file-types-and-cameras.md). # Supported File Types and Cameras Luminar on Web supports JPEG, PNG, HEIC, TIFF, and RAW formats**.** #### RAW Files Luminar on Web can open RAW files from a wide range of cameras. RAW processing may vary depending on the camera model, and compatibility may differ from Luminar for Desktop. RAW files from camera models that haven’t been specifically verified for Luminar on Web may still open, but processing results can vary. If a RAW file doesn’t open or the result doesn’t look as expected, try using a JPEG or another supported format. #### Image Resolution Web processing also has browser-dependent limits on image resolution. These limits apply to both image processing results and export. Safari and other browsers on iOS currently limit the maximum resolution to 4000 pixels on the long edge. Chrome and Firefox currently allow up to 6000 pixels on the long edge. --- # 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-for-web/about-luminar-on-web/supported-file-types-and-cameras.md?ask=&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.