Private viewing entry points for more than 70 file extensions

One workspace, different viewing engines

SovaSpace provides built-in entry points for more than 70 extensions across documents, images, source code, archives, medical imaging, design files, data files and learning packages. The goal is to reduce unnecessary exporting when a user needs to inspect a protected attachment.

The current matrix includes familiar formats such as PDF, EPUB, DOCX, XLSX and PPTX, plus specialist categories such as DICOM, DXF, common 3D formats, PSD, SQLite databases, Jupyter notebooks, Anki packages, XMind maps and fonts.

“Supported” needs a precise meaning

An extension appearing in the viewing matrix means SovaSpace has a defined entry point for that format. It does not mean every historical version, embedded macro, codec, encryption scheme, malformed file or application-specific feature will render perfectly.

Support can mean different things:

• Native reading surface: a focused in-app experience such as PDF, EPUB or supported media.
• Structured preview: an in-app rendering of selected document or data structures.
• View-only inspection: content can be examined but not edited in its original format.
• System-assisted opening: the platform or an installed component may be required.
• Unsupported variant: the extension is recognized, but the particular file cannot be parsed safely or completely.

Privacy benefit of in-workspace viewing

Keeping a file inside the encrypted workspace can reduce the number of plaintext copies created merely for inspection. When the file can be viewed locally, the user does not need to upload it to an unrelated online converter.

This benefit has limits. Some rendering components operate under platform rules, temporary files may be required, and choosing “open with” or exporting plaintext transfers the copy into another application's security boundary.

Search should not fail silently

For supported PDF, EPUB, DOCX and XLSX search, SovaSpace separates a confirmed empty result from an incomplete search. A parser failure, unsupported structure or interrupted operation should not be reported as proof that the term does not exist.

Privacy-safe diagnostic bundles use allowlisted device, stage, count and error categories. They are not designed to include content, keys, tokens or attachment bytes.

File size and complexity still matter

A recognized extension can still exceed available memory, local storage or practical rendering limits. Very large files may be better handled through a specialized workflow, and encrypted cloud objects may need to be fetched before local inspection.

A broad viewing matrix reduces tool switching; it does not replace the authoritative application for editing every specialist format.

Check the product's current platform behavior with a representative file before making SovaSpace the only path for a critical workflow.