SAV Inspector Deutsch
HomeKnow what is preserved before you open, edit or export.
Compatibility reference

Know what is preserved before you open, edit or export.

File compatibility is not a single yes-or-no claim. Reading case data, interpreting the dictionary and writing a faithful new file are separate capabilities. This reference describes the supported workflow and the checks that make limitations visible.

SAV and ZSAV reading

SAV Inspector reads SPSS system files and compressed ZSAV files into a shared Rust model used by both browser and server transports.

  • Numeric and string variables
  • Variable and value labels
  • Print/write formats and measurement levels
  • User-defined missing values
  • File label, notes, weight variable and multiple-response sets
  • Cases and supported compression variants

Writing and verification

The writer creates a new SAV or ZSAV rather than modifying the source bytes in place. The round-trip check immediately reads the result and compares supported dictionary properties and cases.

Proprietary extensions, extremely unusual records or metadata outside the supported model may not be preserved. Inspect the compatibility preview and retain the source whenever a third-party workflow depends on specialised SPSS behaviour.

CSV and XLSX imports

CSV and Excel tables contain cells, not an SPSS dictionary. The local import preview therefore asks for delimiters, encoding, decimal conventions, worksheets and inferred types. It does not invent value labels, missing definitions, weights or multiple-response sets that are absent from the source.

Practical workflow
  1. Open and inspect

    Confirm format, encoding, compression, rows, columns and dictionary properties.

  2. Review compatibility findings

    Pay attention to unsupported or ambiguous metadata before editing.

  3. Write a new copy

    Choose SAV or ZSAV and never discard the source during validation.

  4. Run the round-trip

    Compare the reopened result and test it in the downstream application when that workflow is critical.

FAQ

Frequently asked questions

Are SAV and ZSAV the same?

They represent SPSS system data, but ZSAV uses additional compression and requires newer SPSS versions. Conversion changes representation, not automatically the meaning.

Does XLSX preserve SPSS metadata?

No. A spreadsheet does not natively carry the full SPSS dictionary. Missing rules, value labels and response sets must be supplied or recreated deliberately.

Can every historical SAV file be guaranteed to open?

No parser can honestly guarantee every damaged, proprietary or unusual file. Safety limits and clear errors take precedence over attempting unbounded decoding.

How should an unsupported file be reported?

Keep the original, record the producing application/version and provide a non-sensitive reproduction if possible. Do not send confidential data through an ordinary support message.

SAV Workflow Check

Find out in 30 minutes whether SAV Inspector fits your workflow.

We take one concrete recurring SAV job, define the desired outcome and demonstrate the shortest Local or Teams path. No generic product presentation, no newsletter and no file upload by email.

  • one concrete workflow instead of a feature tour
  • no-upload Local demo or controlled Teams pilot
  • a shared success criterion
  • a clear recommendation — including when SAV Inspector is not a fit

Only used to reply personally to this request. No newsletter. No SAV file or file metadata is transferred through this form. Privacy Email us directly