Your MacDive library, elevated.

On macOS, point the importer at your MacDive folder — the picker pre-navigates to ~/Library/Application Support/MacDive for you. DeepSix finds the database inside it, and because it holds the whole folder, it can also reach the sibling image folders: gear photos, site reference images, and critter thumbnails all come across. Selecting only the lone .sqlite file still works, but imports dives only.

Already did a dives-only import, or imported on iPhone or iPad first? File → Import Photos from MacDive Folder… runs just the photo pipeline against the dives you already have — matched by source ID, deduplicated by source key and perceptual hash, nothing imported twice.

We aim to capture every user-facing field from every dive record. Depth, temperature, gas mixes, decompression data, CCR setpoints, scrubber times, weather, conditions, boat names, divemasters, operators, ratings, notes. Even the raw binary dive computer data is kept for future reanalysis.

The two columns we deliberately skip are Z_ENT and Z_OPT — Core Data internal housekeeping values with no user content. Dive logs accumulate quirks over years, so if something doesn't come across the way you expect, that's a bug we want to hear about.

MacDive stores dive computer profiles as opaque binary blobs — it can display them, but it can't tell you what's in them. DeepSix decodes them.

Suunto and older Shearwater profiles (ZSAMPLES V1): natively parsed into per-second depth, temperature, pressure, CNS, and NDL sample streams.

Newer Shearwater profiles (ZSAMPLES V4, Perdix 2 recent firmware): decompressed from LRE+XOR encoding and parsed at the native 32-byte record level.

For 30+ other dive computer brands, libdivecomputer extracts samples, decompression models, dive modes, and GPS coordinates that MacDive itself couldn't surface. The raw binary is always preserved in DiveProfile.rawData for future re-parsing if the format becomes better understood.

If you dive with a Shearwater Swift AI transmitter, your dive computer recorded GPS coordinates at entry and at exit. This data sits in the compressed binary ZRAWDATA of every Shearwater dive in your MacDive database.

MacDive has never extracted it. DeepSix does — from every historical Shearwater dive in your import, automatically. Entry and exit coordinates are written to your dive site, placed on the map, and used to geolocate every matched photo.

MacDive tracks which photos belong to which dives using internal event timestamps — the time offset from dive start when you took the shot. DeepSix uses those timestamps as a starting point, then scans your entire Photos.app library — not just photos MacDive knew about. If you shot with a Sony A7C II that never synced to MacDive, those photos can be matched too — photos from any camera you own, linked to the dive they belong on.

DeepSix places each matched photo on your dive profile chart at the exact depth and time it was taken. Underwater videos are matched with the same precision. Critter identifications you recorded in MacDive are reconnected to the photos they were originally attached to.

Dive logs accumulate quirks over years, and some damage predates DeepSix — MacDive keeps only the first segment's raw data for merged split dives, and old imports could leave zeroed depths or durations behind. Two Data Tools repair from the source, matching dive by dive and only filling in where your log is missing or clearly wrong: