Spacedrive
A cross-platform file-management Alpha that builds local libraries, indexes locations, searches and previews files, and maintains virtual filesystem metadata above the underlying operating system.
What Spacedrive 0.4.3 does
The 0.4.3 Alpha builds a local Library above existing folders, indexing locations for search, tags, thumbnails and previews. It is an experimental organization layer rather than a cloud backup and should not become the only entry point to irreplaceable data.
Version generations and data boundaries
The archived 0.4.3 Alpha and the current v2 development line represent different architecture and license generations. A Library stores indexes and metadata; it does not create a verified second copy of the source files. Database damage, changed paths or an offline drive can affect the view while the underlying file operations still touch real files.
Maintenance note
This page reviews Spacedrive 0.4.3 Alpha, platform packages, test Libraries, index databases, external media and the separate AGPL and FSL license generations. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Spacedrive to this cloud drive
Baidu Netdisk
Save Spacedrive to this cloud drive
Spacedrive 0.4.3 Alpha Library setup and safe trial guide
Use a copied test directory to create an isolated Library, verify indexing, search, previews and file actions, then back up the application database before evaluating broader use.
Before you start
- Prepare Windows x64, macOS Intel or Apple silicon, or Linux x64 with a test directory containing copied samples.
- Back up the originals independently and record file count, total size and sample hashes.
- Treat the downloaded version as 0.4.3 Alpha and keep its behavior separate from current v2 development documentation.
Installation steps
- 01
Select the 0.4.3 build
Use MSI on Windows, the matching DMG on macOS and a suitable Linux package, then verify the version before pointing the Library at any real data.
- 02
Create an isolated Library
Use a new Library name and database location, add only the prepared test directory, and watch CPU, disk and thumbnail use during the first index.
- 03
Record the database location
Find the application-data and Library database paths, close the app and make a copy. Indexes can be rebuilt, while tags and settings may exist only in the database.
Quick start
- 01
Compare the index with the filesystem
Compare file count, size, type and path with the system file manager, including hidden files, symbolic links, external drives and unsupported formats.
- 02
Test actions on copies
Perform rename, move, tag and delete operations only in the test directory, checking the real path and recycle-bin behavior after each action.
- 03
Rehearse an offline drive and restore
Safely unmount the test drive, inspect its offline state, then restore a database copy without changing the original directory and verify tags and indexes.
Usage tips
- Indexes, media previews and thumbnails parse files and create caches; limit the test directory and keep the operating system decoders current.
- Adding a directory to a Library is not a backup. Keep a separately verified offline or remote copy of important files.
- { "Match the license to the exact generation": "0.4.3 uses AGPL-3.0 while the current v2 line uses FSL-1.1-ALv2 with a later Apache transition." }
Troubleshooting and uninstall
Why does the indexed count differ from the filesystem?
Check ignore rules, permissions, symbolic links, offline locations and active indexing jobs, reproducing the issue in a small directory before changing a production Library.
Why do files look wrong after an external drive is disconnected?
Remount the same volume through the operating system, compare the label and path, then refresh the location. An offline index entry is not a recovered file.
- Preserve metadata and original accessSave important tags, settings and the Library database copy, and confirm every original file remains accessible through the system file manager and a separate backup.
- Uninstall and clean indexes selectivelyStop background tasks, uninstall the app and remove database, thumbnail and cache data only after confirming the old Library is no longer needed.
Frequently asked questions
Can Spacedrive 0.4.3 replace the system file manager?
It is an Alpha indexing layer that still relies on Finder, Explorer or the Linux filesystem for underlying operations. Keep another file-management path and a complete backup.
Can 0.4.3 upgrade directly to the current v2 line?
Treat them as different product generations until a verified migration path exists. Keep full backups and test them separately.
Does adding a folder to a Library complete a backup?
No. A Library stores indexes, tags and previews while the source may remain on one disk. Configure and verify an independent backup separately.