Electronic fax is a service that sends and receives faxes over the internet instead of over a fax machine and a dedicated phone line. The fax number stays. The fax protocol stays. The hardware, the analog line and the paper do not.
The term is used loosely, and several things that are not electronic fax get sold as though they were. This page sets out what the term covers, what it does not, and who it is actually for.
What it includes
A cloud fax service does four things.
It hosts your fax numbers. Numbers live on the provider's infrastructure rather than terminating on a line in your building. Existing numbers can usually be ported; new ones, including toll-free numbers, can be issued.
It receives on your behalf. An inbound fax is answered by the provider, converted to a digital document, and delivered to you, by email, in a web portal, or into another system through an integration.
It sends on your behalf. You submit a document from email, a browser or an application. The provider converts it and transmits it to the destination number using the fax protocol the receiving machine expects, and reports whether the transmission completed.
It keeps the record. Sent and received faxes are stored with timestamps and transmission results, so a fax becomes a searchable document rather than paper in a tray.
The part that makes it work
The receiving end does not have to change. A fax sent from a cloud service arrives at an ordinary fax machine as an ordinary fax. That is the whole reason the migration is practical: you are not asking every clinic, claims processor or county office you deal with to adopt anything.
What it is not
This section matters more than the last one, because most of the confusion is here.
It is not email. Email is often the interface. You send from your mail client and receive in your inbox, but the transmission between the service and the far end is a fax, to a fax number. If your counterparty accepts fax and not email, that distinction is the entire point. Describing cloud fax as "faxing by email" is a fair description of the experience and a misleading description of the mechanism.
It is not a fax machine plugged into a VoIP line. This is the most common false equivalence and the most common source of trouble. Traditional fax was designed for analog lines. The compression and packet loss that go unnoticed in a voice call corrupt a fax transmission, which is why fax over ordinary VoIP fails intermittently, drops pages, or dies on long documents. Handling this properly requires infrastructure built for fax over IP: the case ITU-T Recommendation T.38 exists to cover.
It is not a document management system. A fax service stores what it sent and received. It is not a records system, and treating it as one produces a retention problem rather than solving one.
It is not a secure messaging platform. Encryption in transit and at rest protects the document while the service holds it. Once a fax reaches the destination number, it is a fax: it prints, or it lands in whatever system the recipient runs. A sender does not control the far end.
It is not, by itself, compliance. A service can provide safeguards and contractual terms. It cannot decide what your staff send, to whom, or how long you keep it. That distinction is set out below.
Who needs it
Cloud fax is worth considering when at least one of these is true.
You cannot stop faxing. Counterparties in healthcare, legal, financial services and government frequently require it, and a supplier does not get to overrule a receiving organization's accepted channels.
Your fax hardware is a running cost. A machine, an analog line, consumables and somebody's attention add up quietly, and the line is often the largest part.
Your fax is unreliable since a phone system change. Moving to VoIP and keeping a physical fax machine is the classic cause. This is a solvable problem and cloud fax is the usual solution.
Faxes need to reach people who are not in the building. Remote and multi-site working and a machine in one corridor are not compatible.
You need to know what was sent. If you cannot currently answer "was that document received, and when", a stored transmission record is worth more than the hardware saving.
When it is not the answer
If every counterparty would accept a portal or secure email, and you are keeping fax out of habit, the honest advice is to retire the channel rather than modernize it. Cloud fax is for organizations that have to keep faxing: not an argument that they should.
Compliance, stated precisely
Faxing is not prohibited under HIPAA. The HIPAA Security Rule sets requirements for safeguarding electronic protected health information, and the covered entity remains responsible for meeting them. Where a provider handles PHI on your behalf, a Business Associate Agreement is the instrument that makes the relationship accountable.
The same shape applies elsewhere: the GDPR governs personal data of people in the EU whatever channel it travels on, and PCI DSS governs cardholder data. What a provider can offer is encryption, access control, an audit trail and contractual terms. What it cannot offer is a guarantee about your own workflows.
When a supplier lists standards in its marketing, treat that as an invitation to ask what is certified, by whom, against which version, and when it was last assessed.
Where to go next
Guide to Electronic Fax covers the topic in full, including how the migration works. If the question is budget, How Much Does Electronic Fax Cost? explains what drives the number, and What to Look For in Electronic Fax is the evaluation list.
Or tell us what you are working with: page volumes, the numbers that must keep working, and where the documents need to end up.
Sources
- ITU-T Recommendation T.38: real-time Group 3 facsimile over IP networks.
- 45 CFR Part 164, Subpart C: HIPAA Security Rule, Electronic Code of Federal Regulations.
- Regulation (EU) 2016/679 (GDPR), official text.