The booth at Nova Southeastern went quiet on a Tuesday night. I brought it back from my office in Davie over a remote session, using a keyboard shortcut I had remapped in AutoHotKey. The real one needed a key combination that will not travel down a remote connection. The fix worked. Above all, though, it told me something about the software underneath it.
The photo booth software for Windows we started on is capable stuff. It runs Canon bodies and webcams, it talks to Nayax card readers and MDB hardware, it prints, and it locks down for unattended use. We used it to put a machine in a university lobby that took more than 300 sessions in its first month. The problem was never what it could do. Instead, the problem was how long it took to find where to do it.
So we built VertexBooth. Same job, laid out so an operator can see all of it at once, and built first for the machine we run ourselves. We are giving beta testers two months free, and the form for a key is at the bottom of this post.
What the established tools get right
Start with the fair version, because operators who have run these tools for years are not wrong about them. A few hundred dollars buys a feature list we cannot match today. MDB and card payments, pay per print, pay per session, pay per share, multiple printer support, video capture with overlays, user surveys, lockdown mode, a password protected exit.
It is also stable in the way that matters commercially. In fact, our own crash rate at NSU turned out to be a configuration problem rather than a defect. A status update interval set to one second was hammering the machine, and moving it to sixty seconds settled it down. Their support team found it, and they were right.
None of that is the complaint. After all, a booth that earns money is a booth that runs, and these tools run.
Where the setup time actually goes
Here is the part nobody puts in a feature list. It took me weeks to find that one second setting, and the reason was not that it is hidden maliciously. Rather, the software has hundreds of settings spread across tabbed dialogs and profile files. They are arranged by the order they were built, not the order you need them.
Ask around the operator groups and the same three complaints come back. Scattered settings, a steep learning curve, and minimal visual guidance for whoever has to run the machine. In particular, that matches my experience exactly. Meanwhile, the screens a guest sees are configured in one place, the actions they trigger in another, the print layout in a third. Building one coherent flow therefore means holding all of it in your head.
Certainly, for a mobile operator this is an annoyance you absorb once. An unattended machine is different. Every setting you cannot find is a setting you cannot fix at eleven at night from a phone. In other words, the interface stops being a convenience question and becomes an uptime question.
That is the counterintuitive part. More features made our booth harder to keep running, not easier, because the surface area grew faster than the map did.
What we built instead
VertexBooth is photo booth software for Windows with two halves. Studio is where you build the booth. Kiosk is what the guest touches. Everything below is the current beta, running the machine we operate.
Every screen a guest sees, in one grid

To begin with, eight cards. Each carries a thumbnail of the real design, its internal name, what sits on it, and two buttons. You can see the whole guest journey without opening anything. As a result, handing a booth to a second person stopped being a training exercise.
Move a button by moving it

Similarly, drag across empty space and you have drawn a tappable area. Drag the box and it moves. Grab the corner and it resizes. Down the right side, in plain sentences, is what the screen does when it opens and what happens after a payment. For example, the idle screen begins a payment session for an amount you type into a box, and that is the entire configuration.
A strip builder that shows you the cut

Admittedly this one is small, and yet it saved us the most paper. Firstly choose the layout, then drag the photo slots. The preview draws the dotted line where a DNP RX1HS actually cuts the sheet. By contrast, the way we used to check that was to load paper and print a test.
Payment and hardware in the words you would use

In addition, every settings page opens with a sentence explaining what it is for. Payment says which hardware talks to the card reader. Mock mode walks a full session on a laptop with no reader attached. That is how we test changes before they touch a live machine.
Side by side, on the jobs you actually do
Feature checklists flatter whoever has been shipping longest. So this table compares the two on tasks instead, using the wording each product puts in front of you.
| The task | Established Windows booth software | VertexBooth (beta) |
|---|---|---|
| See every guest screen at once | Screens live across dialogs and profile files | One grid, one card per screen |
| Move or add a button | Edit the configuration, relaunch, look | Drag it on the design |
| Set what a screen does | Configuration entries and key mappings | Pick the action from a list on that screen |
| Check where the 2×6 cut lands | Print a test sheet | Preview the sheet with the cut drawn |
| Turn on card payment | MDB and Nayax VPOS, configured in settings | Nayax from a dropdown, amount in a box |
| Test without hardware | Needs the reader attached | Mock provider, no hardware |
| Run a second booth differently | Profiles | Profiles, switched from the launcher |
| Cameras | Canon DSLR and mirrorless, webcams | Canon, webcams |
| Price | Typically a few hundred dollars per licence, or a monthly subscription | Free for two months, then $250 once |

What VertexBooth does not do yet
Naturally, I would rather you find this out here than three days into a trial.
- No video capture. Stills, GIFs and boomerangs all work.
- Canon over USB, plus Sony and Nikon over USB in beta. Anything else through a capture card.
- More than one printer per machine, routed by print design or by button.
- No cloud microsite or gallery site of our own yet.
- Nayax and mock. MDB is on the list, not in the build.
- Windows only, and it will stay that way.
If your business depends on any of those, the software you already run is still the better tool and I will say so on a call. Still, if you want a booth you can reconfigure in ten minutes without opening a manual, that is the thing we built.
Two months free, and what we want back
To be clear, the beta is open and the trial runs two months with no card. We are not pretending this is generosity. We need operators running builds on hardware we do not own, in rooms we have never stood in, telling us what broke. That is worth more to us right now than licence revenue, so the trade is honest in both directions.
What you get: the full Studio and kiosk build, a licence key, direct access to me rather than a ticket queue. Stay after the trial and the licence is $250 once, locked at that price for life, with no subscription. What we ask: tell us when something fails, and let us ask you a few questions at the end.
Questions operators ask
Can this replace the software I run now?
If you want photo booth software for Windows running a stills booth on Canon or a webcam, yes. For video, multiple printers, MDB or a non Canon body, not yet, and the list above is the honest boundary.
Will it run my existing hardware?
If your machine runs Windows 10 or 11 with a Canon body and a DNP printer, almost certainly. Tell us your exact camera, printer and reader on the form and we will confirm before we send a key.
What happens after two months?
You decide. There is no card on file, so nothing charges by itself and no machine gets bricked mid event. Stay and it is $250 once for a lifetime licence, held at that price for you permanently. Full detail sits on the VertexBooth software page.
Who is building this?
Vertex Vending Group, in Davie, Florida. We build and place photo booth machines under the SmileMore brand, including the permanent install at Nova Southeastern University. VertexBooth exists because we needed it for our own machines first.
Is my session data going to your servers?
In short, photos live on the booth PC. Delivery by text, email or QR goes through the services you configure. We are not building a business on your guests’ images.
One last thing worth saying plainly. We are early, and the established players have a decade of shipping on us. What we have that they do not is a machine of our own in a lobby, taking real money from real students every day. Every rough edge in this software therefore cuts us before it cuts you.
Every capability in the software, grouped and ticked off, is on the full photo booth software features list.





