Support

Tap Capture from the palette library to open the viewfinder. Point the camera at what you want to sample - the loupe magnifies the sample point and the readout pill shows the live hex and RGB value beneath it. Tap the large eyedropper button to collect the colour.

Auto-exposure and auto white balance are the most common reason a sampled colour is off. Tap Lock to freeze exposure and white balance before you sample, or open the manual controls (the top-right reveal) to adjust exposure bias and white-balance temperature by hand. For full control over lighting, use the photo eyedropper instead of the live camera.

Yes. Tap the photo-library button in the capture control row to import an image, then drag the zoomed loupe to place the crosshair on the exact pixel you want. The photo path preserves the image's embedded colour space (including Display P3), so wide-gamut colours are sampled faithfully.

Yes. Manual entry accepts hex, RGB, HSL, and HSB. It's the precise path when you already know the value you want - no camera required.

Switch to multi-sample mode with the grid toggle. In multi mode the photo button becomes extract-from-image, which proposes a set of colours you can keep, drop, or fine-tune before saving. Collected colours gather in the capture tray, where you review them and save the set to a new or existing palette.

Tap the + button on the palette library, or save a set of captured colours to a new palette from the capture tray. Give it a name and it appears in your library.

Open a palette and use Edit to rename it, drag swatches to reorder them, and add tags. Individual swatches can be renamed and given per-swatch notes from the swatch detail view.

Free users can keep up to 3 palettes. Capture is never limited - only the number of saved palettes. Gamut Pro lifts the cap entirely. Creating and organising a palette works fully on the free tier; the limit is on count only.

Swatch detail shows the nearest name from the CSS Color Module Level 4 keyword list - the closest of the 148 standard web colour names to the one you captured. It is a description, not your own label: the name you give a swatch stays in the navigation title, and the nearest-name cell sits with the values below it.

Open any swatch and tap Generate. Generation is always from a colour, so the swatch you opened is the base. The screen has a Harmony | Ramp toggle, so you can compare both derivations of the same colour without backing out. Generation is a Gamut Pro feature.

Five: complementary, analogous, triadic, split-complementary, and tetradic. Ramp mode needs no selector - it produces a ten-step tonal scale from your base colour, preserving the base exactly at its nearest step.

There is no monochromatic scheme, because the tonal ramp is that feature done properly.

Every generated colour starts selected - if you asked for a triad you probably want the triad - and deselecting is one tap. Keeping appends the selected colours to the base swatch's own palette, and Gamut takes you to that palette so you can see them, rather than showing a message about them. There is no palette picker and no second paywall in the flow.

The ramp's base step is shown so you can see where your colour sits in its own ramp, but it can't be selected - adding it would duplicate a swatch the palette already has.

Harmony works by rotating hue, and a colour at or near zero chroma - a grey, a black, a white - has no hue to rotate. Rather than show you an empty grid, Gamut says so and points you at Ramp mode, which works perfectly well on a grey. It is a fact about the colour, not an error.

Both generators compute in OKLCh and bring their output into gamut by reducing chroma perceptually, holding lightness and hue. That matters most at a ramp's light and dark ends, which routinely fall outside the destination gamut - a plain clamp would flatten them. Where a colour was brought in, Gamut shows you that it was.

Pick a foreground and a background colour - from a palette or by entering a value - and Gamut shows the WCAG contrast ratio between them, with pass/fail verdicts for AA and AAA across normal text, large text, and UI components. The contrast checker is free, forever, and never gated.

Gamut's colour engine linearises sRGB using the modern IEC 61966-2-1 transfer function. Some tools follow the older WCAG 2.x draft threshold, which differs by a hair near the boundary. The two agree to within a fraction of a percent; the pass/fail thresholds (4.5, 7.0, 3.0) are exact, so verdicts match.

Yes, from 1.1, as a Gamut Pro feature. Tap a failing verdict chip in the contrast checker and Gamut solves for the nearest colour that meets that criterion - a fix for AA-large is not a fix for AAA-normal, so you choose which one you are aiming at. You also choose which colour moves, foreground or background; foreground is the default, being the half you can usually change.

The search runs along the lightness axis in OKLCh with hue held exact, so the suggestion is the smallest perceptual move that genuinely passes. Where both a lighter and a darker answer exist, both are shown nearest-first with the ratio each reaches, because the distance between them is often large and a big correction shouldn't be dressed up as a small one.

Some pairs cannot reach the target by moving one colour alone. Gamut says so and offers the next step - try moving the other colour, or aim at a lower level - instead of showing you an empty list.

No. The contrast checker is a scratchpad, and its two colours need not be swatches at all. Applying a suggestion sets the checker's own foreground or background so you can carry on checking. Nothing is written to your library.

Yes. From 1.1, tapping a failing row in the palette accessibility audit opens that exact pair in the contrast checker, where the correction lives.

One deliberate detail: the audit judges from the exact ratio and the checker displays and judges from the ratio rounded to two decimal places. For a pair sitting within a hundredth of the threshold, an audit row marked failing can therefore open a checker reading, say, 3.00 - Pass, with no fix offered. Each surface is internally consistent - the audit is the strict instrument, the checker the honest display - and the alternative would put a Fail chip beside a number that reads as a pass.

