← The sleep editIMPORT FORMATS · 5 MIN READ

What can I actually import?

Tested schemas, older and newer variants, and the limits of each source. An export format matters more than a device model.

Choose a sleep file, not just any health export

Open a CSV, JSON response file, Apple Health XML, or supported export ZIP. You can also paste text into the studio. No account connection is made and no API credential is requested. A workout file, glucose reading, or time-in-bed field cannot establish time asleep.

Verified means a specific schema

The regression suite uses official published examples and clearly labeled fictional records derived from documented schemas. It checks exact dates, time units, sleep totals, stages, missing values, and archive handling. It does not establish support for every undocumented historical export.

When a CSV uses unfamiliar columns

Choose the date and time-asleep columns, the date order, and the duration units in the local mapping preview. Inspect the result before applying it. Optional bedtime, wake time, and stage columns can be mapped separately. Never substitute time in bed for time asleep.

Review warnings before interpreting patterns

Check skipped records, duplicate dates, naps, missing stages, and partial API pages. KnowNaps currently describes primary sleep records by date, keeping the longest when distinct sessions share a date; it reports discarded sessions. Retain your original export as the source of truth.

Source-by-source coverage

Reviewed September 27, 2026. API JSON below means a saved response file, not an automatic connection to your account. Unverified native formats may need CSV mapping or an Apple Health export containing actual sleep records.

Known sleep source formats and limitations
Source	Recognized format	Scope and limits
Oura	CSV, JSON	Sleep-summary CSV or v1/v2 sleep JSON. Current Membership Hub exports use v2 models; download durations are seconds.
Apple Health	XML	Import export.xml or a ZIP containing one Health export.xml. Only included sleep records are analyzed.
Fitbit	CSV, JSON	Classic/staged sleep JSON and February 2026 UserSleeps summary CSV. Separate stage files and algorithm_version variants are not supported.
Garmin Connect	JSON	Recognized sleep-summary JSON records. Binary FIT and workout CSV files are not sleep imports.
Samsung Health	Native schema unverified	Native archive schema unverified. Map sleep CSV columns and units using the File Description Guide supplied with your archive.
WHOOP	CSV, JSON	Sleep CSV or saved sleep API JSON; daily recovery and workout files are separate.
Withings sleep data	JSON	Saved Sleep v2 summary API JSON. Native consumer CSV header and unit variants remain unverified.
Polar sleep data	JSON	Saved AccessLink v3 or Dynamic v4 sleep API JSON. The account download is not a verified sleep import.
AutoSleep History	CSV	History CSV with recognized duration fields and ISO dates. Localized date formats and Actigraphy are unverified.
Google Fit	JSON	Saved com.google.sleep.segment API JSON. Session-only files and activity totals are not sleep measurements.
Health Connect	JSON	JSON containing explicit SleepSessionRecord fields. Native backup ZIP and FHIR records are not supported.
Sleep Cycle	Native schema unverified	CSV download exists; native schema variants are not yet verified. Use the custom sleep template if needed.
Ultrahuman	Native schema unverified	Native CSV and API sleep-value shapes are unverified. A generic sample does not establish compatibility.
Circular	Native schema unverified	Native export schema unverified. A platform export may work if it includes actual sleep records.
Xiaomi Mi Fitness	Native schema unverified	Account download exists; native sleep schema unverified. Mi Fitness and Zepp Life are different export routes.
Zepp / Zepp Life / Amazfit	Native schema unverified	Separate account exports; native sleep schemas remain unverified. Workout GPX is not sleep data.
Eight Sleep	Native schema unverified	Personal data requests are available; the native file schema has not been verified.