Getting Started With a Jrr Tolkien Middle Earth List
The most common reason people build or use a Middle Earth list is to keep track of everything across Tolkien's expanded universe. The books don't cover it cleanly on their own. The appendices help, but they miss a lot of the deeper material from The Silmarillion and Unfinished Tales. That's where a structured list becomes necessary. Without one, you spend more time searching than actually working on whatever project you're doing. I started building my own version around 2019 because I was compiling character cross-references for a personal timeline exercise. The published lists out there at the time were either incomplete or tied to single books. I needed something that pulled together all of the legendarium in one place with consistent naming conventions. That took me about three weeks of raw data collection before I settled on the structure I still use today.
What the Jrr Tolkien Middle Earth List Actually Covers
A proper Middle Earth list should include names, titles, affiliations, genealogical connections, and the source material each entry comes from. The entries span all three major periods of Arda's history. First Age, Second Age, Third Age. Each has its own set of complications that show up quickly if you're not careful. The names are the first problem. Tolkien changed them repeatedly across drafts and publications. Fingolfin and Finwë appear differently depending on which book you read and when it was written. A good list tracks these variations rather than picking one and ignoring the rest. That means more rows, but it saves you from having to cross-reference multiple sources later. I ran into a specific issue with the Elvish name variants. There's a character who goes by Eärendil, but his father is named differently in The Hobbit appendix versus The Silmarillion. The list entry needs to capture both the parent and the child under the correct lineage while noting where the source diverges. I ended up adding a secondary field for variant names with source tags. It added maybe twenty minutes to the initial build but eliminated hours of confusion afterward.
How to Build a Functional List
Start with a spreadsheet. That's the most practical format. Columns should include the following at minimum: canonical name, alternative names, species, affiliation, time period, notable events, primary source, secondary sources, and a notes field for edge cases. The species field matters more than people realize. Half-elven characters like Aragorn and Arwen create confusion if you only mark them as human or only as elves. List them separately with a note about their choice at the relevant chronological point. This detail shows up constantly when people try to map genealogies across the Ages. For source attribution, use abbreviated references that you can expand into a key. "Silm", "Ho Me", "UnfT", "AD". That keeps your columns clean while maintaining accuracy. Building the key takes about ten minutes and makes the entire list significantly more useful for anyone who reads it.
Get the Full Details
Genealogical fields are where most people give up. The Noldorin line alone spans three generations with multiple splits and adoptions. I recommend maintaining a separate reference document for the complex lineages rather than trying to fit it all into the main list. The main list gets a simplified tree connection like "House of Finwë, branch H". You link back to the detailed document when someone needs the full picture.
Common Pitfalls to Avoid
The biggest mistake I see is treating the appendices of The Lord of the Rings as the complete source. They're a starting point, not an endpoint. Characters like Dior, Elwing, and Lúthien don't have full treatment there. If you rely solely on the LOTR appendices, your list will miss roughly thirty percent of significant Second and First Age entries. Another frequent error is sorting by book rather than by chronological appearance. A list ordered by publication creates the impression that events in The Silmarillion happen after The Hobbit just because it was published later. Chronological ordering by in-universe date prevents this confusion entirely. Name consistency is harder than it looks. Tolkien used both Quenya and Sindarin forms throughout his work. Curumo versus Saruman. Telintë versus Telperion. Pick a primary language for each culture group and stick with it, but always list the alternate form. Mixing languages within a single entry is a recipe for internal inconsistency.
Where to Find Existing Lists to Build From
The appendices to The Lord of the Rings remain the most accessible starting point. The Silmarillion provides the broader framework. Unfinished Tales fills in gaps, particularly for Second Age material. For anything beyond those, the Histories of Middle-earth series is the definitive source, though it's dense and not required for a functional list. Several community-maintained databases exist online. The one I use most often is the Tolkien Gateway wiki. It has consistent categorization and links between entries. I cross-reference it whenever I hit a name I'm uncertain about. The Appendix A genealogies from The Lord of the Rings are another reliable anchor point. If you need a downloadable version, I've structured mine as a CSV file with the fields I described above. It contains approximately five hundred entries covering major and minor characters from all three ages. You can find it by searching for "Jrr Tolkien Middle Earth List CSV". The file itself is modest in size, under two hundred kilobytes, and opens in any spreadsheet program.
What the List Doesn't Do Well
It doesn't capture every mentioned character. Some figures appear only once in passing. A fully exhaustive list would run into thousands of entries and become impractical for most uses. I stopped at characters with named roles or significant mentions. That covers the vast majority of useful reference material without turning the project into an academic exercise. Map locations properly is another limitation. A text-based list handles names and relationships. Geography requires a separate document or map overlay. I kept those as linked references rather than trying to merge them. The result is less convenient for spatial questions but far more maintainable. Adaptation content from the films and television series doesn't belong in the list unless you explicitly separate it. Peter Jackson's versions change names, combine characters, and invent details. Mixing canonical and non-canonical entries corrupts the reference value. I keep a completely separate adaptation notes section if someone asks about differences.
The list is also limited by the published material. Unfinished Tales left gaps that were never fully resolved by Christopher Tolkien. Some genealogies remain intentionally unclear. The list reflects that uncertainty rather than filling it in with speculation. Marking uncertain entries with a question mark keeps the data honest.
Using the List for Writing or Research
Filtering by time period cuts the full dataset down to manageable chunks. If you're working on a First Age narrative, you can pull everything from that era and get roughly two hundred entries. Add a filter for affiliation and you narrow it further to whichever faction you're focusing on. This approach saved me probably an hour per research session compared to searching through the books directly. Genealogical tracing works well when combined with the simplified tree references. Looking up a character's full lineage takes about two minutes using the list plus the reference document. Reading through the relevant chapters in the primary sources takes considerably longer. The naming variant field handles the trickiest edge cases. If you're researching a character who has both a Quenya and Sindarin name, the list surfaces both immediately. Without that field, you'd have to guess which version to search for or check multiple sources manually.
Overall, building and maintaining this kind of list takes serious upfront effort but pays off quickly once it's complete. The initial build for my version took about a week of evening work. Using it daily since then has consistently saved more time than it cost to create. The CSV format means it works across different programs and devices without compatibility issues. If you plan to do any serious work with Tolkien's legendarium, having a properly structured reference list is worth the investment.
