> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage and Credits

> Track credits across activities, and spend them on reasoning before pixels.

Credits track product usage across activities. The usage page is where you see what you have, what is left, and where it went.

<Frame caption="Credit usage log and usage summary">
  ![Credit usage log and usage summary](https://placehold.co/1600x900/EEEEEE/31343C?text=08-04-usage-credits.png)
</Frame>

| What you see             | Why it matters                           |
| ------------------------ | ---------------------------------------- |
| Total credits            | Your allowance for the current period    |
| Remaining credits        | What is left to spend                    |
| Queries or generations   | Activity that consumed credits           |
| Activity-level usage     | Where credits are going                  |
| Workspace usage patterns | How the team is spending across projects |

Honest advice: do not burn credits by asking for final designs too early. Use lighter workflows first.

* [Review the UX](/product-design-flow/review-ux) and map the flow
* Clarify edge cases
* Use [Brainstorm](/product-design-flow/brainstorm-ideas) while still thinking
* Generate [high-fidelity prototypes](/product-design-flow/high-fidelity-prototype) once the direction is clear

Good credit habits: use richer context to reduce repeated prompting, ask for reasoning before generating many design variations, refine focused parts instead of regenerating entire screens, and use Context Pods for repeated product context. See plans and pricing at [figr.design/pricing](https://figr.design/pricing).

<Note>
  \[VERIFY: confirm how credits are calculated, and whether any credit-to-time comparison is approved language before adding it.]
</Note>