XML to Python

Generate Python classes/structs automatically from an XML document.

100% Client-Side Local Execution

Upload Data

Class Name:

<user>
  <id>1</id>
  <name>Omni</name>
  <isActive>true</isActive>
</user>

<user>
  <id>1</id>
  <name>Omni</name>
  <isActive>true</isActive>
</user>

from dataclasses import dataclass
from typing import Any, List, Optional

@dataclass
class ResponseData:
  user: ResponseDataUser

@dataclass
class ResponseDataUser:
  id: int
  name: str
  isActive: bool

from dataclasses import dataclass
from typing import Any, List, Optional

@dataclass
class ResponseData:
  user: ResponseDataUser

@dataclass
class ResponseDataUser:
  id: int
  name: str
  isActive: bool

What is XML to Python?

This free online tool turns a sample XML document into a ready-to-use dataclass for Python, so you can use this xml to python class generator tool to go straight from raw XML to a typed dataclass (or Pydantic model) without writing the boilerplate yourself. It is built around Python's actual idiom — a dataclass — rather than a generic one-size-fits-all class, and pairs naturally with xmltodict or ElementTree for real-world (de)serialization. Use it for xml to python dataclass or any time you need xml to python dict class, whether you're scaffolding a new Python project or mapping an existing API response.

Technical Execution

Paste or upload a sample XML document and the tool walks its structure field by field, inferring a concrete Python type for each value — mapping basic XML types to `str`, `int`, `bool`, and `float` as appropriate. For nested data, it converts the XML tree into Python dataclasses the way `xmltodict` represents it: child elements become nested dataclass fields, repeated elements become `List[T]`, and attributes are pulled into their own typed fields. On the naming side, it keeps snake_case keys as-is since that already matches PEP 8 field naming, and only adds an alias (via `field(metadata=...)` or Pydantic's `Field(alias=...)`) when a key uses camelCase or contains characters that aren't valid Python identifiers. For optional data, fields seen as `null`, or absent in some sample objects, are typed as `Optional[str]` (or the inferred type) with a `None` default, matching how both dataclasses and Pydantic express optional fields.

Zero Data Storage Guarantee

Everything runs client-side in your browser: the sample XML you paste in — which may contain real field names, endpoint shapes, or structure from a private API or project — is parsed and converted entirely on your device and is never uploaded to any server. Nothing you enter is logged, stored, or transmitted anywhere, so you can safely paste a real payload from an internal or unreleased API to generate an accurate dataclass. Closing or refreshing the tab clears everything, since no copy of your data ever left your machine in the first place.

How to Use XML to Python (Step-by-Step Guide)

Copy a representative sample of your XML (the more fields and nested objects it includes, the more complete the generated dataclass (or Pydantic model) will be).
Paste it into the input panel of the XML to Python tool, or click "Upload" to load it from a xml file.
Review the auto-detected root name, and rename it if you want the generated dataclass to use a specific class or type name instead of the default.
Click "Generate" to produce the Python dataclass (or Pydantic model), which appears instantly in the output panel with syntax highlighting.
Click "Copy" to copy the generated code to your clipboard, or "Download" to save it as a `.py` file.
Paste the result into your Python project and adjust field names or types if your data has edge cases the sample didn't cover.

Frequently Asked Questions (FAQ)

Q: How does this tool handle nested objects and arrays when converting XML to Python?

A: The tool converts the XML tree into Python dataclasses the way `xmltodict` represents it: child elements become nested dataclass fields, repeated elements become `List[T]`, and attributes are pulled into their own typed fields That keeps the generated code organized the way a Python developer would structure it by hand, instead of flattening everything into one giant dataclass (or Pydantic model).

Q: What happens to fields that are nullable or missing from some records?

A: For optional data, fields seen as `null`, or absent in some sample objects, are typed as `Optional[str]` (or the inferred type) with a `None` default, matching how both dataclasses and Pydantic express optional fields. If your sample only has one example object, fields that could be null in other records might not be detected as optional — paste a few varied samples (or an array of objects) for the most accurate result.

Q: Is this better than writing the dataclass (or Pydantic model) by hand?

A: For anything beyond a trivial, flat payload, yes — hand-rolling a dataclass for a nested JSON payload means manually working out every field's type, remembering `Optional` for anything nullable, and keeping the whole tree in sync every time the API response shape changes. The generator produces the same result in seconds and gives you a correct starting point to refine, rather than a blank page.

Q: Is my XML data safe to paste into this tool, especially if it's from a private API?

A: Yes. Everything runs client-side in your browser: the sample XML you paste in — which may contain real field names, endpoint shapes, or structure from a private API or project — is parsed and converted entirely on your device and is never uploaded to any server. Nothing you enter is logged, stored, or transmitted anywhere, so you can safely paste a real payload from an internal or unreleased API to generate an accurate dataclass. Closing or refreshing the tab clears everything, since no copy of your data ever left your machine in the first place.

Q: Can I use this as a convert xml to python object?

A: Yes — the tool is commonly used as a convert xml to python object, and works the same way whether you're converting a one-off response for a prototype or generating model code for a production project.

Q: Does the tool rename fields to match Python naming conventions?

A: Yes. It keeps snake_case keys as-is since that already matches PEP 8 field naming, and only adds an alias (via `field(metadata=...)` or Pydantic's `Field(alias=...)`) when a key uses camelCase or contains characters that aren't valid Python identifiers, so the generated code reads naturally in Python while still deserializing the original XML correctly.

Q: What Python library does the generated code work with?

A: The output is written to pair cleanly with xmltodict or ElementTree, the most common choice for Python developers handling XML, so you can drop it into an existing project without changing your serialization setup.

Q: Does this tool work for deeply nested or large XML samples?

A: Yes. The tool recurses through every level of nesting it finds and generates a complete set of linked dataclass (or Pydantic model) definitions, not just the top level — though for very large samples, trimming it down to one representative record per array is usually enough to get an accurate result.

Report an issue with this tool