Choose your language

Choose your login

Support

Mobility Print System Requirements

This page applies to:

Last updated September 15, 2026

Server Requirements

Hardware Requirements

CPU: Any 64-bit Processor (Intel or AMD)**

Memory: 2GB or more, based on printing volume.

Hard Drive: 3GB of free space or more, based on printing volume.

OS Requirements

Windows: Windows 10, 11, Server 2016, 2019, 2022, 2025

Mac: macOS 13+ (Ventura)

Linux:

  • RHEL 8.0+.
  • SuSE 15.0+.
  • Debian 12.0+.
  • Ubuntu 20.0+.
  • Most distributions built on the previously mentioned versions.
  • Distribution need to support GNU glibc 2.28+ and kernel version 3.2 or later, adhering to vendor supported distributions is recommended and will achieve the requirements.

Additional Considerations

  • There are no known issues with Mac devices using the M series (e.g. M1 / M2) processors, but this has not been officially tested or developed for. Emulation (Rosetta) will be used since the app is not written for Apple Silicon. Please see Known Issues when upgrading macOS and iOS for more information.
  • Devices that support ARM architecture, such as the Raspberry Pi, are not currently supported.
  • Windows devices with Arm64 architecture using emulation under Prism are not currently supported.
  • Windows Desktop class systems such as Windows 10/11, allow only 20 simultaneous connections. This means that these systems should only be used as a “server” to host print queue on networks where you expect less than 20 simultaneous print jobs to be processed.
  • An internet connection is required to automatically update the software when new versions are available. For more information, see the How do I update my Mobility Print server? section in the FAQs.

Printer requirements

Mobility Print works with the vast majority of printers. The key requirement is that the printer has a print driver for the server host operating system (for example, a Windows Driver).

Mobility Print supports all printers that have drivers for modern Windows operating systems except label printers and plotters. This is because the drivers for label printers and plotters use non-standard page sizes. If you find any exceptions, or have problems, please let us know.

Client requirements

  • iOS 16.0+
  • macOS 13+ (Ventura) (64-bit)
  • Windows 11, Windows 10 (64-bit and ARM64)
    • Windows S mode is not supported at this time.
  • Android 13.0+
  • ChromeOS with Chrome version 128+

Additional Considerations

  • There are no known issues with Mac devices using the M series (e.g. M1 / M2) processors, but this has not been officially tested or developed for. Emulation (Rosetta) will be used since the app is not written for Apple Silicon. See Known Issues when upgrading macOS and iOS for more information.
  • Other devices that support ARM architecture without the Prism emulation layer, such as the Raspberry Pi, are not currently supported.
  • Administrator level permissions are required in order to install and use the Mobility Print Cloud client.
  • Cloud Print does not support Android or iOS devices. Cloud Print is currently only available for Chromebooks, Windows, and macOS devices. Android and iOS devices can print using Mobility Print, but only when they are connected to the same local network as the print server - not remotely over the internet.

PaperCut NG/MF integration

Mobility Print integrates with PaperCut NG/MF versions 17.0.3 or greater. The Mobility Print Cloud Print feature integrates with PaperCut NG/MF versions 17.0.3 or greater.

Firewall rules

Which protocols and ports to set up depends on the printer discovery method you are going to use.

Auto-update

The following port and URL endpoints must be externally available for auto-updating:

  • 443 TCP (HTTPS), with connections to:
    • https://mobility-print.papercut.com/\*
    • https://mobility-print-standalone.papercut.com/\*
    • https://storage.googleapis.com/pc-mobility-print.appspot.com/\*

With mDNS printer discovery

Client Client software? Printer discovery protocol Server port (for printer discovery) Job delivery protocol Server port (for job delivery)
macOS No mDNS Inbound: 5353 UDP
Outbound: 5353 UDP
IPPS/HTTPS 9164 TCP
iOS No mDNS Inbound: 5353 UDP
Outbound: 5353 UDP
IPPS/HTTPS 9164 TCP
Android Mobility Print extension mDNS
HTTPS
Inbound: 5353 UDP
Inbound: 9164 TCP
Outbound: 5353 UDP
HTTPS 9164 TCP
Chrome Mobility Print extension mDNS
HTTP
Inbound: 5353 UDP
Inbound: 9163 TCP
Outbound: 5353 UDP
HTTP API (encrypted payload) 9163 TCP
Windows Installer mDNS
HTTPS
Inbound: 5353 UDP
Inbound: 9164 TCP
Outbound: 5353 UDP
IPP/HTTP 9163 TCP

