On-Premise Fax Server or Cloud Fax: Which Should You Choose in 2026?

Short answer: in 2026, an on-premise fax server is only justified in three situations — high, steady volume (several hundred pages a day), deep integration with a line-of-business application hosted on site, or a regulatory constraint requiring that documents never leave your network. Everywhere else, cloud fax (fax-to-email) costs less, removes the burden of maintaining T.38 and the gateway, and is back up and running within minutes after an outage. The real deciding factor is neither price nor technology: it is who is willing to be woken up at night when the line goes down.

About MondialFax. This article is an architecture comparison, independent of any vendor or carrier. MondialFax sends faxes free of charge and without registration to seven destinations (France, Belgium, Germany, Spain, Italy, Portugal, Canada). It does not assign a number and does not handle inbound faxes: the receiving scenarios described below assume a third-party provider. See receiving a fax and our fax-to-email guide.

In many companies there is still a machine nobody looks at any more. It sits in the comms room, between the NAS and the UPS, and it still carries a label written in marker pen: "FAX — DO NOT SWITCH OFF". It is a fax server. It has been running since 2014, maybe 2011. The person who installed it has left. The maintenance contract has been renewed three times without anyone rereading what it actually covers.

Then the analogue line feeding it was cut off — Orange completed the technical shutdown of the PSTN in France according to the schedule announced to Arcep, region by region, after new line sales stopped back in 2018. And that is when a decision has to be made. Put the server back on track with a SIP gateway, or move everything to the cloud.

This article will not decide for you. It gives you the figures, the technical friction points and the compliance questions that tip the balance.

Three architectures, not two

People often frame it as "on-premise server" versus "cloud", as if it were binary. In practice there are three set-ups, and the second is the most common — and the most misunderstood.

1. The on-premise fax server

Fax software (often a hardware fax board or a software stack) installed on a physical or virtualised server in your own premises. It handles the queue, retries, confirmations, archiving, and interfaces with the company directory. Historically it was connected to analogue lines or to an ISDN BRI/PRI circuit.

Once the PSTN was switched off, it has to be connected to a SIP trunk — that is, to an IP telephony provider — and to speak T.38, the ITU standard that carries a fax over IP by "replaying" it as a data stream rather than as sound.

2. The ATA gateway: the false compromise

Many companies have simply plugged their old fax machine or their server into an ATA adapter connected to the business router. It is quick, it is cheap, and it works… sometimes. It is also the leading cause of transmission failures recorded in 2026: compressed voice (the G.729 codec, or G.711 with silence suppression, echo cancellation, dynamic jitter buffer) destroys the fax modulation tones.

We covered the settings that rescue these installations in our guide to fax over VoIP and T.38 failures. The essential point here: an ATA gateway is not an architecture, it is a stay of execution. On an entry-level ATA, enabling the G.711 a-law codec in passthrough, disabling echo cancellation and fixing the speed at 9,600 bps solves plenty of cases — but you remain at the mercy of the slightest change on the carrier's side.

3. Cloud fax (fax-to-email)

The provider hosts the fax infrastructure and gives you a web interface, a dedicated email address or an API. Incoming faxes arrive as PDFs in a mailbox, outgoing ones are sent from a mail client or a portal. You no longer have a fax board, a SIP trunk or T.38 to monitor — the provider carries that complexity.

The real cost: what the quotes don't show

A fax server looks "already written off". That is the classic sunk-cost illusion. Here are the line items you really need to add up over three years.

The item that tips the calculation is almost never the licence: it is the "administration time" line. A thirty-person SME that works out the fully loaded hourly cost of its IT person often discovers that its fax server costs more in human attention than in hardware euros.

Conversely, an organisation sending 400 pages a day — a laboratory, an imaging centre, a logistics hub — sees the maths reversed: the per-page pricing of cloud offerings quickly exceeds the fixed cost of a properly sized SIP trunk.

The approximate threshold observed in the field sits at around a few thousand pages a month. Below that, the cloud almost always wins. Above it, get the spreadsheet out and negotiate volume tiers.

What breaks in a fax server in 2026

T.38 is not guaranteed end to end

T.38 works if every link in the chain supports it: your server, your SBC or router, your carrier, the transit carrier, and the recipient's equipment. A single link that reverts to compressed audio and the transmission fails. Carriers advertise "T.38 compatible", which does not mean "T.38 guaranteed to all international destinations".

That is why an on-premise server, even perfectly configured, still produces failures to certain countries. The cloud provider, on the other hand, often has several routes and switches automatically. You only have one.

The OS ages faster than the fax

A fax server is a server like any other: it has to be patched. Yet many fax software stacks are certified on older OS versions, which encourages postponing updates. The result: a machine exposed to the internal network, handling frequently sensitive documents (medical records, legal deeds, identity papers), that has not seen a patch in a long time.

If you keep an on-premise architecture, plan at the very least for a UPS with network management to avoid abrupt shutdowns that corrupt the queues, plus monitoring that raises an alert when the queue stalls.

The skills are disappearing

This is the most underestimated risk. T.38, SIP signalling, debugging a fax that fails 34% of the way through page 2: these skills are becoming scarce. A reference guide on IP telephony in the enterprise remains a worthwhile investment for a team keeping an in-house infrastructure, but it is no substitute for someone who can read a SIP trace.

Compliance and GDPR: the argument isn't the one you think

The most frequent objection to the cloud is: "our documents must not leave the company". It is a legitimate concern, but often badly framed.

