diff --git a/Setting-Up-Storage.md b/Setting-Up-Storage.md
index 28643c2..5122560 100644
--- a/Setting-Up-Storage.md
+++ b/Setting-Up-Storage.md
@@ -35,11 +35,15 @@ services:
+
+
### `EXT4` (default on Linux), `APFS` (default on macOS)
> [!TIP]
> These default filesystems are fully supported by ArchiveBox on Linux and macOS (w/wo Docker).
+
+
### `ZFS` (recommended for best experience on Linux/BSD) ⭐️
> [!TIP]
@@ -80,11 +84,15 @@ zfs create \
-o keysource=passphrase,prompt \
```
+
+
### `NTFS`, `HFS+`, `BTRFS`
> [!WARNING]
> These filesystems are likely supported, but are not officially tested.
+
+
### `EXT2`, `EXT3`, `FAT32`, `exFAT`
> [!CAUTION]
@@ -95,6 +103,7 @@ zfs create \
---
+
## Supported Remote Filesystems
@@ -111,6 +120,8 @@ The `data/archive/` subfolder contains the bulk archived content, and it support
> If you use a remote filesystem, you should switch ArchiveBox's search backend from [`ripgrep`](https://github.com/ArchiveBox/ArchiveBox/wiki/Setting-up-Search#ripgrep) to [`sonic`](https://github.com/ArchiveBox/ArchiveBox/wiki/Setting-up-Search#sonic) (or [`FTS5`](https://github.com/ArchiveBox/ArchiveBox/wiki/Setting-up-Search#fts5)).
> (`ripgrep` scans over every byte in the archive to do each search, which is **slow and potentially costly** on remote cloud storage)
+
+
### `NFS` (Docker Driver)
`docker-compose.yml`:
@@ -129,6 +140,8 @@ volumes:
device: ":/archivebox-archive"
```
+
+
### `SMB` / `Ceph` (Docker CIFS Driver)
`docker-compose.yml`:
@@ -152,6 +165,8 @@ volumes:

+
+
### Amazon S3 / Backblaze B2 / Google Drive / etc. (RClone)
```bash