SimpleumSafe · Blog

Move from Boxcryptor to SimpleumSafe on Apple devices

SimpleumSafe can be a suitable Boxcryptor alternative if you use only Mac, iPhone, and iPad and want an encrypted archive with its own file manager. It is not a drop-in replacement for Boxcryptor’s virtual drive or transparent cloud-folder workflow.

Boxcryptor states that its operations were discontinued on December 31, 2025. Dropbox had acquired several Boxcryptor assets in December 2022. If you still have Boxcryptor-encrypted data, preserve your ability to decrypt it before removing the old software, account, keys, or source files.

Mac & i magazine logo

"If you only use Apple devices, SimpleumSafe 3 is a worthy replacement for the discontinued Boxcryptor."

Mac & i 1/2024

View purchase options 7-day free trial

Is SimpleumSafe a direct Boxcryptor replacement?

No. Both products encrypt files on the device, but their workflows differ:

Boxcryptor workflow SimpleumSafe workflow
Exposed decrypted views of encrypted cloud folders through a virtual drive Imports files into a separate encrypted Safe with its own file manager
Worked across several desktop and mobile platforms Available for macOS, iPhone, and iPad; no Windows or Android version
Used existing cloud-provider folders as the main working location Stores the Safe locally and synchronizes encrypted change data through SimpleumSafe

Choose SimpleumSafe when an encrypted Apple-only document archive fits your workflow. Test it with a small Safe before migrating a large archive or a shared business process.

What SimpleumSafe protects

SimpleumSafe encrypts imported file contents and file attributes, including names, inside a Safe. The encrypted stored data uses non-meaningful identifiers. SimpleumSafe supports three synchronization methods:

  • iCloud synchronization between supported Apple devices;
  • wireless peer-to-peer synchronization without an internet service; and
  • shared-folder synchronization between Macs.

The normal synchronization target contains encrypted Safe data and encrypted change information, but not the separate Safe key file. This makes copied synchronization data plus the Safe password alone insufficient for decryption.

That boundary matters: protection also depends on keeping the Safe password, Safe key material, recovery material, and unlocked devices separate and secure. Synchronization is not a backup.

Important functional limits

  • Files are protected after they have been imported. The original source files remain where they were until you remove them deliberately.
  • Exporting or sharing a file creates a usable, decrypted copy at the destination you select.
  • On macOS, previewing or editing uses SimpleumSafe’s encrypted Secure Temporary Storage. An authorized editing app can access its working copy while the file is open.
  • The app does not impose a general file-size limit, but available device storage, file-system limits, synchronization capacity, and the 100 GB Secure Temporary Storage limit on macOS still apply.
  • SimpleumSafe does not replace device security, FileVault, tested backups, access control, or an organizational migration plan.

Read How SimpleumSafe works and the Technical White Paper for the product architecture and boundaries.

Migrate Boxcryptor files on a Mac

Do not import the still-encrypted Boxcryptor files directly. SimpleumSafe can only protect files after Boxcryptor has made their readable contents available.

  1. Preserve Boxcryptor access first. Follow Boxcryptor’s off-migration guidance. Keep the required installer and exported key material if they are still available to you.
  2. Create a separate backup. Do not delete or overwrite the Boxcryptor source during the migration.
  3. Check free space. You may temporarily need space for the encrypted source, decrypted working files, the new Safe, and a backup.
  4. Create and test a small SimpleumSafe Safe. Store it locally on the Mac, use a strong unique password, and secure the recovery material separately.
  5. Decrypt a manageable batch with Boxcryptor. Copy the readable files to a local working folder you control.
  6. Import that batch into SimpleumSafe. Open the Safe and drag the files or folders into its file manager.
  7. Verify before continuing. Compare file and folder counts, open representative files, and confirm that the Safe can be reopened after restarting the app.
  8. Repeat and back up the completed Safe. Configure SimpleumSafe synchronization separately if you need the Safe on another device.
  9. Remove old copies only after verification. Decide which encrypted and decrypted migration copies may be deleted according to your backup and retention requirements.

For a business archive, test permissions, shared workflows, recovery, storage capacity, and restore procedures before committing to the migration.

Primary and product sources

Continue with the SimpleumSafe system requirements or frequently asked questions.