XML to Ruby

Generate Ruby 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>

class ResponseData
  attr_accessor :user
end

class ResponseDataUser
  attr_accessor :id, :name, :is_active
end

class ResponseData
  attr_accessor :user
end

class ResponseDataUser
  attr_accessor :id, :name, :is_active
end

What is XML to Ruby?

This free online tool turns a sample XML document into a ready-to-use class (or Struct) with attr_accessor for Ruby, so you can use this xml to ruby class generator tool to go straight from raw XML to a typed class or Struct without writing the boilerplate yourself. It is built around Ruby's actual idiom — a Ruby class — rather than a generic one-size-fits-all class, and pairs naturally with Nokogiri for real-world (de)serialization. Use it for convert xml to ruby object or any time you need nokogiri xml to class, whether you're scaffolding a new Ruby 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 Ruby type for each value — mapping basic XML types to `String`, `Integer`/`Float`, and `true`/`false` as appropriate. For nested data, it maps nested XML elements to nested Ruby classes built with `attr_accessor`, representing repeated elements as arrays, in the same shape Nokogiri's DOM traversal would produce. On the naming side, it keeps snake_case keys as-is since that matches Ruby's idiomatic naming convention, and only renames a key when it isn't a valid Ruby identifier. For optional data, fields observed as `null`, or missing from some sample objects, are simply left unset (Ruby's dynamic typing means `nil` is always a valid value), and the generated initializer uses keyword arguments with `nil` defaults for them.

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 Ruby class. 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 Ruby (Step-by-Step Guide)

Copy a representative sample of your XML (the more fields and nested objects it includes, the more complete the generated class or Struct will be).
Paste it into the input panel of the XML to Ruby 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 Ruby class to use a specific class or type name instead of the default.
Click "Generate" to produce the Ruby class or Struct, 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 `.rb` file.
Paste the result into your Ruby 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 Ruby?

A: The tool maps nested XML elements to nested Ruby classes built with `attr_accessor`, representing repeated elements as arrays, in the same shape Nokogiri's DOM traversal would produce That keeps the generated code organized the way a Ruby developer would structure it by hand, instead of flattening everything into one giant class or Struct.

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

A: For optional data, fields observed as `null`, or missing from some sample objects, are simply left unset (Ruby's dynamic typing means `nil` is always a valid value), and the generated initializer uses keyword arguments with `nil` defaults for them. 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 class or Struct by hand?

A: For anything beyond a trivial, flat payload, yes — writing a Ruby class with `attr_accessor` for every field of a nested API response by hand is quick for small payloads but easy to get inconsistent across a larger, deeply nested one. 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 Ruby class. 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 xml to ruby hash class?

A: Yes — the tool is commonly used as a xml to ruby hash class, 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 Ruby naming conventions?

A: Yes. It keeps snake_case keys as-is since that matches Ruby's idiomatic naming convention, and only renames a key when it isn't a valid Ruby identifier, so the generated code reads naturally in Ruby while still deserializing the original XML correctly.

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

A: The output is written to pair cleanly with Nokogiri, the most common choice for Ruby 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 class or Struct 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