The GDPR does not prohibit outsourcing. It requires a processor contract compliant with Article 28, clear information about hosting locations, a legal basis for the processing, and appropriate technical measures (Article 32). The CNIL has repeatedly pointed out that using a processor remains possible as long as the controller retains control over the purposes and verifies the guarantees offered.

The concrete questions to put to a cloud fax provider:

• Where are the received PDFs physically stored, and for how long?
• Is the provider subject to extraterritorial legislation (Cloud Act)?
• Is there encryption at rest as well as encryption in transit?
• Does the contract provide for deletion and return of the data at the end of the relationship?
• Is there access logging that you can review yourself?

For health data the rule is stricter: hosting falls under HDS certification (health data hosting provider), governed by the French public health code and overseen in France by the Agence du numérique en santé. A medical practice moving its faxing to the cloud must check this point before anything else — and, in parallel, consider the use of MSSanté, which we discuss in our article on fax in the healthcare sector.

By the same token, keeping the server in-house exempts you from nothing. An unencrypted server, with no access control, whose PDFs sit in an open network share, is less compliant than a certified provider. Our guide to fax confidentiality and the GDPR sets out the minimum expected measures.

The decision framework

Stay on an on-premise server if…

• You consistently exceed a few thousand pages a month.
• Your line-of-business software (DMS, hospital information system, notarial practice software) integrates natively with the fax stack and rewriting it would be expensive.
• A contractual or sector-specific constraint requires that documents never leave your network perimeter.
• You have in-house SIP/T.38 expertise and genuine on-call cover.

Move to the cloud if…

• Your volume is irregular or low, with occasional peaks.
• Your IT team is small, shared or outsourced.
• You want incoming faxes to be readable from a mobile — see our guide to sending a fax from a smartphone.
• You no longer have a comms room worthy of the name, or you are shutting down your on-site servers.
• You need to keep your legacy number and port it cleanly — a topic covered in keeping your fax number after the PSTN switch-off.

The hybrid set-up, taken seriously

There is a third way, rarely put forward in quotes: keep outbound faxing in-house for bulk sends generated by the line-of-business software, and outsource inbound to a fax-to-email service. You halve the maintenance surface, you eliminate the question of incoming numbers and stalled queues, and you keep the application integration. This is often the most rational solution for mid-sized organisations.

Migration, step by step

1. Take an inventory of the fax numbers actually in use. In half of all cases, two thirds of the DDIs have received nothing in a year. Your carrier's call logs are enough.
2. Measure the volume over a rolling twelve months, inbound and outbound separately. It is the only data point that drives the financial decision.
3. Identify the integrations: which applications drop files into the server's queue? Who consumes the confirmations?
4. Test before you cut over. Order a temporary cloud number, send to your five most critical recipients, including those abroad — dialling codes and international routes hold surprises, as explained in sending a fax abroad.
5. Port the numbers, never the other way round: you don't disconnect first.
6. Retrieve the archive. The faxes received over recent years are on the server's disk. Export them to durable storage — an encrypted external hard drive at minimum, ideally a backup in three copies — before any decommissioning. The applicable retention periods are detailed in archiving your faxes.
7. Decommission properly: secure disk wiping, trunk cancellation, and an update to your record of processing activities.

What to do with the hardware once the migration is complete

A decommissioned fax server contains documents. Do not resell it as is, and do not drop it off at a recycling centre without processing it first. Software erasure of the disks with a recognised utility, or failing that physically removing the drives, is the bare minimum. For teams regularly handling end-of-life equipment, a precision screwdriver kit avoids damaging the fixings and makes it easy to extract the storage media cleanly.

The office fax machine, for its part, often retains value as a scanner. If you keep it, an automatic document feeder in good condition and a stock of compatible cartridges are enough to keep it going for a few more years in that secondary role. Our article on the end of life of the fax machine sets out the options.

Frequently asked questions

Can a fax server work without a PSTN line?

Yes, provided it is connected to a SIP trunk that supports T.38, or to a correctly configured ATA gateway. The PSTN has no longer been sold in France since 2018 and its technical shutdown took place geographical area by geographical area according to the schedule published by Orange and monitored by Arcep.

Is cloud fax less reliable than an on-premise server?

For international destinations, generally the opposite: a provider has several outbound routes and switches automatically when one fails. An on-premise server depends on a single carrier. On the other hand, you depend on the provider's availability, hence the importance of a written SLA.

Can I keep my fax number when moving to the cloud?

Yes, through geographic number portability, just as for a voice line. The process is initiated with the gaining provider, using your RIO code. Never cancel the old line before the port has gone through.

Is cloud fax GDPR-compliant for a medical practice?

It can be, but you need to check the host's HDS certification, the data location and the existence of an Article 28-compliant processor contract. Without all three, the answer is no.

Should you keep a physical fax machine as a backup?

Rarely useful in 2026: without an analogue line, it will not work anyway. It is better to arrange backup access to the provider's web portal from a device outside the corporate network.

In summary

• Three architectures coexist: on-premise server on a SIP trunk, ATA gateway (a technical stay of execution), and cloud fax.
• The deciding cost is not the licence but the administration time and the cost of an out-of-hours outage.
• The economic threshold sits at around a few thousand pages a month: below that, the cloud almost always wins.
• T.38 is never guaranteed end to end; a multi-route provider absorbs international failures better than a single carrier.
• The GDPR does not prohibit outsourcing: it requires an Article 28 contract, a known data location and verifiable security measures — plus HDS certification for health data.
• The hybrid set-up (in-house sending, cloud receiving) is often the most rational for mid-sized organisations.
• Migrate in the right order: inventory, volume measurement, testing, number porting, archive export, secure decommissioning.