Guide · Updated August 2026
Which Garmin watches can actually read depth in a Connect IQ app
"Reads depth" on a Garmin spec sheet and "reads depth in a third-party Connect IQ app" are two different claims. Garmin's native dive activity, on watches that have one, uses a dedicated sensor that Connect IQ apps never see. What a Connect IQ app like inDepth Apnea Blue gets instead is whatever pressure value the firmware hands to the Sensor API — and on several current Garmin watches, that value is capped at roughly 3 m no matter how deep you actually go. This page is a dated, sourced table of what we've actually measured, per watch, with the evidence tier for each row.
Measured, inferred and reported — three different tiers of evidence
Not every row below rests on the same kind of evidence, and we label each one rather than flatten them into one confident list. Measured means an instrumented dive or a pressure chamber run with a logged pressure or depth value and a date. Inferred means a watch that shares a sensor generation or case rating with a measured model, where the same clamp is expected but has not itself been dive-tested. Reported means a single field observation from a tester — useful, but weaker than an instrumented run, and never published with a pressure figure it doesn't have.
Connect IQ depth reading by Garmin watch
| Watch | CIQ depth reading | Evidence | inDepth |
|---|---|---|---|
| Descent Mk3i 51 mm | Saturates at 131,048 Pa ≈ 3.3 m | Measured — instrumented dive + recorded FIT file, both pinned at the same ceiling. | Blue + Pool (dive-time rest models only) |
| Fenix 8 Solar 47 mm | Tracked to 8.445 m in a pressure chamber, no saturation | Measured, in a pressure chamber — a single run, one firmware build. This shows self-consistency, not calibrated accuracy; no reference instrument was in the chamber, and no Pa ceiling is published for this reason. | Blue + Pool |
| Other Fenix 8 SKUs (43 mm, 47 mm, Pro 47 mm, Solar 51 mm) | Shipped as true-depth, same family as the tested Solar 47 mm | Not individually chamber-tested — no data on these specific SKUs. | Blue + Pool |
| Fenix 5 / Fenix 5 Plus family | Field-verified to 30 m, uncapped | Measured, in open water. (Not verified past 30 m — no ~42 m figure.) | Blue on all six; Pool on the Plus models only |
| Fenix 7 family | ~3 m (clamped) | Inferred from the measured Descent clamp — not dive-tested on a Fenix 7 itself. | Yes, dive-time rest models only |
| Descent Mk3 43 mm | ~3 m (clamped) | Same clamped family as the measured Mk3i; not separately instrumented. | Yes, dive-time rest models only |
| Descent Mk2 / Mk2S | ~3 m (clamped) | Reported by a tester. No pascal figure — not instrumented. | Yes, dive-time rest models only |
| Fenix 6, epix, MARQ, Forerunner, Venu, vívoactive | Unknown | No data. | Not supported — tell us your watch below |
"Can this watch read depth" and "does inDepth run on it" are two different questions, and the table above answers only the first one. A watch can have a barometric sensor and inDepth can still not run on it — the Fenix 6, epix, MARQ, Forerunner and Venu lines above have no measured or reported Connect IQ depth data at all and are not supported today. Separately, a watch inDepth does support can still have a clamped reading — the Fenix 7 family and both Descent lines still run inDepth Blue and Pool, just with the depth-driven surface-rest models hidden. Check the table's "inDepth" column, not just the reading, before assuming either one.
Why does Connect IQ depth stop at about 3 m on some Garmin watches?
It's a firmware policy, not a bug in any app. On watches with a dedicated dive sensor, Garmin routes that sensor to its own native dive computer and hands third-party Connect IQ apps only the surface-altimeter barometer, which is capped at around 131,048 Pa (about 3.3 m of water) on the Descent Mk3i, measured with an instrumented dive and a recorded FIT file. Descent Mk2 / Mk2S are reported to clamp the same way by a tester, though that has not been instrumented with a pressure figure. The Fenix 7 family is inferred to clamp near 3 m too, on the same reasoning, not from a Fenix-7-specific dive test.
Is the Descent a real dive computer even though its Connect IQ depth clamps at 3 m?
Yes — for its own native dive mode, which uses the dedicated deep-range sensor Garmin does not expose to Connect IQ. The 3 m figure only describes what a third-party app like inDepth can read live or record through Connect IQ. The Descent's own dive computer reads far past that; Connect IQ apps just cannot see it.
Does inDepth still work on a watch with a clamped depth reading?
Yes, with a smaller feature set. On a clamped watch (Fenix 7 family, Descent Mk2 and Mk3) inDepth still times dives, logs sessions and runs the surface-rest models that use dive time rather than depth — 2x, 3x and Manual. The depth-driven models (Adaptive/AIDA, Taravana, Molchanovs) are hidden on those watches because the reading cannot drive them safely.
This page is about what Connect IQ can read, not a claim about diving safety by itself. inDepth Apnea Blue is a freediving aid, not a medical device, and no surface-rest model removes the risks of freediving. See the surface intervals guide for what each rest model actually does.
Don't see your watch?
If your Garmin isn't in the table above, we don't have depth data for it and inDepth doesn't support it yet. Tell us the model and we'll email you if that changes — this isn't a program to join, it's just a "let me know" list for unsupported watches.
Own one of the supported watches already? Download inDepth and see your own watch's depth reading for yourself, or read what inDepth Apnea Blue adds on top of it.