# USD support in Slicer

**URL:** <https://discourse.slicer.org/t/usd-support-in-slicer/40115>\
**Category:** Support\
**Created:** [November 11, 2024, 4:57am UTC](https://discourse.slicer.org/t/usd-support-in-slicer/40115 "2024-11-11T04:57:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [November 11, 2024, 4:57am UTC](https://discourse.slicer.org/t/usd-support-in-slicer/40115/1 "2024-11-11T04:57:05Z")

</div>

There was some talk about USD format support in Slicer (e.g., [Open source Human Anatomy Atlas - #7 by pieper](https://discourse.slicer.org/t/open-source-human-anatomy-atlas/17734/7))

Was there any movement towards it?

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [November 11, 2024, 2:36pm UTC](https://discourse.slicer.org/t/usd-support-in-slicer/40115/2 "2024-11-11T14:36:45Z")

</div>

I haven’t seen a lot of interest in it, but there is a set of vtk C++ code for exporting to it if we wanted to. Do you have a particular use case in mind?

> **[GitHub - NVIDIA-Omniverse/ParaViewConnector: Plugin for Kitware ParaView adding Omniverse and...](https://github.com/NVIDIA-Omniverse/ParaViewConnector)**
>
> Plugin for Kitware ParaView adding Omniverse and USD support

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [November 11, 2024, 4:56pm UTC](https://discourse.slicer.org/t/usd-support-in-slicer/40115/3 "2024-11-11T16:56:02Z")

</div>

Nothing in particular at the moment, but given it is popularity we might eventually need it as an export format in Slicer. Particularly if it can support (not sure if it does) more object types than glTF.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [November 11, 2024, 5:13pm UTC](https://discourse.slicer.org/t/usd-support-in-slicer/40115/4 "2024-11-11T17:13:18Z")

</div>

USD was designed for a very different use case so probably could export many things (rendering related and maybe transforms and such) and also define extensions for slicer-specific data concepts. I just haven’t seen a lot of demand for it yet but maybe Blender i/o will be a driver. Since Omniverse is a paid service it’s hard for me to see it gaining much traction for our community but we’ll see how things evolve.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [November 11, 2024, 5:18pm UTC](https://discourse.slicer.org/t/usd-support-in-slicer/40115/5 "2024-11-11T17:18:22Z")

</div>

The following discussion is likely relevant:

> **[OpenUSD Support](https://discourse.vtk.org/t/openusd-support/12198)**
>
> I would like to understand the VTK community’s perspective on potential support for the OpenUSD standard. This thread was prompted by discussion at today’s VTK.js developers meeting. Overview Universal Scene Description is an open source project...