Online XML to vCard Converter
Convert XML contact data to vCard files in your browser. Map names, phones, and emails, then download a VCF file.
The conversion workspace is built for private XML handling, with processing completed in your browser.
Conversion focus
Schema-aware handling helps keep columns and nested fields understandable.
Map each VCF field to a normalized table column. Use Include to choose output lines; Check all / Uncheck all sit under the mapping table. You can duplicate TEL / EMAIL / ADR to output multiple entries.
| # | VCF Field | Mapping | Include | Others |
|---|---|---|---|---|
| Provide input above to load mapping options. | ||||
What this conversion is for
Flatten XML into columns, map headers to vCard fields using the on-page mapping table, then export .vcf for contacts apps.
- Conversion options for XML include Flatten nested structures, flatten type, and (when flattening is off) Select table—same behavior as JSON tabular exports.
- First extracted row as header, Limit # of rows, and Skip # of rows shape the intermediate grid feeding vCard.
- Use Format after edits to ensure the parser still accepts your file before a long export.
Understanding your XML structure
- The tool parses your file into an element tree; deep nesting stays nested until you enable Flatten nested structures with Type 1 / 2 / 3.
- With flattening off, repeated sibling elements can surface as separate “tables” in Select table—choose the one that matches the rows you need.
- Malformed XML (unclosed tags, bad entities) fails fast in the browser parser—fix the source, then use Format or Convert again.
- For targets that build a table first, Limit # of rows and Skip # of rows under Conversion options help you rehearse on a subset.
vCard export from XML-derived columns
- XML is parsed to rows first; each row can become one vCard after you map headers to properties.
- Use the mapping accordion to align columns with FN, TEL, EMAIL, ADR, and related fields—controls match the live ConversionTab mapping UI.
- Include toggles and duplicate-line actions follow the same rules as other tabular → VCF paths.
- Invalid or empty required mappings surface as export issues—fix the grid before retrying.
Use this output next
Spreadsheet review of contacts.
Dedupe and CRM cleanup in a grid.
Apps and directory sync.
Stage contacts for import.
Suggested workflow
Paste XML in the Text tab or upload a file; use Format when it helps.
Check root element, namespaces, and that entities are well-formed before mapping.
Map columns to FN/TEL/EMAIL (and optional N/ADR). Use + on TEL/EMAIL/ADR to add more fields on the same contact—not extra people. A blank name still exports as “Contact.”
Bundle .vcf for Google Contacts, Outlook, or handset import.
Before you convert
- Large XML can be memory-heavy—start with a slice if the file is huge.
- Phone numbers without country codes often import weakly on mobile.
- Keep a copy of the original XML as the audit trail after you ship vCard.
Choose the right output
When XML to vCard is useful
- Contacts apps require vCard text, not arbitrary XML.
- You can map extracted column headers to vCard properties in the mapping accordion.
- You need FN/TEL/EMAIL-style bundles Google or Outlook can import.
- Each logical row becomes one card after mapping.
When another format is better
- Bulk events belong in ICS, not contact cards.
- Data science paths want CSV/JSON, not vCard folding rules.
- When you only need printable directories, PDF may beat vCard bundles.
- Directory sync (LDAP/SCIM) beats manual vCard drops at enterprise scale.
Why use ConversionTab?
- Runs in your browser — XML you paste or load stays on your device while you Format or Convert.
- No mandatory upload — the transform runs client-side; you copy or download results from your own session.
- Fast iteration — quick feedback when markup or options change.
- Structured handoffs — suited to engineers and reviewers moving data between systems without extra glue services.
Continue with other formats
Flat pipelines and spreadsheet handoffs instead of VCF.
Print-ready snapshots instead of VCF.
Typed spreadsheet review instead of VCF.
APIs, fixtures, and browser-native trees instead of VCF.
Executable load scripts instead of VCF.
Reviewed XML → vCard notes
FAQ accordions below complement this page—open a section when you need edge cases or field rules.
Turn XML contact data into a downloadable .vcf file for address books.
Paste or upload XML, pick the repeating contact table if needed, map columns to FN/TEL/EMAIL, then convert. Duplicate TEL/EMAIL mapping rows add fields on the same card—not extra people.
- Paste XML or upload a file. Flatten or pick the repeating contact table if the document nests people under a parent node.
- Map columns to FN, TEL, EMAIL, and optional fields under vCard mapping options.
- + on TEL/EMAIL/ADR adds fields on the same contact—not extra people. Structured N keeps
;separators; blank names become Contact. - Select Convert, review the output, then copy or download the
.vcf. Use Load Sample and Clear as needed.
XML is parsed as structured input for this page. Use complete rows, valid syntax, and consistent field names so the converter can preserve the important data when creating vCard.
vCard is generated from the parsed XML data. Review the output before importing it into another system, especially when the destination expects strict columns, dates, or contact fields.
Help
Questions before converting
One question per row — expand only what you need.
Paste XML or upload a file, flatten or pick the repeating contact table if needed, map columns to FN/TEL/EMAIL, select Convert, then copy or download the .vcf.
+ on TEL, EMAIL, or ADR adds another field on the same contact—not another person. − removes a duplicated mapping row.
Use Family;Given;;;. Semicolons stay structural so address books can split first and last names.
The card still exports with the placeholder name Contact when no usable name is mapped.
Use Load Sample and Clear. Format helps check well-formed XML before you convert.
No. Conversion runs in your browser on this page.
Explore more conversions
Same goal, other inputs
JSON people data compiled into VCF for handset import.
SQL people data compiled into VCF for handset import.
XLSX people data compiled into VCF for handset import.
CSV & workbook bridges
Workbook to pipeline text.
Common API-to-sheet path.
Spreadsheet-first path to the same shape.
Exports & delivery
Web table fragment.