Stable Point Aware 3D (SPAR3D) is a large reconstruction model based on
SF3D, that introduces the ability to make real-time edits and generate a textured UV-unwrapped 3D mesh asset from a single image in less than a second. By introducing a first-of-its-kind two-stage architecture, SPAR3D combines the benefits of a fast point cloud diffusion model with regressive mesh predictions to enable unparalleled control over 3D object generation.
Please note: For individuals or organizations generating annual revenue of US $1,000,000 (or local currency equivalent) or more, regardless of the source of that revenue, you must obtain an enterprise commercial license directly from Stability AI before commercially using SPAR3D, any derivative work of SPAR3D (such as a “fine tune” model), or their outputs. You may submit a request for an Enterprise License at
https://stability.ai/enterprise. Please refer to Stability AI's Community License, available at
https://stability.ai/license, for more information.
We use renders from the
Objaverse dataset, available under the Open Data Commons Attribution License. We utilize our enhanced rendering method, which more closely replicates the distribution of images found in the real world, significantly improving our model's ability to generalize. We filter objects based on the review of licenses and curate a subset suitable for our training needs.
For usage instructions, please refer to our
GitHub repositoryAll uses of the model should be in accordance with our
Acceptable Use Policy.
The model was not trained to be factual or true representations of people or events. As such, using the model to generate such content is out-of-scope of the abilities of this model.
As part of our safety-by-design and responsible AI deployment approach, we implement safety measures throughout the development of our models, from the time we begin pre-training a model to the ongoing development, fine-tuning, and deployment of each model. We have implemented a number of safety mitigations that are intended to reduce the risk of severe harms. However, it is the responsibility of developers to conduct their own testing and apply additional mitigations based on their specific use cases.
For more about our approach to Safety, please visit our
Safety page.
