# How to save volume property JSON as a preset

**URL:** <https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139>\
**Category:** Support\
**Created:** [September 12, 2026, 2:55pm UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139 "2026-09-12T14:55:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![derradji](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/derradji/32/79013_2.png) [@derradji](https://discourse.slicer.org/u/derradji)\
**Post date:** [September 12, 2026, 2:55pm UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139/1 "2026-09-12T14:55:04Z")

</div>

hi  
i have **volume property saved vp.JSON , and i want to set it as a preset and select it for every volume a want to render .  
is there a feature that can add or save any modified preset as a new one**

---

<div class="post-metadata">

**Author:** ![Esteban\_Barreiro](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/esteban_barreiro/32/5430_2.png) [@Esteban\_Barreiro](https://discourse.slicer.org/u/Esteban_Barreiro)\
**Post date:** [September 14, 2026, 12:55pm UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139/2 "2026-09-14T12:55:07Z")

</div>

Hi!

You can drag and drop your vp.jason to Slicer and select it as volume property in the Input panel on Volume Rendering module.

 ![vp](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/7/5/75d5979d543024951672e99e6625d1b450dc1a6e.png)

---

<div class="post-metadata">

**Author:** ![derradji](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/derradji/32/79013_2.png) [@derradji](https://discourse.slicer.org/u/derradji)\
**Post date:** [September 25, 2026, 8:32pm UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139/3 "2026-09-25T20:32:53Z")

</div>

hi  
yes that’s a repetitive solution but i wish to add it as a preset

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [September 25, 2026, 10:19pm UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139/4 "2026-09-25T22:19:27Z")

</div>

Rest assured, you’re not the only one asking for this functionality. The ability to save and add custom volume rendering presets is the number 1 liked feature request on the Slicer issue tracker. See below:

> <https://github.com/Slicer/Slicer/issues/5505>
>
> \## Is your feature request related to a problem? Please describe.
> 
> I always st…art creating my volume rendering from scratch, however, that takes a long time and a lot of time and guessing 
> 
> \## Describe the solution you'd like
> 
> creat a simple " create a custom preset " in the volume rendering module

---

<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:** [September 25, 2026, 10:21pm UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139/5 "2026-09-25T22:21:40Z")

</div>

Yes, somehow never gets implement. The isssue is 5+ years old (and even older than that if you look at the forum).

---

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [September 30, 2026, 10:09am UTC](https://discourse.slicer.org/t/how-to-save-volume-property-json-as-a-preset/48139/6 "2026-09-30T10:09:49Z")

</div>

> [@derradji](#):
>
> yes that’s a repetitive solution but i wish to add it as a preset

You may try this [addon](https://gitlab.com/chir-set/Tools7/-/tree/master/ManyThingsToolBar#10-custom-volume-rendering-presets) that I just added in the parent extension project.