Tauri macOS localStorage lives in a WebKit SQLite file
On macOS, a Tauri app's WKWebView localStorage is stored at ~/Library/WebKit/<bundle-id>/WebsiteData/Default/<hash>/<hash>/LocalStorage/localstorage.sqlite3, along with -wal and -shm files. The origin file in the <hash> dir shows which origin it is (e.g. tauri / localhost). The schema is ItemTable(key TEXT UNIQUE, value BLOB), and values are stored as UTF-16LE. Read them with select hex(value) ..., then bytes.fromhex(h).decode('utf-16-le'), and encode the same way when you write. To read safely, copy all three sqlite files somewhere else first. Only write while the app is closed, and back up all three files before you do.
Related for Capacitor iOS apps planning a native migration: the WebView origin is capacitor://localhost by default, and if capacitor.config sets server.iosScheme to a scheme WKWebView already handles (e.g. 'https'), Capacitor's InstanceDescriptor.normalize() silently resets it to 'capacitor' (WKWebView.handlesURLScheme check), so the localStorage origin is still capacitor://localhost. A supported way to read it from native code is a one-shot WKWebView on WKWebsiteDataStore.default() with a WKURLSchemeHandler for 'capacitor' serving a blank page at capacitor://localhost/, then evaluateJavaScript on localStorage; reading the sqlite file directly is the brittle fallback.
Same layout on the iOS Simulator (iOS 26.2 and 26.5) for a Capacitor app: <app data container>/Library/WebKit/<bundle-id>/WebsiteData/Default/<salted-hash>/<salted-hash>/LocalStorage/localstorage.sqlite3, identical ItemTable(key TEXT UNIQUE, value BLOB) schema. The origin file lists scheme and host twice (top-frame origin, then frame origin), e.g. capacitor/localhost, so a native reader must load the origin as a top-level page. Because the dir names are salted hashes, prefer reading via a WKWebView on the default data store over opening the file.