# Why should I use GeneratOrd? The alternative to GeneratOrd is to inscribe each item in your collection as a separate image. Because images are quite large compared to HTML files, it is much more expensive. Because of the initial cost of inscribing the traits, the larger the collection, the larger the potential savings you will get from using GeneratOrd. Let's use the Fomojis 2.0 collection as an example to see the power of recursion. #### Without GeneratOrd Fomojis 2.0 has 2009 images, and each is roughly 46KB. This results in a total size of the whole collection of 92.4MB. At a fee rate of 10 sats/vB, the total cost of inscribing all 2009 images would be around **2.31BTC**! For most collections, this would be prohibitively expensive. #### With GeneratOrd Fomojis 2.0 had 170 different traits, each one being roughly 19KB. Thus, the total size of the traits was 3.23MB. The HTML files are 117 bytes each, and there are 2009 of them, resulting in an extra 235KB to inscribe. Finally, the metadata was 26KB, resulting in the total size of the collection being 3.5MB. At a fee rate of 10sats/vB, this would only cost **0.09BTC!** **That is a saving of over 96%** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.generatord.io/readme/why-should-i-use-generatord.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.