UML Class Diagram Maker

What to include in your description

List the classes or domain concepts, each class’s responsibility, important attributes, known operations and relationships. State whether a relationship is inheritance, composition or a simple association when you know.

A practical starting point

For a lending system, describe Book, Member and Loan with the actual attributes and operations your project contains. If no implementation exists, say that you want a conceptual domain model.

Make a diagram in four steps

1. Connect and validate your own Gemini API key.
2. Enter a project title and abstract, then optionally add a public GitHub repository.
3. Add relevant details, choose your diagram types and review the project.
4. Check the generated blueprint and assumptions, refine the diagram and download.

What to check before you export

• Use singular class names that match your implementation.
• Include only members relevant to the view.
• Distinguish inheritance from composition and association.
• Review multiplicity and any conceptual assumptions.

Choose the view that answers your question

A class diagram describes software or domain structure. A database schema describes physical tables, SQL types, keys and constraints. The two views can be related without being identical.

Diagrams use a monochrome palette by default. SVG stays vector; PNG exports at 1×, 2× or 3×. Use Download All for a ZIP containing your selected formats and project summary.

Common questions