What's Actually Inside a Sims 4 Furniture Package?
Download enough Sims 4 custom content and eventually you start wondering why a single .package file for one chair can be so much bigger, and so much more complicated, than "chair." It's not really a chair as far as the game is concerned — it's a bundle of things that have to agree with each other before that chair ever shows up in your catalog.
There's an object definition in there. A 3D model. Textures, materials, a few different levels of detail, information about how the object sits in space, even data about how it casts a shadow. Normally you never see any of this. You place a sofa, the game handles the rest, and you move on with your build.
A Build/Buy viewer is basically a way of pulling back that curtain. SimsModly's Online Studio Build/Buy Viewer lets you open a compatible object package right in your browser and poke around at its 3D structure — the materials, the textures, the LOD meshes, the footprint, all of it — without installing anything or opening the actual game.
So what counts as "Build/Buy" content, exactly?
Build/Buy is the part of the game where you construct and furnish your lots — EA describes it more or less as the mode for building and decorating homes and community spaces. People usually think of furniture first: sofas, tables, lamps, shelving. But it covers a lot more ground than that. Walls, floors, doors, windows, fences, staircases, decorative clutter — each of these has its own internal resources sitting behind it, and when you download custom content, it typically arrives as a .package file.
And that one file can hold a surprising amount.
A chair is never just its mesh
Look at a custom table in-game and what you're really looking at is several separate systems agreeing to work together. The game has to know what the object is, how it shows up in the catalog, which model to render, which textures and materials belong to it, how it should look up close versus from across the room, which geometry state applies, where its shadow falls, and how much physical space it eats up.
None of that information lives in one tidy place. It's spread across the package, stitched together through internal references. That's part of why opening one of these files in a low-level editor can look like chaos at first glance — you're not looking at "a chair file," you're looking at the individual pieces the game assembles into a chair.
The object definition (OBJD)
One of the core resources here is the Object Definition, usually just called OBJD. This is part of what tells the game an object exists and how it connects to everything else it needs — its model, its footprint, and so on.
There's a relationship worth knowing about between OBJD and another resource called COBJ. Community documentation on Sims 4 packages generally describes the two as linked by instance ID, with COBJ handling most of the catalog-facing side of things and OBJD tying the object to its underlying resources.
You never see any of this while decorating a house, obviously. You click, the game does the rest.
COBJ: the catalog half
COBJ, or Catalog Object, is closer to the part players actually interact with — it's what shows up in the Build/Buy catalog itself. It typically holds things like the localized name and description you see in the panel. The object that exists in the game world and the entry you click on to find it aren't necessarily the same resource; the game just makes the connection feel seamless.
And then, the actual model
Eventually the object has to look like something. That's where the geometry resources come in — MODL and MLOD, depending on what you're looking at.
This is where a viewer gets genuinely interesting, more so than just staring at a texture. A texture tells you what the surface looks like — wood grain, marble, brushed metal. The mesh is a different thing entirely: it's what the object actually is, geometrically. Swap the texture on a table and it can look totally different. Swap the mesh and you've changed its shape.
Why does one object need more than one model?
Because you're not always looking at it from the same distance. Stand right next to a piece of custom furniture and the game can afford to render it in full detail. Walk across the room, or the map, and rendering that same level of detail for every object in view would be wasteful. So the game falls back on LODs — Levels of Detail — swapping in simpler geometry the farther away you get. More detail when you're close enough to care, less when you're not. It's a pretty standard trick in 3D graphics generally, and Sims 4 objects lean on it too.
MLOD resources are tied to that lower-detail geometry specifically. The exact structure varies by object, but the takeaway is the same: the game isn't using one single mesh in every situation, and a fairly simple-looking piece of furniture can end up shipping with several model-related resources because of it.
Textures are only one layer of the picture
It's tempting to think of the whole thing as mesh + texture = object. That's not quite right, though. A texture tells the renderer what a surface looks like, but not how it should behave under lighting — that's the job of materials and shaders. A wooden table isn't just a mesh wrapped in a brown image; the material is what determines whether that surface reads as glossy, matte, or glass-like once light hits it. This is one of the reasons a package viewer tells you more than simply exporting the texture and opening it as a picture would.
Objects can have more than one geometry state
Some objects don't stay visually consistent — think of things that change appearance depending on what state they're in during gameplay. Rather than treating each version as a totally separate object, the package can just bundle the resources for all of its possible states together. Being able to see which geometry states a package supports is genuinely useful when you're trying to figure out why an object seems to contain several near-duplicate pieces of geometry.
Even shadows are part of the package
Something most players never think about: an object has to cast a believable shadow, and that doesn't happen for free. The package carries information specifically about how the object interacts with the game's lighting and shadow rendering — it's not just a solid mesh floating in space as far as the renderer is concerned.
Footprints — where the object actually lives, spatially
This might be the most practically useful detail for builders. The footprint is what determines the space the game treats as "occupied" by an object, and it isn't always the same as the shape you see. A decorative piece can visually spill over an area while its actual placement footprint is smaller (or shaped differently). That's the reason an object sometimes seems to leave more, or less, usable space around it than its silhouette suggests — Build Mode is reading the footprint, not the mesh.
Why bother inspecting any of this?
Honestly, for a lot of players it's just curiosity. For CC creators it's more practical — maybe you're reverse-engineering how an object was built, checking whether a package actually has multiple LODs, chasing down a texture bug, or trying to understand why a footprint isn't behaving the way you expected. And sometimes you're just staring at a .package file wondering what's actually in there. That's a fine reason on its own.
Sims 4 Studio already does this, so why use a browser tool?
Sims 4 Studio remains one of the go-to tools for working with Sims 4 CC, and its own documentation goes well beyond simple previews — it covers how object packages are put together, resource by resource, including where each one lives and how to edit it. If you're actively creating content, that full environment is hard to beat, and installing another viewer on top of it probably won't change much for you.
But there's a real difference between editing an object and inspecting one. If all you have is a single .package file and you want a quick look inside it, opening a browser tab is a lot less friction than firing up a full desktop application.
That's the gap SimsModly's viewer is aimed at. You give it a compatible object package, and it parses the supported resources right there in the browser — object definition data, catalog info, textures, MODL resources, LOD meshes, geometry states, material info, shadows, footprint data, and whatever other metadata the object carries. Instead of an opaque file, you get a 3D scene you can actually look around in.
Your file doesn't leave your computer
One reasonable worry with any browser-based 3D tool is where the file actually goes. With this one, the package is processed locally — the preview gets assembled in your browser rather than uploaded somewhere and rendered on a server. So it's your package, straight to your browser, straight to a preview — nothing routed through a remote pipeline in between. If you're working with something unreleased, or you just don't like the idea of your CC leaving your machine, that distinction actually matters.
Where a viewer like this earns its keep
A few situations where this kind of tool is genuinely handy:
Checking downloaded CC before it goes in your Mods folder — a quick look before you commit.
Learning how objects are built, if you're getting into creating CC yourself and want to see how the models, LODs, and materials fit together.
Troubleshooting — if an object looks off in-game, the problem is probably sitting somewhere in its geometry, texture, material, or LOD setup. Inspecting it won't hand you the answer outright, but it gives you a concrete place to start looking.
Comparing two similar-looking objects to see where they actually differ under the hood.
Cleaning out an overgrown Mods folder, where relying on filenames alone stops being reliable after a certain point.
What it's not trying to be
Worth saying plainly: this is a viewer, not an editor. It's built to let you inspect supported resources — it's not pretending to replace a proper CC creation suite. If you want to remodel a sofa, redo its UV map, paint new textures, and package it back up as something new, you still need a real editing workflow for that. The question this tool answers is much narrower: what's already in this package? Sometimes that's exactly the question you actually have.
Why a browser tool makes sense at all
Plenty of workflows genuinely need a full desktop application, and plenty don't. If you're creating CC seriously and every day, a proper modding setup belongs on your machine. But if you're a player who grabbed one object and wants a quick look, or a creator who just needs to check a package while working on a different computer, a browser tab beats setting up an entire local environment for a five-minute task. The point isn't that a browser makes 3D asset creation easy — it doesn't try to. It's that inspecting one object doesn't have to turn into a whole project.
What it still can't tell you
Even a good viewer has limits. It can show you the structure of a package, but it can't tell you how that object actually behaves once it's sitting in a real lot. Placement, routing, interactions, animations, object slots, clipping, how it looks under actual in-game lighting, how it behaves next to other objects — none of that shows up in a static preview. The viewer shows you the asset. The game shows you the asset in context. Those really are two different kinds of testing, and skipping the second one because the first one looked fine is how bugs slip through.
The bigger picture
Build/Buy feels effortless from the player's side — click a chair, place it, move on to the next corner of the room. Underneath that is a surprisingly involved stack of resources: catalog definitions, object definitions, meshes, textures, materials, geometry states, LODs, shadows, footprint data. You're not meant to think about any of it while you're playing.
But the moment you start creating CC, or troubleshooting it, or just getting curious about how the game actually works, that hidden structure stops being irrelevant and starts being the whole point. That's what a tool like this is for — not a replacement for a full desktop creation suite, just a way to open a compatible package, see the 3D asset, and look at what's actually holding it together, straight from your browser.
FAQ
What is a Sims 4 Build/Buy Viewer? A tool for inspecting and previewing compatible Build/Buy object packages from The Sims 4 — including their 3D geometry and the resources behind it.
What can a Build/Buy package actually contain? Depending on the object, catalog and object-definition resources, meshes, textures, materials, LODs, geometry states, and other supporting resources the game needs.
What's an OBJD? An Object Definition resource — part of what defines a Sims 4 object and links it to related resources like its model and footprint.
What's a COBJ? Catalog Object. It handles the catalog-facing side of an object, including things like its localized name and description.
What are LODs? Levels of Detail — different versions of an object's geometry used depending on how far away it's being viewed, to keep rendering efficient.
What's an MLOD? A resource tied to an object's lower-detail or alternate geometry.
What's an object's footprint? The space the game treats as occupied by an object — which determines how it interacts with placement and everything around it, and isn't always the same as its visible shape.
Do I need Sims 4 Studio to inspect CC? No — SimsModly's Online Studio Build Buy Viewer can inspect supported object packages directly in a modern browser.
Does it upload my file anywhere? No. Compatible packages are processed locally, and the preview is built in your browser.
Can it replace Sims 4 Studio? Not for actually creating or editing CC — Studio is a much broader environment. This tool is focused specifically on inspecting and previewing.
Can I use it to confirm an object works correctly in-game? It'll help you understand what's in the package, but you'll still need to test placement, routing, interactions, clipping, and general behavior in the actual game.