Venn Set Diagram Builder

How to use Venn Set Diagram Builder

See where your lists overlap without hiding the membership evidence. Every universe element belongs to one mutually exclusive region; the diagram shows its count, while the report and printable table retain the exact members in source order.

1. Provide an explicit universe of at most 200 unique nonblank strings and two or three named member lists. Every set member must appear in the universe.
2. Use exact strings consistently. Choose SVG for the count diagram, printable HTML for the full region roster, or JSON for the source lists and checked partition.
3. Inspect every region, including none, and compare the inclusion-exclusion union witness. Circle sizes stay fixed even when sets are empty, identical or nested.

Good to know

• Two or three sets share one workflow, producing four or eight regions. Universe and each list hold 0–200 unique strings; names have at most 24 UTF-16 code units and member strings at most 80. Blank strings, controls, invalid Unicode scalar text, duplicate members, duplicate set names and members outside the explicit universe are refused. No implicit universe is inferred.
• Strings use literal equality. Case, leading/trailing spaces and composed/decomposed Unicode representations remain distinct; no spelling correction, canonicalization, fuzzy match or multiset duplicate count is applied. Region members retain universe order rather than being locale-sorted.
• This is a fixed non-proportional Venn diagram, not an area-proportional Euler layout. All possible regions stay visible, with explicit zero counts; an empty or contained set does not change the circle arrangement. Generated counts never claim probabilistic independence or statistical inference.
• The standalone SVG shows set names and region counts; the full member roster is in the HTML and JSON report. Diagram viewport is 600 by 500 SVG units, with ordinary unscaled font sizes. Long member strings wrap in the printable table; actual font support, page breaks, diagram rendering and physical print layout require inspection.
• Browser-local processing, with no upload, persistence, external resources or code execution. Model JSON is limited to 30,000 characters, 10,000 values and 18 levels. Generated HTML is capped at 750,000 characters, standalone SVG at 50,000 and the complete report at 1,000,000. The downloaded artifact must be inspected in the target browser and print setup.