InDesign Desktop vs. InDesign Server for Automation with Enfocus Switch
When setting up automated publishing workflows using Enfocus Switch, one of the biggest decisions you'll face is whether to use Adobe InDesign Desktop or Adobe InDesign Server. Both can technically be integrated into a Switch-based environment, but the differences between them are important to understand—especially when it comes to stability, licensing, and unattended automation.
This article walks through both options, compares their features, and offers a summary to help you choose the best path for your setup.
HOW AUTOMATION MIGHT WORK WITH EACH
Using InDesign Desktop
At first glance, it might seem tempting to just use the version of InDesign you're already familiar with: the Desktop version. It runs in a traditional GUI environment and can be manually controlled. If you're planning a workflow where someone is always present to log in, start InDesign, and click a few buttons, then this could work.
Some users have even found ways to semi-automate this setup by using scheduled tasks or scripting tools to quit and restart InDesign or Enfocus Switch at specific intervals. But there are caveats: InDesign Desktop needs an interactive user session, it throws up pop-up dialogs, and it can silently fail if something goes wrong in the background.
Using InDesign Server
InDesign Server is the behind-the-scenes powerhouse Adobe designed for exactly this type of thing. It doesn't have a GUI. It runs in the background, can be installed as a Windows service, and communicates over SOAP or scripting interfaces. It's robust, reliable, and built for headless automation. When paired with Switch, it becomes a true hands-off solution.
It does require a separate license and may seem a little intimidating at first, but if you're serious about automation, it's the better long-term option.
Feature Comparison: InDesign Desktop vs. InDesign Server
Feature | InDesign Desktop | InDesign Server |
---|---|---|
GUI Required | Yes | No |
Can run without a logged-in user | No | Yes |
Supports background services | No (workarounds only) | Yes |
Built for automation | No | Yes |
Licensing for automation | No | Yes |
Handles pop-ups and alerts | Manual intervention needed | Silent/background execution |
Multi-instance support | No | Yes (single instance for Switch) |
Crash recovery | Manual | Built-in job queue support |
Communication | ExtendScript, GUI-based | ExtendScript, SOAP, CLI |
Summary: What's Possible and What's Not
Automation Task | Desktop InDesign | InDesign Server |
---|---|---|
Run as a Windows Service | ❌ Yes, but unreliable | ✅ Supported |
Supports auto-restart workflows | ⚠️ Requires user login/session | ✅ Headless support |
Process hot folder jobs unattended | ✅ Yes | ✅ Yes |
Integration with Switch using DesignMerge App | ✅ Fully supported | ✅ Fully supported |
Adobe licensing-compliant automation | ❌ Technically, No | ✅ Yes |