What v1 checks
VCARD boundaries, VERSION 3.0/4.0, required FN, expected N, duplicate UID, obvious property structure, long physical lines, limited REV and BDAY risks, and payload presence.
Step 1
Choose one local input
UTF-8 · up to 20 MB · up to 5,000 VCARD starts
The browser reads the selected file locally only after you choose Analyze.
Ready. Choose a file or paste text; nothing has been read.
Step 2
Value-free findings
Card indexes and physical source lines are 1-based.
0Cards
0Errors
0Warnings
0Info
No issues were reported by this limited checker. This does not guarantee importer compatibility.
| Severity | Card | Line | Property | Description |
|---|
Deliberate limits
This is not a complete RFC 6350/2426 validator. It does not fully validate quoted-printable, base64 PHOTO, parameter grammar, or every date-time variant. It never repairs or exports contacts.
Privacy boundary
Names, phones, emails, addresses, original values, and PHOTO/KEY/SOUND payloads are not shown in findings or copied into report.json. Clear removes this page’s in-memory result references.
Bounded manual service · USD 15
Need a reviewed correction?
One vCard file, up to 1,000 contacts: import-diagnostic summary, one corrected file, and one revision.
Discuss scope safely
Do not attach the contact file or any personal data to the first email. Agree on scope and a safe transfer method first.