Yes, and 1.1 improved it considerably. Option pickers throughout the app now scale with Dynamic Type - below accessibility sizes they look exactly as they always did, and at accessibility sizes the options expand in place into selectable rows. Rows whose text column can no longer hold a value reflow into a column rather than breaking a hex code or a word in half.

A Pro feature. Gamut simulates the common colour-vision-deficiency types across a single swatch or a whole palette, using a published simulation model, so you can see how your colours read to people who perceive colour differently. The palette accessibility audit runs contrast checks across every pairing in a palette and flags the ones that need a darker or lighter partner.

Per swatch, you can copy hex, RGB, HSL and HSB for free; the code formats - SwiftUI Color, UIColor, CSS, and oklch() - are Pro. Per palette, the export ladder covers:

• Hex list (free)
• CSS custom properties
• OKLCH (added in 1.1)
• SwiftUI Color extension
• Tailwind config
• JSON
• A swatch-sheet PNG and an Xcode asset catalog
• Adobe .ase swatches (added in 1.2)
• GIMP .gpl palettes (added in 1.2)
• W3C DTCG design tokens (added in 1.2)

Thirteen formats in all: three free, and ten developer formats in Gamut Pro.

OKLCH is the CSS Color 4 perceptual notation - oklch(L C H) - and it arrived as a Pro copy row and a Pro export rung in 1.1. It is the only value on the swatch card that carries the colour's own space rather than an sRGB mapping of it, which is exactly why it is there: it can express a colour sRGB cannot hold.

For the same reason it sits outside the sRGB / Display P3 export toggle. OKLCH is device-independent, so it always emits the swatch's true colour - a toggle there would offer a choice whose only honest setting is off.

It controls the colour space the exported values are written in. Under sRGB, any colour that falls outside the sRGB gamut is clamped, and Gamut shows a note telling you exactly how many colours were affected - so a wide-gamut colour is never silently narrowed without your knowledge. Choose Display P3 to keep the full gamut where your target supports it.

Tap the copy affordance on any swatch row to copy its hex, or open the swatch detail for hex, RGB, HSL, and HSB - each with its own copy button. A quiet toast confirms the copy.

The palette widget is a Pro feature. Long-press your iPhone home screen until the icons wiggle, tap the + at the top left, search for Gamut, and add the widget. Tap it to configure which palette it shows. The widget renders in Display P3 where your device supports it.

Sync is a Pro feature. It uses your private iCloud account (CloudKit) to keep your palettes and swatches in sync across your own devices. There is no Gamut server - the developer cannot see your data. Free users run Gamut as an independent local app on each device.

Yes. Everything saves locally the moment you capture it. On Pro, CloudKit queues changes and syncs when you're back online. Your palettes are always available whether or not you have a connection.

Yes. Gamut can export a library archive and restore it. Restoring is treated as retention, not creation - so a free user can restore an archive of more than three palettes and keep them all. Data portability is never gated.

Pro unlocks:

• Unlimited palettes
• The full export ladder - ten developer formats, including SwiftUI, CSS, OKLCH, Tailwind, .ase, .gpl and design tokens
• The Pro per-swatch copy formats, including oklch()
• iCloud sync across your devices
• Colour-vision simulation and the palette accessibility audit
• Harmony and tonal-ramp generation
• Contrast correction - the suggested fix for a failing pair
• The home-screen palette widget
• The alternate app icon (added in 1.2)

$19.99 a year, with a 7-day free trial for new subscribers, or a one-time lifetime unlock at $39.99 - exactly two years of the annual plan. The lifetime tier exists because a tool you own shouldn't nag you with recurring billing, and it carries no trial because there is nothing to try before: you simply own it. Prices are shown in your local currency at purchase time.

A monthly plan was offered briefly at launch and is no longer sold. If you subscribed monthly before it was withdrawn, nothing changes - your subscription continues to renew as normal until you cancel it.

Nothing is deleted. When you try to create a fourth palette, Gamut prompts you to upgrade. Your existing palettes remain fully accessible. You can delete a palette to make room, or upgrade to Pro to keep adding.

Nothing is deleted. If you had ten palettes under Pro, you keep all ten - fully visible and usable. You simply can't create a new one until you're back under three palettes or re-subscribed. Sync stops and the app reverts to a local library, but your data is untouched. Re-subscribing restores everything instantly.

Open Settings → Gamut Pro (or the paywall) and tap Restore Purchases. Make sure you're signed in to the same Apple ID that made the original purchase. This is essential for a lifetime buyer setting up a new device.

Subscriptions are managed through Apple. On your iPhone, go to Settings → [your name] → Subscriptions, find Gamut, and tap Cancel. Your Pro features stay active until the end of the current billing period. The lifetime purchase is permanent and cannot be cancelled.

Yes. The lifetime unlock is enabled for Family Sharing. Subscriptions follow Apple's standard Family Sharing behaviour.