Storyline XLF import error

Storyline XLIFF import error after CAT-tool editing

If Storyline rejects a translated XLF/XLIFF file, compare the original export and the returned file first. The import doctor checks the common structure blockers locally.

Diagnose original + translated XLF What to check first

Import blocker

Storyline import usually breaks after structure drift in the translated file.

CAT tools and AI edits can preserve visible text while changing IDs, targets, protected inline tags, encoding declarations, or XLIFF version details. The checker flags these import blockers and avoids repair claims for unsupported cases.

Fast checklist

Start with the original Storyline translation export and the returned translated file.
Look for missing targets, protected tag drift, changed trans-unit IDs, malformed XML, and unsupported XLIFF versions.
Treat XLIFF 2.0 support as diagnostic-only until a safe repair path is proven.
Use the repair download only when the preview reports a safe fix.

What the import doctor can do

Diagnose structure drift

Find changed IDs, missing targets, protected tag drift, malformed XML, unsupported versions, and encoding issues.

Repair only safe classes

Paid repair appears only for safe fixes that do not rewrite translated course text.

Keep files local

The preview runs in the browser. Your XLF text is not uploaded to KikuAI for this checker.