VCF TRIAGE · PRACTICAL GUIDE
VCF Encoding Problems: UTF-8, UTF-16 and Folded Lines
By BestTools ·
An encoding error and a vCard structure warning are different problems. Preserve the original bytes, then obtain a supported UTF-8 export rather than simply renaming or rewriting the file.
Check decoding before contact structure
VCF Triage accepts valid UTF-8 and explicitly rejects a UTF-16 byte-order marker. It also rejects invalid UTF-8 instead of silently converting it. An unsupported file is not automatically a corrupt file.
If you have access to the source contacts application, export a separate supported copy. Keep the original while you compare names, punctuation and non-Latin characters. Do not replace unexpected characters by guessing what a person’s details should be.
Separate a folded line from a new property
A continuation line can belong to a preceding property. The workbench unfolds lines for its limited analysis while retaining original record text for selected-original extraction. This is one reason not to split or reformat a file by arbitrary visible line counts.
Legacy encodings, quoted-printable and older vCard forms receive limited handling or warnings. A version label alone does not describe every encoding and property rule present in a real export.
| Observation | Interpretation |
|---|---|
| UTF-16 marker | Unsupported encoding in this tool |
| Invalid UTF-8 bytes | Decoding failed; no conversion attempted |
| Complete block with warnings | Review that record and the destination requirements |
| Continuation line | Inspect it with its preceding property |
Use a reversible conversion workflow
- Preserve the original file, including its extension and source context.
- Obtain a new UTF-8 copy through the source application or a trusted encoding workflow.
- Inspect the new copy locally and compare representative non-Latin names and notes.
- Export a small deliberate set of complete records.
- Check the resulting contact fields in the destination before importing a larger set.
Do not mistake a browser preview for complete validation
A readable name in the local preview is useful evidence, but it does not test every parameter, photo encoding or destination-specific import rule. The tool does not decode photographs or validate email and telephone identity.
If file bytes need investigation, keep a record of the exact decoding failure. A structural report and an original-record export serve different purposes. Avoid sharing real contact fields when a synthetic reproducer or value-free diagnostic can describe the problem.
Sources and further reading
Sources checked on 2026-10-26. Platform menus and supported formats can change.