> 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/extra-tools/extra-tools-in-the-plugin-mode.md).

# Extra tools in the Plugin mode

Discover how to use catalog tools effectively when operating Luminar for Desktop as a plugin.

When you use Luminar for Desktop as a plugin for Photoshop or Lightroom Classic, all tools located in the Edit and Presets tabs will be accessible.

Also, you can use the HDR Merge, Focus Stacking, and Upscale AI tools in the Lightroom plugin. Achieve even more impressive results with any editing workflow.

Moreover, please keep in mind that if you invoke Luminar for Desktop from Photoshop or select the “Edit a Copy with Lightroom Adjustments” option in Lightroom Classic, you’ll get a TIFF file in the Luminar plugin.

Therefore, if you need to work with the RAW file in Luminar, you need to upload it in standalone mode.

Alternatively, using Lightroom Classic, you can choose ‘Export Original’ after right-clicking the photo > Export > Luminar for Desktop > Open Source Files.

When you use Luminar for Desktop as an Extension to Photos on macOS, Catalog tools are not available.


---

# 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/extra-tools/extra-tools-in-the-plugin-mode.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.