> 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/about-luminar-for-desktop/standalone-image-editor.md). # Standalone Image Editor Discover how to use Luminar for Desktop as a standalone image editor, allowing you to edit photos with advanced tools and features without relying on other software. You can choose to open one or multiple images in a Luminar for Desktop session and make basic or creative edits to them. Any edits made to these images will automatically be stored in your Luminar for Desktop Catalog. There are several ways to open images for editing in Luminar for Desktop: * You can **add folders**, leaving your photos exactly where they are on your hard drive. * You can **import images** from a memory card or external drive, moving or copying them to a new location. * You can **open individual images** from any location, which allows you to easily edit and export photos that you don’t want to keep in your **Luminar Catalog**. --- # 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/about-luminar-for-desktop/standalone-image-editor.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.