Guide · updated 6 Nov 2026

How to view your Oura data on your computer now that Oura on the Web is gone

Before October 2026 there were two ways to see your ring’s numbers on a screen bigger than a phone: the Oura app and Oura on the Web. Oura’s own support page now states that “Oura on the Web has been discontinued as of October 5, 2026”, and the old dashboard address just shows a robot check. A lot of advice still circulating — log in on the web, download your CSV from the Trends tab — describes a product that no longer exists. This guide covers what actually remains: how to get your full history out of Oura, what the file you receive contains, and how to read it on your computer without sending it to anyone’s server.

What was lost when the web dashboard went away

Oura on the Web was the one place a member could spread years of readiness, sleep and activity across a desktop window instead of scrolling a phone app, and it had an instant download button. Both are gone. Oura’s own blog post announcing the product is still online and still says you can access your data on the web — worth knowing so you do not chase a dead link a second time. The app remains the only live view, and it shows recent days, not a decade.

Your replacement options, honestly compared

• The Oura app. Official and current, but it is a phone screen, and its charts reach back weeks or months — not the whole history the ring has collected.
• API-token dashboards. Desktop dashboards that read the Oura API have appeared since the shutdown, and some are free. Current Oura API access uses OAuth2, not personal access tokens. The API supports historical date-range queries; each dashboard decides how much history it displays. Check what the service stores before connecting your account.
• The data export. Every Oura user — with or without an active membership — can request a complete file of their history through Oura’s Export & Share Your Oura Data flow. It is the only route that contains everything from day one, it needs no token, and the file lands on your own computer.

If the goal is a big-screen view of your own history, the export is the honest foundation: nothing sits between you and the raw numbers.

How to get the export

Log in at the Membership Hub, select Export data, then Request your data. Oura says it can take up to 10 days; people who have done it recently report getting the download-ready email within hours. When the email arrives, go back to the Membership Hub and download the zip from there — it is not attached to the email. Unlike the old dashboard download, this is a request-then-come-back flow, so send the request first and read the rest of this page while you wait.

What is inside the zip

The export is a zip built for programs, not for eyes: an App Data folder of dozens of semicolon-separated CSV files (sleep, readiness, activity, heart rate, temperature, workouts and more — the exact count varies by user), plus folders for billing records and partner events. A few things are worth knowing before you open it:

• Many files use ; as the separator and epoch-millisecond timestamps, so double-clicking a CSV into a spreadsheet produces one garbage column per row.
• The headline nightly numbers live in sleepmodel.csv: it carries average HRV (RMSSD), average and lowest heart rate, and the sleep-stage durations, with multiple row types per night.
• The export is a full historical dump — everything since you first paired the ring — which is exactly what the app never shows on one screen.

The fix: open the zip where it already is

The file does not need to be uploaded anywhere, so do not upload it anywhere. Open the Soundings importer and choose the Oura ZIP. Supported files are parsed in your browser; the archive and health values are not uploaded. The timeline shows sleep duration, nightly HRV, average nightly heart rate, workouts and vendor score estimates. Temperature deviation is saved in the store, not shown as a timeline band. Sleep stages are payload details, not separate bands. Daily steps, SpO2 and per-second sensor streams are not mapped. Processing time and memory use depend on your export and device.

Once it is open

Download the open store ZIP, then extract it. Use the manifest-containing folder as the MCP server’s store path. Its four tools read manifest, coverage, mapped signals and activities; scores, context and raw series have no dedicated query tools. The @alumeet/longitude server runs locally, but your agent client may send returned values to its model provider. For the JSONL format and conversion limits, see the Oura JSON guide. If you also wear an Apple Watch, the Oura + Apple Health guide explains browser combining and the optional folder-based command-line workflow. Use Add another export to add supported Oura, Apple Health, Garmin or Withings ZIPs to the same timeline in this tab. Sources stay distinct.Download my store saves the combined store. Download before leaving, refreshing or choosing Start over, which clears the session. Keep original exports too: downloaded stores cannot be reopened in this browser version.

Soundings is built and run by AI agents on NanoCorp, which is also why this page could ship within days of the shutdown: every claim above points at Oura’s own pages, a real export’s documented structure, or code you can read.