Resumable encrypted workflows for large files

No artificial plan-based file ceiling

SovaSpace does not add a separate subscription-tier single-file ceiling for ordinary attachments. That does not mean file size is unlimited. Practical capacity remains bounded by the connected Google Drive quota and APIs, device storage, filesystem, memory, codec and network conditions.

The useful distinction is between an artificial product limit and the real limits of the systems handling the file.

Encrypt before the cloud transfer

Attachment bytes are encrypted on the authorized device before upload. The cloud object is not a plaintext copy waiting for a later protection step.

Large transfers keep durable progress and resume information where supported. If the network disappears or the application restarts, completed work does not always need to be repeated from the beginning.

Honest pending state

An Entry can exist locally while one of its large attachments is still pending, retrying or blocked by quota. SovaSpace reports those states separately instead of presenting the entire operation as finished.

Before switching devices or relying on the cloud copy, users should confirm that required upload and synchronization work has completed.

Start compatible cloud video before the full download

For supported encrypted cloud video, the client can request and decrypt only the needed portions—technically, byte ranges—rather than downloading the whole object before playback starts. Seeking to a new section can trigger another request for that part of the encrypted file.

The result depends on the container, codec, indexing layout, platform decoder, network and Google API behavior. A format that requires information near the end of a file can still need additional ranges before playback becomes usable.

Local storage is a separate constraint

Cloud quota and device capacity are not interchangeable. A Google account may have room for a large encrypted object while the current phone or computer lacks enough local space for a complete offline copy, temporary processing or export.

SovaSpace reports cloud and local storage separately so the user can diagnose the actual constraint.

Back up the objects, not only the index

A recovery database can describe a large attachment without containing all of its encrypted bytes. For an independent recovery plan, retain the required encrypted object mirror in addition to the verified control package and Root Key.

A resumable upload improves reliability; it is not proof that the remote object is complete until verification and synchronization finish.

Use representative large files to test the exact platform, codec, network and recovery workflow that matters to you.