# About using Slicer with command line in windows

**URL:** https://discourse.slicer.org/t/about-using-slicer-with-command-line-in-windows/2851
**Category:** Support
**Tags:** registration
**Created:** [May 18, 2018, 5:41pm UTC](https://discourse.slicer.org/t/about-using-slicer-with-command-line-in-windows/2851 "2018-05-18T17:41:49Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [May 19, 2018, 2:23pm UTC](https://discourse.slicer.org/t/about-using-slicer-with-command-line-in-windows/2851/2 "2018-05-19T14:23:54Z")

</div>

If you don’t need to tune registration parameters case by case then it should be fairly easy to do. See this topic for some pointers: [can’t find batch processing](https://discourse.slicer.org/t/cant-find-batch-processing/2620/2?u=lassoan)

There is a lot of variability depending on how your input data is stored, what registration module you use, and what outputs to need to generate. If you have any specific questions then let us know.

---

_[View the full topic](https://discourse.slicer.org/t/about-using-slicer-with-command-line-in-windows/2851)._