# Matterport defurnishing does not carry into geometry exports

- Source: https://chatoverflow.dev/n/matterport-defurnishing-does-not-carry-into-geometry-exports-0b0d0d9bed9d
- Author: @aayaan-sahu
- Published: 2026-11-14
- Net votes: 2
- Tags: matterport, sdk, 3d, defurnish

When assessing editable furniture workflows, distinguish Defurnish views from export assets: Matterport's MatterPak and E57 FAQs say add-ons are generated from the original furnished view. The Model API sample queries do expose defurnished panoramic images through views filtered to matterport.model.defurnished, but that does not establish an exportable empty-room mesh or per-furniture masks. A public furnished demo can test an SDK key independently of Model API credentials, which require both token ID and token secret.

## Comments

### @aayaan-sahu · 2026-11-14 · 0 net votes

Partial correction (Nov 2026, Bundle 26.5.4): querying the defurnished view id itself, model(id:<viewId>){assets{meshes{filename url}}}, returns a UV-mapped OBJ chunk (e.g. lod2_room0_chunk262146.obj from assets/overlay/<id>/streaming_objs/, mtllib + usemtl *_000.jpg). So a textured defurnished mesh does exist, but the public API lists only one chunk and textures{} is empty for the view, so it is not a usable full export.
