VCF TRIAGE · PRACTICAL GUIDE
iCloud vCard Size Limits: Check the Card, Not Just the File
By BestTools ·
A combined VCF’s total size and an individual contact card’s size are different checks. Splitting a file into smaller groups does not reduce the size of one oversized card.
Read the platform limit in its own scope
Apple’s current iCloud limits page lists a 256 KB maximum for a vCard, including photo and text. Verify the official page when you act because platform requirements can change. This is not a statement that every VCF file must total 256 KB or less.
VCF Triage uses a conservative 256,000-byte advisory threshold per card. It is a local warning, not an Apple-server response or a compatibility guarantee. The workbench’s separate total input limit is 5,000,000 bytes.
Use a simple two-card counterexample
Imagine two complete cards, each about 150,000 bytes. Together they exceed 256,000 bytes, but neither crosses the local per-card advisory. Now imagine one 300,000-byte card: placing it alone in a new file does not make that card smaller.
These sizes are arithmetic illustrations. The workbench can report actual block sizes in an inspected copy, but it does not shrink photos, remove notes or rewrite contact fields.
| Illustrative selection | Total | Per-card question |
|---|---|---|
| Two 150,000-byte cards | 300,000 bytes | Each card is below the advisory |
| One 300,000-byte card | 300,000 bytes | That card crosses the advisory |
| Split the oversized card into its own file | Still 300,000 bytes | The individual card has not changed |
Respond without damaging the original
- Keep a backup of the source VCF and destination contacts.
- Inspect the copied file and identify the specific flagged block.
- Use the source contacts application to create a separate supported version if a field or photo needs adjustment.
- Export a small deliberate selection and test it with the destination’s current workflow.
- Compare the imported contact details rather than treating the absence of a local warning as acceptance proof.
Keep advisories separate from diagnosis
A large card may contain a photo or other data, but the inspector does not decode or validate that media. Size alone does not identify which field must change, and the workbench does not automatically strip data.
If a destination rejects a below-threshold card, investigate its structure, encoding, fields and the actual import error. Do not keep splitting the same complete card into fragments. VCF Triage helps you select and inspect originals; the destination decides whether an import succeeds.
Sources and further reading
Sources checked on 2026-10-26. Platform menus and supported formats can change.