**How Long Does a Fax Take? Transmission Time Calculator**

> Estimate how long a fax takes from its pages, resolution, modem speed and line type, with the T.30 call phases explained and why VoIP runs slower than the modem.

Source: https://faxvio.com/tools/fax-transmission-time/ · updated: 2026-09-06

[Home](https://faxvio.com/) [Free tools](https://faxvio.com/tools/) Fax transmission time calculator: how long a fax takes, page by page

**Free tool** · runs in your browser · nothing is uploaded

# Fax transmission time calculator: how long a fax takes, page by page

A fax is a phone call between two machines, and the call has a fixed shape: dial, handshake, one page at a time, a confirmation after each, hang up. Put in the pages and the line, and the calculator adds up that shape.

Pages

Resolution Standard · 204 × 98 dpi Fine · 204 × 196 dpi

Connection speed V.27ter · 4,800 bit/s V.29 · 9,600 bit/s V.17 · 14,400 bit/s V.34 · 33,600 bit/s (Super G3)

Page content Light text (a letter) Dense text (a contract) Form with graphics Photo or scanned image

Line Ordinary phone line (PSTN) VoIP (T.38 or G.711)

Error correction ECM on T.30 Annex A. Cleaner pages, longer calls on a noisy line.

≈ 2 min 6 s

Range **1 min 41 s – 2 min 31 s** · 3 pages · Fine · 204 × 196 dpi · 14,400 bit/s

- Call setup, handshake and training: **20 s**
- 3 × page (30 s of data + 4 s MPS/MCF): **1 min 43 s**
- EOP, final confirmation, disconnect: **3 s**

ECM adds about 10 % on a clean line and far more on a noisy one, where blocks are retransmitted.

## How the transmission time calculator works

The calculator adds up the phases of a Group 3 fax call as ITU-T Recommendation T.30 defines them. A call begins with dialling, ringing and the exchange of the calling and called tones, then a handshake in which the receiver announces what it can do and the sender chooses the speed, then a training sequence; the calculator budgets 20 seconds for all of that. Each page is then sent as compressed image data at the negotiated modem rate, and after each page the sender asks the receiver whether it got the page and waits for the answer, which costs about 4 seconds of signalling and retraining per page. After the last page the sender signals the end of the procedure, waits for the final confirmation and disconnects, another 3 seconds. Total time is setup plus pages times the per-page time plus teardown, and the range shown is that figure plus or minus 20 percent.

The per-page data time comes from the page’s size in bits divided by the modem rate. Under ITU-T Recommendation T.4 a fax line is 1,728 picture elements across a 215 mm width; a 297 mm page holds 1,145 lines at the standard 3.85 lines per millimetre and 2,290 at the fine 7.7, rounded. Those raw bits are compressed before transmission with T.4’s Modified Huffman or Modified READ coding, and how well they compress depends entirely on what is on the page: the calculator assumes roughly 20:1 for a light page of text, 10:1 for dense text, 6:1 for a form with boxes and logos, and 2.5:1 for a photograph or a scanned image with grey tones dithered into dots. Those ratios are typical results, not a standard, and they are the largest source of uncertainty in the estimate. Error correction mode adds about 10 percent on a clean line; a VoIP line caps the rate at 14,400 bit/s and adds 15 percent for retrains, for reasons explained further down.

## What happens during a fax call

ITU-T T.30 divides a fax call into five phases, lettered A to E, and every fax machine and fax gateway made since 1980 follows them. Knowing the phases is what turns “it is still sending” from a worry into a timeline.

1. **Phase A, call establishment.** The sender dials and, while the line rings, emits the CNG calling tone, a 1,100 Hz beep every three seconds that tells whoever answers that a fax machine is calling. The receiver answers with the CED called-station tone at 2,100 Hz. This is the part a person hears if they pick up a fax line by mistake.
2. **Phase B, pre-message procedure.** The receiver sends its Digital Identification Signal, DIS, listing the speeds, resolutions, paper sizes and coding schemes it supports. The sender replies with a Digital Command Signal, DCS, choosing one combination, and then sends a training sequence at the chosen modem speed. If training fails, the sender drops to a lower speed and tries again; each drop costs seconds.
3. **Phase C, message transmission.** The compressed image data of one page is sent at the negotiated rate. This is the only phase whose length depends on the page itself.
4. **Phase D, post-message procedure.** After the page the sender sends Multi-Page Signal, MPS, if more pages follow, or End of Procedure, EOP, after the last. The receiver answers with Message Confirmation, MCF, if it decoded the page acceptably, or Retrain Positive or Retrain Negative if it wants the next page at a different speed or the same page again. The MCF is the receiver’s acknowledgement, and it is what a transmission receipt is built on.
5. **Phase E, call release.** The sender sends Disconnect, DCN, and both ends hang up.

Faxvio shows a fax as **Delivered** only when its carrier reports that the MCF for the last page arrived, and marks it **Could not be delivered — pages returned** when the call ended without one. That is the whole reason the status can stay at Transmitting for minutes: the app is waiting for the same signal a fax machine waits for. [What Delivered means in Faxvio](https://faxvio.com/) is explained on the home page.

*The five phases of a T.30 fax call and what each costs in time*

| Phase | Signals | Typical time |
| --- | --- | --- |
| A · Call establishment | Dial, ring, CNG 1,100 Hz, CED 2,100 Hz | About 10–15 s, more on international routes |
| B · Pre-message procedure | DIS from the receiver, DCS from the sender, training (TCF) | About 5–10 s; each failed training adds a retry at a lower speed |
| C · Message transmission | T.4-coded page data at the negotiated rate | 10 s to 2 min per page, set by content and speed |
| D · Post-message procedure | MPS or EOP from the sender, MCF (or RTP/RTN) from the receiver | About 4 s per page including any retrain |
| E · Call release | DCN | About 3 s |

***A two-page fax of dense text in fine resolution at 14,400 bit/s takes about 1 min 31 s, and only 60 seconds of it is page data.** Grey is setup and training, black is the pages, green is the receiver’s MCF confirmation after each page, gold is the disconnect. Drawn to scale from the calculator’s model. Free to reuse with a link to this page*

## Which modem speeds do fax machines use?

Group 3 fax uses a family of ITU-T modem Recommendations, and the two machines on a call negotiate the fastest one both support and the line will carry. The receiver lists its capabilities in DIS; the sender picks in DCS; training confirms the line can actually sustain the choice, and if it cannot, the sender steps down. That is why the speed printed on a fax machine’s box is a ceiling, not a promise.

*Fax modem standards and their maximum rates*

| Recommendation | Max bit/s | First published | Note |
| --- | --- | --- | --- |
| ITU-T V.27ter | 4,800 | 1976 | The first Group 3 fallback rate; every fax machine must still support it |
| ITU-T V.29 | 9,600 | 1976 | Mandatory in Group 3; the rate VoIP carriers recommend on unstable lines |
| ITU-T V.17 | 14,400 | 1991 | The usual speed of a fax over an ordinary phone line or T.38 |
| ITU-T V.34 | 33,600 | 1994 | “Super G3”; both machines must support it, and it rarely survives T.38 version 0 |

V.27ter and V.29 are the mandatory pair every Group 3 machine carries, at 2,400 and 4,800 bit/s and at 7,200 and 9,600 bit/s respectively. V.17 raised the ceiling to 14,400 bit/s in 1991 and is the rate most calls settle on. V.34, marketed as Super G3, reaches 33,600 bit/s and roughly halves the page time, but only when both machines support it and the path between them is a real analogue circuit, which over modern networks it seldom is.

## Why a page takes 30 to 60 seconds at 14,400 bit/s

A fine-resolution page is about four million raw bits. At 14,400 bit/s that would be over four and a half minutes uncompressed, and nobody would fax anything. T.4’s coding shrinks it by describing each scan line as runs of white and black rather than pixel by pixel, which is why the time depends on the page: a letter with wide margins is mostly long white runs and compresses twentyfold, while a scanned photograph, dithered into a pattern of alternating dots, barely compresses at all. The calculator’s default, a page of dense text, comes to 395,712 bits after compression and 27 seconds on the line before error correction, plus the 4 seconds of MPS and MCF around it.

Providers that bill by the minute put a number on this. eFax’s published international rate page states that its per-page rates apply to pages that take less than 60 seconds to transmit and that this covers approximately 90 percent of all fax pages; that is the provider’s own figure, but it matches what the arithmetic above predicts for text at 14,400 bit/s. Faxvio bills by the page, not the minute, so a slow page costs the same as a fast one; the time matters only for how long you wait for the receipt.

***The same page size, four contents: a light letter is a 19-second page at 14,400 bit/s and a scanned photograph a 125-second one.** Fine resolution, ECM on, including the 4-second confirmation after each page; from the calculator’s compression assumptions (20:1, 10:1, 6:1 and 2.5:1). Free to reuse with a link to this page*

*Per-page time at 14,400 bit/s by content and resolution, ECM on, including the per-page confirmation*

| Page content | Assumed compression | Standard 204 × 98 | Fine 204 × 196 |
| --- | --- | --- | --- |
| Light text | 20:1 | 12 s | 19 s |
| Dense text | 10:1 | 19 s | 34 s |
| Form with graphics | 6:1 | 29 s | 54 s |
| Photo or scanned image | 2.5:1 | 1 min 4 s | 2 min 5 s |

*Estimated time for a fine-resolution fax of dense text, ECM on, ordinary phone line*

| Pages | 9,600 bit/s | 14,400 bit/s | 33,600 bit/s |
| --- | --- | --- | --- |
| 1 | 1 min 12 s | 57 s | 40 s |
| 3 | 2 min 51 s | 2 min 6 s | 1 min 14 s |
| 5 | 4 min 30 s | 3 min 14 s | 1 min 48 s |
| 10 | 8 min 36 s | 6 min 5 s | 3 min 13 s |
| 20 | 16 min 50 s | 11 min 48 s | 6 min 2 s |
| 50 | 41 min 30 s | 28 min 54 s | 14 min 31 s |

Computed from the calculator’s model; real calls vary with the page content, the receiving machine and the line, so read each figure as the middle of a range about 20 percent either side.

## What error correction mode does to the time

Error correction mode, defined in Annex A of T.30, splits each page into blocks of frames with checksums. The receiver reports which frames arrived damaged and the sender retransmits only those, so a line hit that would otherwise print as a streak across the page is repaired invisibly. The cost is time: on a clean line ECM adds framing overhead and a short exchange per block, which the calculator prices at about 10 percent, and on a noisy line every retransmission adds to the call, sometimes doubling it. Fax carriers that route over the internet generally advise switching ECM off on lines that show repeated retransmissions, because a longer call over an unstable path is more likely to drop than a slightly imperfect page is to be rejected.

## Why a VoIP line is slower than the modem’s number

Almost every fax sent from a phone app, Faxvio included, leaves the carrier as a voice-over-IP call and is converted to an analogue signal only at the far end. Two mechanisms carry fax over IP. T.38 is a Recommendation of its own: the gateway demodulates the fax signal and sends the image data and the T.30 signalling as packets, and the gateway nearest the receiver remodulates it. G.711 pass-through instead treats the fax tones as ordinary audio and sends them through the voice codec uncompressed. T.38 is the more robust of the two, and it is what carriers try first when they detect a fax tone; if the far end does not answer the T.38 request, the call continues in G.711.

Both mechanisms cost speed. The widely deployed version 0 of T.38 does not carry V.34, so a Super G3 machine on a T.38 call falls back to V.17 and 14,400 bit/s at best, which is why the calculator caps the rate over VoIP. Packet loss or jitter on the path shows up to the modems as line noise, and their response is to retrain at a lower speed or, under ECM, to retransmit blocks; the calculator adds 15 percent for that. Telnyx’s support documentation on T.38 and G.711 fax goes further and recommends limiting calls to 9,600 bit/s, using normal rather than fine resolution and turning ECM off on unstable routes, on the grounds that a shorter call is a more reliable one. Choose VoIP in the calculator and 9,600 bit/s to see what that advice costs in time.

## International faxes

Distance does not change the page time; the two machines agree a rate and the bits take as long as they take. What an international call adds is in Phase A: longer dialling and ringing, and on some routes a gateway or two more between the carrier and the receiving machine, each a place where packets can be delayed. A fax to Japan or Korea from a US carrier typically spends a few more seconds in setup and is otherwise identical. Faxvio sends to [37 countries](https://faxvio.com/destinations/) at the same page price, and the timing model here applies to all of them.

## What to do while the app says Transmitting

Nothing. Leave the app, or leave the phone; the call runs from the carrier’s gateway, not from the device, and the result arrives as one notification. Faxvio prints the time of the last status update under the state, so a fax that has said Transmitting for four minutes with an update forty seconds ago is a ten-page document doing what the table above predicts. A status that has not changed in 20 minutes is labelled stale, which means the carrier has stopped reporting and the app is waiting on its poller rather than a live event. If the call ends without the last MCF, the fax is marked as returned and the pages go back to your balance; you can send it again, and the free retry is the returned pages.

## Bottom line

A fax of 3 pages of dense text in fine resolution takes about 2 min 6 s at 14,400 bit/s over an ordinary line, of which roughly 23 seconds is call setup and release and about 34 seconds is each page with its confirmation. Under ITU-T T.30 every page must be acknowledged by the receiving machine before the next is sent, and that acknowledgement, the MCF after the last page, is what Faxvio waits for before it stamps a receipt Delivered. Text pages take 30 to 60 seconds at 14,400 bit/s, images can take two minutes, a VoIP path caps the speed at 14,400 and adds retrains, and none of it changes the price, because Faxvio charges by the page, not by the minute.

## Then send it from your phone

Faxvio scans the pages, dials the number and hands you a transmission receipt when the receiving machine confirms. Pay per page, no subscription, first page on us.

[Download on theApp Store](https://apps.apple.com/app/apple-store/id6808320984?pt=127157325&ct=seo_site&mt=8) Android soonGoogle Play

## Questions people ask

How long does a one-page fax take?

About 57 s at 14,400 bit/s for a dense page in fine resolution, most of it call setup. A light page of text in standard resolution can be under 40 seconds; a scanned photo can take two minutes on its own.

Why does my fax say Transmitting for several minutes?

Because a fax is transmitted at modem speed, one page after another, and each page waits for the receiving machine to confirm before the next begins. A ten-page fax at 14,400 bit/s is around six minutes even on a clean line. Faxvio shows the time of the last update under the status and labels it stale after 20 minutes; it never marks a fax Delivered until the receiving machine has confirmed the last page.

Does resolution change the time?

Yes. Fine resolution (204 × 196 dpi) scans 7.7 lines per millimetre against 3.85 for standard, so a page carries twice the raw bits and takes roughly twice as long to send. The compression standard recovers some of that on text, none of it on images.

Does the calculator know how long my fax will actually take?

No. It applies published modem rates and typical compression ratios to a fixed call shape. The receiving machine sets the speed it will accept, the line decides how many retrains happen, and the content decides how well the page compresses. Treat the range as the honest answer and the single figure as its middle.

Is a fax over the internet faster?

Usually not. T.38 carries the same modem signalling as packets, and most gateways negotiate no faster than 14,400 bit/s. Where the internet helps is on the sending side: Faxvio uploads the pages in seconds, and the slow part, the call itself, runs from the carrier’s gateway rather than from your phone.

Does the time depend on the country I fax to?

Only in the setup phase. International call routing can add several seconds of dialling and ringing, and a poor route adds retrains. The page time itself is set by the two machines and the modem rate they agree on, not by distance.

## Related on this site

- [See the page as the receiving machine will print itFree tool](https://faxvio.com/tools/fax-preview/)
- [What the same fax costs, page by pageFree tool](https://faxvio.com/tools/fax-cost-calculator/)
- [Write the number the way the network dials itFree tool](https://faxvio.com/tools/fax-number-format/)
- [Make a cover sheet for the pages you are timingFree tool](https://faxvio.com/tools/fax-cover-sheet/)
- [Countries Faxvio sends to, and their dial codesReference](https://faxvio.com/destinations/)
- [What Delivered means in FaxvioHome](https://faxvio.com/)

---

HTML version: https://faxvio.com/tools/fax-transmission-time/
Structured data for this site: https://faxvio.com/api/v1/openapi.json · https://faxvio.com/llms.txt
Free to quote and reuse with a link back to the source URL above (CC BY 4.0).