Photoshop panel & batch automation
A desktop app that batch-runs your own actions on a whole wedding, and a panel that docks inside Photoshop with your client's approved selections, your PSD templates and your files already in the room.
Sound familiar?
You batch a wedding overnight and find it stalled at photo 340 on a stuck plugin dialog.
Every editing machine in the studio produces a slightly different look.
Album design means hunting for the approved photos, then dragging them in one at a time.
A standing portrait gets cropped into a landscape frame because the template did not care.
You place the same photo on two spreads and only notice at print.
What changes
Add a wedding folder, pick one of your styles, press Start. It runs your own Photoshop actions on every photo. Topaz, Portraiture, Nik and Camera Raw run to completion — stuck dialogs are dismissed automatically, so one bad photo never freezes the queue. Close the app mid-run and it resumes from the exact photo it stopped at.
Styles and action sets sync through the cloud, so the look does not drift between the two editors and the machine in the corner.
Point the panel at your own PSD and it fills your design — your artwork, your frame shapes, your fonts. Rounded, oval and hand-drawn slots all work, because photos are clipped to the template’s real shapes rather than cropped to rectangles. Teach it which rectangles are photo holes once and it remembers that file permanently.
Press Sheets and the whole album is drawn to scale first — every spread, every photo in its frame, nothing built. Swap two photos by clicking them, replace one from disk, take one out. Then press Build and Photoshop does in one pass exactly what you already approved.
Every photo is matched to a frame of its own shape. If one has nowhere to go it is left out and named — not squeezed in, and not marked used, so it stays available for the next spread. You can still overrule it from the preview.
Local files, sheet building, templates and export never talk to the server. A venue with no signal does not stop the album getting built.
Side by side
| What you need | Without a system | With Wedding OS |
|---|---|---|
| Overnight batches | Stalled at photo 340 on a dialog | Dialogs dismissed; resumes after a crash |
| Consistency across machines | Each editor’s own actions | Styles synced from the cloud |
| Album layout | Dragging photos in one at a time | Whole album drawn to scale, then built |
| Templates | Rebuild the design in a new tool | Fills your own PSD, shapes intact |
| Duplicate placement | Noticed at print | Used-marks on every photo |
FAQ
No, and it is not trying to. Wedding OS never builds photo, RAW, album or video editors — it owns the workflow around the tools you already use. The panel brings your approved selections and templates into Photoshop rather than pulling you out of it.
It runs your own action sets, so whatever your actions call, it calls. Topaz, Portraiture, Nik and Camera Raw are handled explicitly: the watchdog dismisses the dialogs plugins leave open, which is what usually kills an unattended batch.
A soak run drove the real production queue through 10,000 images with six failure types injected — crashes, timeouts, plugin failures — verifying every recovery, retry and memory recycle. All checks passed. Photoshop itself is stood in for in that run, because you cannot crash it ten thousand times on purpose; the crash-recovery code is separately unit-tested.
Windows, a Photoshop licence you already own, and a Wedding OS account. The desktop app installs the panel for you and starts the agent in the background.
Yes — layered PSDs for your archive, print-ready JPEGs for the lab, or both at once split into their own subfolders. You can also save edits back as versions and publish a finished spread straight to the client’s album without leaving Photoshop.
Start free on Lite — every feature at solo scale, no card, and a full export any time you want out.
Related: Album selection · All features · Pricing · Studio management software