> 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/organizing-images/star-ratings-in-luminar-for-desktop.md).

# Star Ratings in Luminar for Desktop

Learn how to assign star ratings to your images in Luminar for Desktop to help sort and categorize your photos efficiently and streamline your editing workflow.

{% @arcade/embed url="<https://app.arcade.software/share/aEy9wQE9VukuSWwfbFhB>" flowId="aEy9wQE9VukuSWwfbFhB" %}

The **Star Ratings** feature in Luminar for Desktop allows you to easily rate and organize your photos, helping you quickly identify your best shots and sort through large collections. You can rate each photo with a score ranging from **1 star** to **5 stars**.

**Viewing and Filtering by Star Ratings**

Once you've rated your photos, you can filter and sort your library based on star ratings, making it easy to find your best images when you need them.

To filter your images by star rating:

1. Go to the **All Photos**.
2. Select the **Rating** option.
3. Choose the desired star rating to display only photos with that specific rating.


---

# 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/organizing-images/star-ratings-in-luminar-for-desktop.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.