image-to-mesh-cli
Image → semantic segmentation → per-object Unity meshes.
Free, local pipeline: YOLO-seg cuts an image into object masks + transparent crops, then each crop becomes a Unity-importable mesh (textured-quad stub today, TripoSR backend optional).
Install
pip install image-to-mesh-cli
# or from source:
pip install -e .
Requires Python 3.10+.
Use
image-to-mesh segment test_images/bus.jpg --out output/bus
image-to-mesh mesh --manifest output/bus/manifest.json --out output/bus/meshes --backend stub
image-to-mesh pipeline test_images/bus.jpg --out output/bus --backend stub
Outputs per image: overlay.jpg, masks/, crops/ (RGBA, square-padded for
image-to-3D), manifest.json, meshes/ (.obj + .mtl + texture).
Drag meshes/*.obj into Unity — each imports with its crop as texture.
Backends
stub(default): textured quads, works everywhere, no GPU needed.triposr: real single-image-to-3D via TripoSR. Needs torch plus a checkout at./triposr_weights_src(cloned from VAST-AI-Research/TripoSR). Falls back tostubwhen unavailable.
1 maintainer
Metadata
1 maintainer
Release files for image-to-mesh-cli 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| image_to_mesh_cli-0.1.1.tar.gz | 9.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| image_to_mesh_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / image_to_mesh_cli-0.1.1.tar.gz
| Download URL | image_to_mesh_cli-0.1.1.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d12ceb90820db40838eb98e11f8455ab8133a69eb54d34e52c8d085758215828
|
|
BLAKE2b-256 checksum How to use checksums |
f374bb66a7788e341ba5f74cbbfbdf43e36d32315a7aa841591a5e9a5778fb29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / image_to_mesh_cli-0.1.1-py3-none-any.whl
| Download URL | image_to_mesh_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a68a19ca8b08e6f929837ee84b1d9e6c5b3fd233a7dff41687fddd14545c7af8
|
|
BLAKE2b-256 checksum How to use checksums |
1f36d38e202727bd29b32b8a5cb6fefdc22950f86e89842cbfd4b1157b38f55b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logSecurity for image-to-mesh-cli 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for image_to_mesh_cli-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
