What is a RIP hot folder — and how to automate it
A hot folder is a directory that RIP software watches continuously: any print-ready file dropped into it gets picked up and queued for printing automatically, with the color profile and settings assigned to that folder. RIPs like NeoStampa, the software that drives many DTF printers, use hot folders as their standard automation entry point — no clicking through an import dialog per job.
What a RIP actually does
RIP stands for Raster Image Processor. It converts artwork (PNG, TIFF, PDF) into the exact droplet instructions a specific printer lays down — handling color management, ink limits, white-ink underbase generation, and halftoning. Every professional DTF printer runs behind a RIP; the hot folder is simply the conveyor belt that feeds it.
The half-written file problem
Hot folders have one classic failure mode: the RIP watches for new files and grabs them the moment they appear — even if the file is still being written. A 300 DPI gang sheet PNG can be hundreds of megabytes; if the RIP ingests it mid-copy, you get a truncated, corrupt print and wasted film. The fix is an atomic write: write the file under a temporary name the RIP ignores, then rename it to its final name in one instantaneous operation. The RIP only ever sees complete files.
Feeding a hot folder from the cloud
Cloud production software and an on-prem RIP have to meet somewhere, and that somewhere is the hot folder on the RIP PC. The clean pattern is a small agent that runs on that PC and polls the cloud for print-ready sheets — outbound requests only, so there are no inbound firewall holes, port forwarding, or VPNs. When a sheet is ready, the agent downloads it, writes it atomically into the right hot folder for that printer and film width, and reports back.
KOVA ships a zero-dependency agent (~90 lines of plain Node.js) that runs on the RIP PC, polls for queued sheets, and drops them into your NeoStampa hot folder with an atomic temp-then-rename write. Per-printer routing maps each print profile to its own folder. Click “Send to RIP” in the browser; the file appears in the print queue.
See the RIP integrationFrequently asked questions
Virtually all production RIPs support them — NeoStampa, Cadlink Digital Factory, Kothari Print Pro, and others. The folder-watching behavior is standard; the file naming and settings mapping differ per RIP.
Network copies are exactly how half-written files get ingested — the RIP sees the file appear at byte zero. An agent that writes locally and renames atomically eliminates the race condition.
Not with a polling agent. The agent only makes outbound requests to the cloud, which works through firewalls and NAT without any network configuration.