Skip to content

Editor and storage tools

Respawn Studios edited this page Nov 15, 2026 · 1 revision

Editor and storage tools

A lightweight editor beside your files

Open an eligible local, SFTP, SMB or ZIP document with Edit in Traverse. Opening preferences choose which supported types use the editor. Documents can use native tabs or separate windows.

Syntax colours cover common code, configuration and markup formats. JSON/JSONC formatting, indentation, bracket completion, Find/Replace and line commands have their own controls in Editor Defaults. They help you edit; they don't execute code or replace a language server.

Remote Save stays tied to the connection and original file. If the server's copy changed, Traverse can refuse the stale Save while keeping your edited text. Saved Versions offers offline read-only review. A ZIP text Save uses the archive update review instead of a separate remote write.

Find the space worth investigating

Open Storage Analysis for a folder to see charts, largest items and groupings. Scans enumerate metadata. Logical size and allocated size describe different things; neither promises how much space deletion will free, especially with clones, hard links and snapshots.

A saved result keeps its scan date. Reopening it doesn't start a new scan. Refresh can reuse eligible observations; Scan Every Folder requests complete traversal. Forget removes the analysis, not the files it described.

Drives, health and benchmarks

Drives groups volumes, health, benchmarks and analysis. Selecting a device doesn't start a write test. SMART values need hardware and enclosure support, so an unavailable reading is never presented as a healthy result.

Live health monitoring is opt-in and limited to supported internal drives. The date and availability of a reading matter. USB bridges, Hackintosh drivers and other hardware can expose different information.

A benchmark needs a writable folder and an explicit Start. It writes and verifies Traverse's own scratch file; Stop and cleanup remain part of the flow. Compare matching completed workloads rather than treating a cached result as raw-disk speed.

Formatting, partitioning and physical APFS volume changes are not ordinary available workflows. Use Disk Utility for those tasks. See the feature guide for the current limits.

Clone this wiki locally