> For the complete documentation index, see [llms.txt](https://docs.qolaba.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qolaba.ai/image-generation/output-settings-and-controls/resolution-and-quality.md).

# Resolution and Quality

Quality controls the visual fidelity and detail level of your generated image. Higher quality produces sharper, more detailed output — and costs more credits per generation. Choosing the right quality setting for the stage of your workflow is one of the most effective ways to manage credit usage without compromising final output.

***

#### Available Quality Settings

| Quality  | Resolution   | Credit Cost   | Best For                                                           |
| -------- | ------------ | ------------- | ------------------------------------------------------------------ |
| **720p** | 1280 × 720px | Lowest        | Quick concept tests, prompt validation, draft exploration          |
| **1K**   | \~1024px     | Low–Moderate  | General iteration, style testing, standard social media            |
| **2K**   | \~2048px     | Moderate–High | High-quality social media, presentations, client previews          |
| **4K**   | \~3840px     | Highest       | Print, large-format display, commercial production, final delivery |

***

#### How to Choose Quality

1. **Use 720p for exploration.** When testing a new prompt, model, or keyword combination, 720p gives you a fast, low-cost output that clearly shows composition, color, subject placement, and overall direction. There is no reason to generate at higher quality until you are satisfied with what you see at this level.
2. **Use 1K for standard iteration.** Once your prompt and settings are directionally correct, move to 1K for a clearer view of detail and quality before committing to a final resolution. Most social media platforms are well-served at 1K for standard posts and stories.
3. **Use 2K for client previews and high-quality social.** 2K produces noticeably sharper output suitable for client-facing previews, high-quality social media content, and most digital distribution formats. Use this when 1K feels slightly insufficient but 4K is not yet warranted.
4. **Use 4K for final production output only.** 4K is reserved for outputs destined for print, large-format display, broadcast, or any context where maximum resolution is required. Credit usage is significantly higher at 4K — never use it for testing or iteration.

***

#### Draft vs. Final Strategy

The most credit-efficient approach to image generation treats quality as a two-stage decision:

* **Stage 1 — Draft:** Generate at 720p or 1K to validate prompt, model, composition, and style. Iterate here until the output direction is confirmed.
* **Stage 2 — Final:** Upgrade to 2K or 4K for the confirmed output only. If multiple variations are needed, generate the batch at final quality only after the draft stage is complete.

{% hint style="info" %}
A 720p draft followed by a single 4K final generation costs a fraction of generating multiple 4K outputs from the start. Validate first — upgrade only when ready.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qolaba.ai/image-generation/output-settings-and-controls/resolution-and-quality.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.