> For the complete documentation index, see [llms.txt](https://docs.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaedim3d.com/creating-assets/input-guidelines/input-image-examples/furniture.md).
# Furniture
For generating furniture we suggest:
* [Game-ready](/creating-assets/game-ready-assets.md), for realistic textures and higher accuracy in geometry for soft materials
* Depending on complexity, "Standard" or "High" [generation quality](/creating-assets/prototype-assets.md#levels-of-quality) (if using [Prototype](/creating-assets/prototype-assets.md))
* Uploading images with additional views/angles of the furniture if available
## Suggested Inputs
### Multiple Views
It is always recommended to upload multiple views as separate images. The more angles, the better.
|  |  |  |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
### Single View
If uploading a single image, make sure it shows most of the furniture like the examples below ⬇️
* Clear view of object (no hidden parts)
* Clear image
* Minimal background
### ❌ Inputs to avoid
Avoid input images that have multiple objects. These generations will not be processed.
### Output Examples
Input image
47,812 tris / High quality
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kaedim3d.com/creating-assets/input-guidelines/input-image-examples/furniture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