With Known Host printer discovery

When setting up Mobility Print with a known host, the following port and URL endpoints must be externally available to be able to retrieve the client setup files:

  • 443 TCP (HTTPS), with connections to:
    • https://www.papercut.com/api/product/mobility-print/latest/client/windows
    • https://www.papercut.com/api/product/mobility-print/latest/client/macos
    • https://www.papercut.com/api/product/mobility-print/latest/client/android
    • https://ios-profile-signing-dot-pc-mobility-print.appspot.com/sign-profile/v1
Client Client software? Printer discovery protocol Server port (for printer discovery) Job delivery protocol Server port (for job delivery)
macOS Mobility Print App HTTPS Inbound: 9164 TCP
Outbound: n/a
IPPS/HTTPS 9164 TCP
iOS Configuration profile HTTPS Inbound: 9164 TCP
Outbound: n/a
IPPS/HTTPS 9164 TCP
Android Mobility Print App HTTPS Inbound: 9164 TCP
Outbound: n/a
HTTPS API 9164 TCP
Chrome Mobility Print App HTTP Inbound: 9163 TCP
Outbound: n/a
HTTP API (encrypted payload) 9163 TCP
Windows Installer HTTPS Inbound: 9164 TCP
Outbound: n/a
IPP/HTTP

IPPS/HTTPS*
9163 TCP

9164 TCP*

* Job delivery protocol and port will switch to IPPS/HTTPS on port 9164 if a trusted certificate is installed on the Mobility Print server. This only applies to the Known Host and DNS discovery methods. Steps can be found in our article Configure Mobility Print to use a trusted TLS/SSL certificate.

With DNS printer discovery

Client Client software? Printer discovery protocol Server port (for printer discovery) Job delivery protocol Server port (for job delivery)
macOS No DNS Inbound: 53 UDP
Inbound: 53 TCP
Outbound: 53 UDP
Outbound: 53 TCP
IPPS/HTTPS 9164 TCP
iOS No DNS Inbound: 53 UDP
Inbound: 53 TCP
Outbound: 53 UDP
Outbound: 53 TCP
IPPS/HTTPS 9164 TCP
Android Mobility Print App DNS
HTTPS
Inbound: 53 UDP
Inbound: 9164 TCP
Outbound: 53 UDP
HTTPS API 9164 TCP
Chrome Mobility Print App DNS
HTTPS
Inbound: 53 UDP
Inbound: 9163 TCP
Outbound: 53 UDP
HTTP API (encrypted payload) 9163 TCP
Windows Installer DNS
HTTPS
Inbound: 53 UDP
Inbound: 9164 TCP
Outbound: 53 UDP
IPP/HTTP

IPPS/HTTPS*
9163 TCP

9164 TCP*

 

* Job delivery protocol and port will switch to IPPS/HTTPS on port 9164 if a trusted certificate is installed on the Mobility Print server. This only applies to the Known Host and DNS discovery methods. Steps can be found in our article Configure Mobility Print to use a trusted TLS/SSL certificate.

With Cloud Print printer discovery

Local (same host)

Client user context service internal/localhost connection only
port 9165 TCP localhost (127.0.0.1)

Inbound

No firewall rules.

Outbound

To register the server and notify it of incoming jobs  
port 443 TCP mp.cloud.papercut.com
port 443 TCP v1.0.3770 and later:notif.mp.cloud.papercut.com, IP(s): 3.13.10.206, 3.147.218.242Deprecated: mqtt.notifications.cloud.papercut.com
To orchestrate the peer-to-peer connection  
port 3478 TCP
port 3478 UDP
global.stun.twilio.com
port 443 TCP
port 3478 UDP
global.turn.twilio.com

Comments

Comments are not available in this preview environment. On papercut.com, this space shows the live Disqus comment thread for this page.