# GUI
**URL:** https://forums.powershell.org/t/gui/3566
**Category:** PowerShell Help
**Created:** [December 26, 2014, 8:27am UTC](https://forums.powershell.org/t/gui/3566 "2014-12-26T08:27:41Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@hel-thapa](https://forums.powershell.org/u/hel-thapa)
#### Post date: [December 26, 2014, 8:27am UTC](https://forums.powershell.org/t/gui/3566/1 "2014-12-26T08:27:41Z")
Can we create a GUI interface in PowerShell tool? If, can, how is it?
---
### Author:  [@donj](https://forums.powershell.org/u/donj)
#### Post date: [December 26, 2014, 8:29am UTC](https://forums.powershell.org/t/gui/3566/2 "2014-12-26T08:29:13Z")
Yes. PowerShell Studio.
---
### Author:  [@matt-mcnabb](https://forums.powershell.org/u/matt-mcnabb)
#### Post date: [December 26, 2014, 12:06pm UTC](https://forums.powershell.org/t/gui/3566/3 "2014-12-26T12:06:34Z")
It’s very possible to create GUI tools with Powershell. As mentioned by Don, Powershell Studio allows the creation of GUIs using a graphical interface. It is very similar in feel to creating a WPF application in Visual Studio or a form in Microsoft Access. However, Powershell Studion is pretty pricey; If you use all the time it’s well worth it but not for a one-off or for experimentation.
You can do the same thing just by using Windows Presentation Foundation (WPF) which Powershell has full access to, but this requires a lot of extra code overhead. You can also use Windows Forms which is an older way of doing what WPF does, but is still valid for many uses.
For simple pop-ups and such, I have even used stuff like the Wscript.Shell object - think Yes/No/Cancel dialogs and such.
---
### Author:  [@will-anderson](https://forums.powershell.org/u/will-anderson)
#### Post date: [December 28, 2014, 11:57pm UTC](https://forums.powershell.org/t/gui/3566/4 "2014-12-28T23:57:03Z")
I got introduced to PowerShell Studio when I was at TechMentor earlier this year. I was able to build usable tools for my admins in less than an hour. Like Matt mentioned, it’s pretty pricey if it’s coming out of your own pocket. If the company is paying for it though, the cost isn’t bad at all.
---
### Author:  [@\_timpringle](https://forums.powershell.org/u/_timpringle)
#### Post date: [December 29, 2014, 10:47pm UTC](https://forums.powershell.org/t/gui/3566/5 "2014-12-29T22:47:36Z")
You can also download the 30 day trial if it’s something that you only need temporarily. From what I can recall it gives full functionality during that period.
If you export the build to clipboard, then you can paste the entire code into the PowerShell ISE and continue work from there.
---
### Author:  [@hel-thapa](https://forums.powershell.org/u/hel-thapa)
#### Post date: [December 30, 2014, 3:37am UTC](https://forums.powershell.org/t/gui/3566/6 "2014-12-30T03:37:06Z")
Thank you so much Don Jones sir, how can I get PowerShell Studio? I mean, can you send me any link to download PowerShell Studio?
Thank you once again
---
### Author:  [@william-murphy](https://forums.powershell.org/u/william-murphy)
#### Post date: [December 30, 2014, 4:05am UTC](https://forums.powershell.org/t/gui/3566/7 "2014-12-30T04:05:32Z")
Its made by Sapien. And its the only editor aside from the ISE/notepad that anyone on my team uses these days.
[url][SAPIEN Technologies, Inc. - Tools and Information for IT Professionals](http://www.sapien.com/software/powershell_studio%5B/url%5D)
---
### Author:  [@jack-neff](https://forums.powershell.org/u/jack-neff)
#### Post date: [December 31, 2014, 3:53am UTC](https://forums.powershell.org/t/gui/3566/8 "2014-12-31T03:53:02Z")
Agreed with Matt McNab. If you’re just creating simple GUI’s for your scripts you’re better off spending a little time learning WPF or (my favorite) XAML. Also do not overlook the extremely useful ‘Show-Command’ cmdlet! Many times I can get away with that alone!
There are free WPF and XAML editors out there but I’m not sure what I’m allowed to post here so just ask Google. But as Will said if work is flipping the bill than PS Studio is the way to go.
---
### Author:  [@dotnVo](https://forums.powershell.org/u/dotnVo)
#### Post date: [May 16, 2024, 8:46pm UTC](https://forums.powershell.org/t/gui/3566/9 "2024-05-16T20:46:34Z")