> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/gum-tool/gum-elements/skia-standard-elements/arc.md).

# Arc

### Introduction

Arcs are curved lines with variable thickness. Arcs can also be used to draw wedges if the line thickness is large enough.

<figure><img src="https://2695663588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fzQmxQ1VeUFHcoo2c%2Fuploads%2Fgit-blob-00c5400b6839d9ec517cfe47cf77fd80d09d8067%2Fimage.png?alt=media" alt=""><figcaption><p>Three arc instances - a default arc, a rounded arc with gradient graphics, and an arc creating a wedge</p></figcaption></figure>

### Arc dimensions

Arcs draw inside their bounds, with the edge of the arc touching the bounding rectangle. On Skia, the thickness of the arc remains consistent regardless of the bounds width and height. For MonoGame, KNI, and FNA, see [Arcs in Non-Square Bounds](#arcs-in-non-square-bounds).

The following shows an arc with a Sweep Angle of 270 degrees, being resized in the Editor tab.

<figure><img src="https://2695663588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fzQmxQ1VeUFHcoo2c%2Fuploads%2Fgit-blob-a90f5ba229572762921b686c32cfcdafdec478b6%2F26_16%2014%2029.gif?alt=media" alt=""><figcaption><p>On Skia, arc thickness remains constant when an arc's dimensions change</p></figcaption></figure>

### Arc and Circle

An Arc with a `Sweep Angle` of `360` draws the same pixels as a [Circle](https://docs.flatredball.com/gum/gum-tool/gum-elements/circle.md) with the same bounds when the Arc's `Thickness` equals the Circle's `Stroke Width`.

{% hint style="info" %}
On MonoGame, KNI, and FNA this match is available in November 2026, or now if building Gum from source. Before then, the Arc's stroke was about one pixel wider than the Circle's.
{% endhint %}

### Arcs in Non-Square Bounds

In non-square bounds, an Arc on MonoGame, KNI, and FNA is stretched to fill the bounds, so it is thicker along the longer side. An Arc 60 wide and 40 tall with a `Thickness` of `8` is about `12` thick at the left and right. The same stretch makes a radial gradient elliptical.

<figure><img src="https://2695663588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fzQmxQ1VeUFHcoo2c%2Fuploads%2Fgit-blob-8cda3c883056b544fc0ffec3c107e44e640afa8a%2F21_05%2019%2029.png?alt=media" alt=""><figcaption><p>Arc that is 60 wide and 40 tall with a Thickness of 8, a Start Angle of 90 and a Sweep Angle of 270</p></figcaption></figure>

{% hint style="info" %}
The stretched Arc on MonoGame, KNI, and FNA is available in November 2026, or now if building Gum from source.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flatredball.com/gum/gum-tool/gum-elements/skia-standard-elements/arc.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.
