Supported Cloud Services
Necron Vault Manager works with any cloud storage provider that syncs files to a local folder on your computer. The app never communicates directly with cloud APIs — instead, it reads and writes encrypted files to local folders that your cloud provider's desktop client syncs automatically.
How Cloud Integration Works
Necron's cloud integration is sync-client-based, not API-based:
- You install the cloud provider's desktop sync client (e.g., Dropbox, Google Drive, OneDrive)
- The sync client creates a local folder on your computer that mirrors your cloud storage
- You add that local folder as a vault storage location in Necron Vault Manager
- Necron writes encrypted files (
.ncrn/ NCV2/NCV3 objects) to the folder - The sync client automatically uploads the encrypted files to the cloud
This means any cloud service with a desktop sync client is compatible with Necron Vault Manager.
Tip
Because Necron encrypts files before they reach the sync folder, the cloud provider never sees your plaintext data. File contents, names, and directory structure are all encrypted. The provider only stores opaque encrypted blobs.
Officially Tested Providers
The following providers are explicitly supported in the Create Vault wizard with dedicated provider buttons:
Dropbox
| Detail | Value |
|---|---|
| Sync client | Dropbox Desktop App |
| Default sync folder | C:\Users\ |
| Setup | Install Dropbox → sign in → select a subfolder as vault location |
Dropbox syncs individual file changes efficiently, which works well with Necron's per-file encryption model. Each encrypted object is a separate file, so only changed files are re-synced.
Google Drive
| Detail | Value |
|---|---|
| Sync client | Google Drive for Desktop |
| Default sync folder | Mounted as a virtual drive (e.g., G:\My Drive\) or C:\Users\ |
| Setup | Install Google Drive for Desktop → sign in → select a subfolder as vault location |
Note
Google Drive for Desktop offers two modes: Mirror (files stored locally) and Stream (files downloaded on demand). For best results with Necron, use Mirror mode for your vault folder to ensure all encrypted files are available locally. Stream mode may cause files to appear offline.
OneDrive
| Detail | Value |
|---|---|
| Sync client | OneDrive (built into Windows) |
| Default sync folder | C:\Users\ |
| Setup | OneDrive is pre-installed on Windows → sign in → select a subfolder as vault location |
Note
OneDrive has a Files On-Demand feature that can offload files to the cloud. Ensure your vault folder is set to "Always keep on this device" so encrypted files are available locally for Necron to read.
Other Compatible Providers
Any cloud service with a local sync folder works with Necron. Here are some known-compatible options:
| Provider | Sync Client | Notes |
|---|---|---|
| iCloud Drive | iCloud for Windows | Use the local iCloud Drive folder |
| pCloud | pCloud Drive | Virtual drive or local sync folder |
| Sync.com | Sync.com Desktop | End-to-end encrypted provider + Necron encryption = double protection |
| MEGA | MEGAsync | Local sync folder |
| Tresorit | Tresorit Desktop | Another E2E-encrypted provider; Necron adds an additional encryption layer |
| Nextcloud | Nextcloud Desktop Client | Self-hosted cloud option |
| Box | Box Drive | Enterprise cloud storage |
| SpiderOak | SpiderOak ONE | Zero-knowledge cloud storage |
Tip
Using a cloud provider that already offers encryption (like Tresorit or Sync.com) with Necron creates a double encryption setup — the provider encrypts your already-encrypted Necron files. This is redundant but not harmful, and some users prefer the belt-and-suspenders approach.
Setting Up a Cloud Location
To add a cloud-synced folder as a vault location:
- Ensure the cloud provider's desktop sync client is installed and running
- In Necron Vault Manager, create a new vault or add a location to an existing vault
- Click the appropriate provider button (Dropbox, Google Drive, OneDrive) or Local for other providers
- In the folder picker, navigate to your cloud sync folder
- Select or create a subfolder for the vault (e.g.,
Dropbox/NecronVault/) - The folder is now a vault location — encrypted files will be written here and synced automatically
Warning
Do not place a vault location inside another vault's storage folder. Necron detects nested vault locators and rejects them to prevent conflicts.
Best Practices for Cloud Locations
Use Dedicated Subfolders
Create a dedicated subfolder for each vault rather than using the sync root:
Dropbox/
├── NecronVault-Work/ ← Vault location for work vault
├── NecronVault-Personal/ ← Vault location for personal vault
└── (other Dropbox files)
Avoid Selective Sync Exclusions
Don't exclude your vault folder from syncing. If the cloud client stops syncing the folder, Necron treats that location as offline and self-healing can't repair it.
Monitor Sync Status
After encrypting or importing files, check that the cloud sync client shows the upload as complete. Large files may take time to sync, especially on slower connections.
Combine Cloud with Local
For the best redundancy, configure each vault with at least:
- One local folder (fast reads/writes, always available)
- One cloud folder (off-site backup, accessible from other devices)
See Adding Locations and Best Practices for detailed location strategy advice.
Troubleshooting
| Issue | Solution |
|---|---|
| Cloud location shows as "offline" | Check that the cloud sync client is running and signed in |
| Files not syncing to cloud | Verify the folder isn't excluded from sync; check sync client status |
| Slow vault operations on cloud folders | This is normal — cloud-synced folders have higher latency. Use a local primary location for speed. |
| "Files On-Demand" / "Smart Sync" issues | Disable on-demand features for your vault folder so files are kept locally |
| Sync conflicts (duplicate files) | Necron uses unique filenames to avoid conflicts. If they occur, run a vault integrity check |
Further Reading
- Adding Locations — add cloud and local folders to a vault
- Vault Integrity Check — verify files across all locations
- Self-Healing & Repair — automatic cross-location repair
- Best Practices — location strategy recommendations