# Storage Explorer Inspect and edit AsyncStorage, registered MMKV instances, and registered SecureStore keys. Use the backend filter to choose the data you want to inspect. ## Supported Backends > **Multi-instance MMKV support** — If you use multiple MMKV instances, register each instance explicitly. Switch between instances and see key counts per instance. --- ## Installation After setting up [Buoy core](../quick-start), install this package and restart Metro. AsyncStorage can be discovered automatically; register MMKV instances and SecureStore keys below. ### SecureStore setup Expo SecureStore (iOS Keychain / Android KeyStore) has no key-listing API, so register the keys you want visible — pass the module in, no extra dependency needed: ```typescript import * as SecureStore from "expo-secure-store"; import { registerSecureStoreKeys } from "@buoy-gg/storage"; registerSecureStoreKeys(SecureStore, [ "auth.accessToken", { key: "session", keychainService: "com.myapp.auth" }, // Biometric-protected keys are listed but never auto-read (no surprise Face ID prompts) { key: "pin", requireAuthentication: true }, ]); ``` ### MMKV setup Register the same instance your app reads and writes. For MMKV v4: ```typescript import { createMMKV } from "react-native-mmkv"; import { registerMMKVInstance } from "@buoy-gg/storage"; export const storage = createMMKV({ id: "mmkv.default" }); registerMMKVInstance("mmkv.default", storage); ``` If your app already creates this instance, add the registration beside that code instead of creating another instance. Give each registered instance a distinct name. To verify setup, write a disposable test key through your app, find it in Storage, edit it, and read it back through your app. Delete the test key when finished. Registered values are re-read every few seconds while the browser is open, so a secure write shows up without reopening the tool. AsyncStorage and MMKV writes are picked up the moment they happen; the keychain gets a poll instead because it has no change notification of any kind. --- ## What You Can Do --- ## Smart Features **Edit values in place** — Expand a key and hit *Edit value* to write a new one straight to the device. Types are preserved: an MMKV number stays a number, a boolean only accepts `true`/`false`, and a key holding JSON has to stay valid JSON — so you can't silently turn an object into a quoted string. Buffers, read-only MMKV instances, and biometric-protected SecureStore keys say why they can't be edited instead of offering a broken field. **Edit arrays and objects without typing JSON** — Tap any node in the value tree and its actions appear alongside the key's other buttons: arrays get append, duplicate, reorder and remove; objects get add-key, duplicate and remove; scalars get a text field, with booleans as a two-way toggle. Use the raw text editor when you want to paste a complete value. **Inline value previews** — Short values show right on the card (`number · 42`, `string · "en"`), and booleans get a color-coded true/false badge. No need to expand to see simple values. **Pin to top** — Pin the keys you're watching so they stay at the top of the list. Pins persist across sessions. **Hide from list** — One tap filters noisy keys out of the browser (from the expanded card or bulk selection). Non-destructive — unhide any time from the filters panel. **JSON formatting** — Values that are valid JSON are automatically pretty-printed for readability. **Live events** — Watch storage changes happen in real-time as your app reads and writes data. **Bulk selection** — Select multiple keys to delete or export them all at once. --- ## What's Next - [Network Monitor](./network) — Inspect supported HTTP requests - [Environment Inspector](./env) — Validate env vars with type checking - [React Query](./react-query) — Inspect query cache and simulate states --- ## FAQ ### How do I view AsyncStorage contents in Expo? Install `@buoy-gg/storage` and open the Storage tool from the floating menu — all AsyncStorage keys are browsable and editable on the device, including in Expo Go. ### Does it support MMKV? Yes. Register each MMKV instance, then select it with the backend filter. SecureStore requires explicit key registration too. ## Web support The browser uses localStorage and sessionStorage with the shared editor, event history, undo, and snapshots. Native secure storage is unavailable on web. Import it from the package's `/web` entry (7.0.41 or later). See [Web installation](../web/installation#tool-setup) for registration, dependencies, and browser boundaries. ## Swift backends The Swift port maps `async.*` to the app's UserDefaults domain and `secure.*` to registered keychain items. `getRequiredKeys` returns the configuration from `BuoyStorageModule.configure(requiredKeys:)`. Register existing native MMKV instances with `BuoyMMKVRegistry.shared.register(...)`. Each registration supplies typed reads, writes, removals, and its encryption/read-only flags. The Storage browser and MCP use the same registration. Call `refresh(instanceId:)` after app writes to record changes; Buoy writes refresh automatically. The SDK does not add an MMKV dependency. See the [Swift integration guide](https://github.com/Buoy-gg/Buoy-Swift) for the host integration. MMKV values keep their string, number, or boolean type. Binary values show their byte count. Read-only stores reject edits, and internal Buoy keys are filtered out. Storage history undo/jump supports UserDefaults only. For Swift setup and what the native version covers, see the [Swift tools guide](../swift/tools#storage). Buoy keeps its own keys out of this view. Counts and saved app state leave them out too.