Requirements & recommended hardware

Gear

What you need to run Virtual.ink, and what we recommend once you're past the minimum.

Did you know?

Virtual.ink isn't limited to this desktop app. It's also available on Android, iOS, and as a plugin for Premiere and After Effects.

Computer requirements

Virtual.ink runs from one live camera source. A second camera is optional, it feeds mashup renders (for example a behind-the-scenes shot next to the finished light-painting result on Basic and up), it does not combine with the main feed to build the live effect itself.

CPU, GPU, and storage needs scale mainly with your license tier's resolution ceiling: Starter (720p), Basic (1080p), Pro and Pulse (4K, plus ProRes recording).

Windows

  • Windows 10 or 11, 64-bit
  • Intel Core i5 or equivalent for 720p/1080p, Intel Core i7 or equivalent (or better) for 4K and ProRes recording
  • Any modern integrated GPU (Intel Iris or newer) for standard use, a dedicated NVIDIA GPU is recommended at 4K and also enables hardware-accelerated recording (NVENC) for lower CPU load

Mac

  • Apple Silicon (M-series) only, the current build does not run on Intel Macs
  • A base M-series chip is enough for 1080p and most effects, a Pro/Max/Ultra chip helps for 4K and ProRes recording
  • Recording uses Apple's built-in hardware encoder automatically, no dedicated GPU needed

All configurations

  • 8 GB RAM minimum, 16 GB recommended for 4K or ProRes recording
  • 700 MB available storage for the app itself, recording storage scales with resolution, quality preset, and duration, 4K ProRes files are especially large
  • Internet connection for license login
  • One dedicated USB 3 port per capture device (one for the main camera, a second only if you add the optional mashup source)

Camera and capture options

Virtual.ink works with any camera that outputs a clean HDMI signal and any standard HDMI capture card. HDMI capture generally gives the most flexibility and the best image quality. If you already have a camera and capture card, there's a good chance they'll work, request a free trial before purchasing to confirm compatibility with your specific hardware.

Not sure if your camera qualifies? Check the supported camera list first. If it's not listed, check your camera's manual for a clean HDMI output option (no overlays, no on-screen display). Most cameras released after 2021 can output clean HDMI.

Option 1: HDMI capture

  • Single camera: any camera with clean HDMI output, plus a compatible HDMI capture card.
  • Dual camera: two cameras with clean HDMI output, plus two compatible HDMI capture cards.

Option 2: Camera through USB

  • Simpler setup, with more limited image quality and control than HDMI.
  • Canon: Windows only, up to 1024 px wide over USB. The simplest setup path. Compatible models include most Canon DSLRs, some newer mirrorless models (M50, R, RP, M6ii), and some PowerShot models (G7xiii, G5xii).
  • Sony: works with cameras that include a built-in webcam mode, usually up to 1280 px wide.
  • GoPro: direct USB can reach 1920x1080 on models such as the GoPro 10, 11, 12, and 13.
  • Only one camera can run over direct USB, but it can be combined with a second camera connected through HDMI capture.

Option 3: Webcam

  • Logitech Brio, or any webcam that lets you control settings manually.

Camera connection

There are two practical ways to connect a camera to Virtual.ink. Both make the camera appear as a video input that the app can use in Live.

Option 1: HDMI capture card

Connect the camera's HDMI output to a USB capture card, then connect the capture card to the computer.

This is the most reliable path for production use. It supports the widest range of cameras, resolutions, and frame rates, and it avoids most of the limits that come with vendor webcam utilities.

  • Best fit for events, photobooths, and any setup that needs to stay stable for long sessions.
  • Prefer USB 3 capture devices that expose stable 1080p25 modes.
  • Use clean HDMI output with no focus boxes, menus, or camera overlays.
  • For dual-camera setups, prefer one dedicated USB path per capture device.

Recommended capture cards:

Device Best for Notes
Inogeni 4K2USB3 Preferred choice for Virtual.ink Very stable, strong mode support, good fit for fixed 25 fps workflows
Magewell USB Capture HDMI Best alternative Reliable professional capture with low latency
Elgato HD60 X Good fallback Consumer device, still solid when passthrough also matters
Elgato Cam Link 4K Single-camera fallback Compact and common, less ideal for dual fixed-25-fps rigs

Avoid generic HDMI-to-USB dongles sold under labels such as USB Video or HDMI Capture. They often expose unstable modes, ignore MJPG requests, or fall back to bandwidth-heavy formats that can collapse to very low frame rates.

Option 2: Manufacturer webcam software over USB

Camera makers also offer webcam utilities that expose the camera directly over USB. This is simpler to wire, but it usually comes with lower resolution ceilings, fewer controls, and more compatibility risk.

  • Canon, Sony, Nikon, GoPro, Fujifilm, Panasonic, and others all have some form of webcam workflow.
  • In practice these utilities are best for lighter setups, teaching, or temporary rigs.
  • HDMI capture is still the better default for event production.

Typical limitations:

  • Resolution and frame rate are often capped below what the same camera can output over HDMI.
  • Support varies by exact model, firmware, operating system, and utility version.
  • Multi-camera support is often limited or locked behind a paid tier.

Why 25 fps is usually the safer target

Virtual.ink does not benefit much from a capture path pushing far more frames than the app actually needs. In most real setups, a stable 25 fps feed is better than an unstable 50 or 60 fps feed.

  • Lower bandwidth on USB and the host chipset.
  • Fewer dropped or duplicated frames when running two cameras, recording, and preview together.
  • Easier to keep both cameras on a predictable fixed-rate path.

If your device only exposes 1080p60 it can still work, but it is usually not the ideal match for a two-camera Virtual.ink rig.