> For the complete documentation index, see [llms.txt](https://support.aperty.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.aperty.ai/about-aperty/as-a-standalone-editor.md).

# As a Standalone Editor

Portrait retouching should be quick, efficient, and accessible, allowing photographers of all levels to achieve stunning results with ease. That's why we've developed Aperty, a cutting-edge photo editing tool created by photographers for photographers.

Tailored specifically for professional portrait photographers, Aperty recognizes the historically complex and time-consuming nature of portrait retouching and offers a streamlined solution that combines ease of use with advanced technology. It enables photographers to achieve high-quality results efficiently, significantly reducing the time spent on post-processing.

Developed in collaboration with renowned portrait photographer Julie Trotti, Aperty simplifies retouching while maintaining consistent, high-quality outcomes in skin editing and other professional challenges.

### System Requirements

{% tabs %}
{% tab title="MacOs" %}

| **Mac model**  | <p>Early 2010 or newer MacBook, MacBook Air, MacBook Pro,<br>iMac, iMac Pro, Mac Pro, or Mac Mini</p> |
| -------------- | ----------------------------------------------------------------------------------------------------- |
| **Processor**  | Intel® Core™ i5 8gen or better, Apple M1/M2/M3 chip                                                   |
| **OS version** | macOS 12.0 or higher is required                                                                      |
| **RAM**        | 8 GB (16+ GB recommended)                                                                             |
| **Disk space** | 10 GB free space; SSD for best performance                                                            |
| **Display**    | 1280×768 or higher resolution                                                                         |

{% hint style="info" %}
You can check your Mac system specifications and hardware by choosing the **Apple icon > About this Mac**
{% endhint %}
{% endtab %}

{% tab title="Windows" %}

| **Hardware**   | Windows PC with a mouse or similar input device         |
| -------------- | ------------------------------------------------------- |
| **Processor**  | Intel® Core™ i5 8 gen or better, AMD Ryzen™ 5 or better |
| **OS version** | Windows 10 version 1909 or higher (only 64-bit OS)      |
| **RAM**        | 8 GB or more (16+ GB recommended)                       |
| **Disk space** | 10 GB free space; SSD for best performance              |
| **Display**    | 1280×768 or higher resolution                           |
| **Graphics**   | Compatible with OpenGL 3.3 or later                     |

{% hint style="info" %}
You can check your system specifications on Windows 10 by opening **Settings** and clicking **About.**
{% endhint %}
{% endtab %}
{% endtabs %}


---

# 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.aperty.ai/about-aperty/as-a-standalone-editor.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.