# How long does this document take on a fax line?

> Pick a PDF or TIFF to see its fax transmission time: the seconds its page data takes at the modem rate you pick. Coded in your browser, never uploaded.

Page: https://faxforagents.com/tools/fax-time/
Last changed: 2026-11-19

Updated Nov 19, 2026

Pick a PDF or TIFF to see its fax transmission time, how long its pages take on a fax line. This page codes each page the way a Group 3 fax machine does, then works out the seconds at the modem rate you pick. Your browser does the work, and the file is never uploaded.

The figure is the page data alone. The call set-up, the modem training, the confirmation after each page, retries and a busy line all add time. Our measured times show how much on our own faxes.

## How long did our own faxes take?

Measured on our own live faxes between 2026-11-09 and 2026-11-13

| Pages | From the send to the final report | The call itself |
| --- | --- | --- |
| 1 page | 29 to 34 seconds | 25 seconds |
| 2 pages | 35 to 59 seconds | 31 seconds |
| 8 pages | 327 seconds | 313 seconds |

We measured these times on our own live faxes between 2026-11-09 and 2026-11-13, from the send to the carrier's final report. They are a measurement, never a promise. The same figures are in [facts.json](https://faxforagents.com/facts.json), and our post on [how long a fax takes](https://faxforagents.com/blog/how-long-does-a-fax-take/) explains them.

## What does the figure cover?

The figure is the page data of a call, as T.4 defines it, at the rate and minimum scan line time you pick. For each page it adds up these parts.

- The code words of every scan line.
- The end of line code, or EOL, after each line and once before the first.
- Fill, the zeros that make a short line last the minimum scan line time.
- The 6 EOLs that end the page.

The total coded scan line is defined as the sum of data bits plus any required fill bits plus the end-of-line (EOL) bits. [ITU-T T.4, clause 3](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

A real call takes longer. Before the pages, the machines answer, state what they can do, agree on the rate and train the modems. After each page the receiver confirms it, and a page can be sent again. All of that is in the procedure of T.30, and none of it is in this figure. Compare it with the calls in our table above: the gap is the rest of the call.

## How is a page coded?

Each page is laid on the scan line at its own size and centred. A page wider than the line is scaled down to fit it. The line has 1728 picture elements, or pels, along 215 mm.

A total of 1728 picture elements represent one horizontal scan line of 215 mm length. [ITU-T T.4, clause 4.1.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

Down the page, standard resolution has 3.85 scan lines per millimetre and fine has 7.7. These are the two resolutions [our fax TIFF page](https://faxforagents.com/tools/fax-tiff/) sets files against.

a) a standard resolution of 3.85 lines/mm ± 1% in vertical resolution; [ITU-T T.4, clause 2.1 a)](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

b) optional higher resolution of 7.7 lines/mm ± 1% and 15.4 lines/mm ± 1% in vertical direction; [ITU-T T.4, clause 2.1 b)](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

Each pel is the average of the pixels it covers, and a pel darker than mid-grey is black. A TIFF whose pixels already match the pels and lines to within 1% is coded pixel for pixel.

A fax TIFF is 1728 pels wide at 200 or 204 per inch. Its rows are coded one for one as standard lines at 98 or 100 lines per inch, and as fine lines at 196 or 200. [Our fax TIFF page](https://faxforagents.com/tools/fax-tiff/) quotes the profile of RFC 3949 that treats those values as equal.

In pixels/inch, the allowed values are 200 and 204, which may be treated as equivalent. [RFC 3949, section 3.2.1](https://www.rfc-editor.org/rfc/rfc3949.html)

In pixels/inch, the allowed values are 98, 100, 196, and 200; 98 and 100 may be treated as equivalent, and 196 and 200 may be treated as equivalent. [RFC 3949, section 3.2.1](https://www.rfc-editor.org/rfc/rfc3949.html)

Each line is then coded with the one-dimensional scheme of T.4, called Modified Huffman. A line is a row of runs, white and black in turn, and each run has its code word.

In order to ensure that the receiver maintains colour synchronization, all data lines will begin with a white run length code word. [ITU-T T.4, clause 4.1.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

If the actual scan line begins with a black run, a white run length of zero will be sent. [ITU-T T.4, clause 4.1.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

Run lengths in the range of 0 to 63 pels are encoded with their appropriate terminating code word. [ITU-T T.4, clause 4.1.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

Run lengths in the range of 64 to 1728 pels are encoded first by the make-up code word representing the run length which is equal to or shorter than that required. [ITU-T T.4, clause 4.1.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

This is then followed by the terminating code word representing the difference between the required run length and the run length represented by the make-up code. [ITU-T T.4, clause 4.1.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

This code word follows each line of data. [ITU-T T.4, clause 4.1.2](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

In addition, this signal will occur prior to the first data line of a page. [ITU-T T.4, clause 4.1.2](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

Fill must be added to ensure that the transmission time of Data, Fill and EOL is not less than the minimum transmission time of the total coded scan line established in the pre-message control procedure. [ITU-T T.4, clause 4.1.3](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

The end of a document transmission is indicated by sending six consecutive EOLs. [ITU-T T.4, clause 4.1.4](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

So a blank line is one white run of 1728 pels: a make-up code word, a terminating code word of zero and the EOL. A line of dense text has many short runs, and many more bits. In Figure 2 of T.4, the EOL of the last line is the first of the 6 that end the page.

## Which modem rates and scan line times can you pick?

The rates are the ones the DCS frame of T.30 can set. In that frame the sending machine picks the rate for the call. The 33 600 bit/s rate is the top of the V.34 title.

The modem rates this page offers and where each one is written

| Rate | Modem | Source |
| --- | --- | --- |
| 2400 bit/s | [V.27ter](https://faxforagents.com/glossary/#standard-v-27ter) | 2400 bit/s, ITU-T Rec. V.27 ter [T.30, Table 2, bits 11 to 14, DCS](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items) |
| 4800 bit/s | [V.27ter](https://faxforagents.com/glossary/#standard-v-27ter) | 4800 bit/s, ITU-T Rec. V.27 ter [T.30, Table 2, bits 11 to 14, DCS](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items) |
| 7200 bit/s | [V.29](https://faxforagents.com/glossary/#standard-v-29) or [V.17](https://faxforagents.com/glossary/#standard-v-17) | 7200 bit/s, ITU-T Rec. V.29 7200 bit/s, ITU-T Rec. V.17 [T.30, Table 2, bits 11 to 14, DCS](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items) |
| 9600 bit/s | [V.29](https://faxforagents.com/glossary/#standard-v-29) or [V.17](https://faxforagents.com/glossary/#standard-v-17) | 9600 bit/s, ITU-T Rec. V.29 9600 bit/s, ITU-T Rec. V.17 [T.30, Table 2, bits 11 to 14, DCS](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items) |
| 12 000 bit/s | [V.17](https://faxforagents.com/glossary/#standard-v-17) | 12 000 bit/s, ITU-T Rec. V.17 [T.30, Table 2, bits 11 to 14, DCS](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items) |
| 14 400 bit/s | [V.17](https://faxforagents.com/glossary/#standard-v-17) | 14 400 bit/s, ITU-T Rec. V.17 [T.30, Table 2, bits 11 to 14, DCS](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items) |
| 33 600 bit/s | [V.34](https://faxforagents.com/glossary/#standard-v-34) | The title of V.34, in our [fax standards table](https://faxforagents.com/glossary/#standard-v-34) |

The machines agree on a rate at the start of the call, and a call can step down to a slower one. This page uses the rate you pick for every page.

The minimum scan line time is the least time one coded line takes, so that the receiving machine can print it. A line with fewer bits than that gets fill. T.4 offers these times, and the calling machines agree on one before the pages.

a) 20 milliseconds recommended standard; [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

b) 10 milliseconds recognized option with a mandatory fall-back to the 20 milliseconds standard; [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

c) 5 milliseconds recognized option with a mandatory fall-back to the 10 milliseconds option and the 20 milliseconds standard; [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

d) 0 millisecond recognized option with a mandatory fall-back to the 5 milliseconds option, the 10 milliseconds option and the 20 milliseconds standard, and an optional fall-back to the 40 milliseconds option; [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

e) 40 milliseconds recognized option. [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

The identification and choice of this minimum transmission time is to be made in the pre-message (phase B) portion of T.30 control procedure. [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

T.4 names 20 ms as the standard, so the page starts there. T.4 also has an option where fine resolution takes half the time of standard. This page applies one time to both, the first alternative.

1) Alternative 1, where the minimum transmission time of the total coded scan line is the same both for the standard resolution and for the optional higher resolution: [ITU-T T.4, clause 3.1](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

At 33 600 bit/s the page sets the time to 0 ms, because V.34 always runs in error correction mode. That mode also sends the data in frames, which the figure leaves out.

The use of the Error Correction Mode (ECM) is mandatory for all facsimile messages using the V.34 modulation system. [ITU-T T.30, clause F.3](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items)

The optional T.4 error correction mode of operation and IAFD mode require 0 ms of the minimum scan line time capability. [ITU-T T.30, Table 2, note 8](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.30-200509-I!!PDF-E&type=items)

For the optional error correction mode, an HDLC frame structure is utilized to transmit the total coded scan line. [ITU-T T.4, clause 3.3](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items)

## How large is a page before it is coded?

Without a file, here is the size of a blank page before any coding, one bit per pel. It is a reference for scale, not a time. How much coding saves depends on what is on the page.

Scan lines and uncoded bits of a blank page, at 1728 pels a line

| Paper | Standard | Fine |
| --- | --- | --- |
| US Letter | 1,071 lines, 1,850,688 bits | 2,142 lines, 3,701,376 bits |
| A4 | 1,143 lines, 1,975,104 bits | 2,287 lines, 3,951,936 bits |

## What does this page leave out?

- The rest of the call. That is the answer, the exchange of what each machine can do, the training, the confirmation after each page and the hang-up.
- Retries. A page sent again, or a call made again after a busy signal, adds its whole time again.
- Two-dimensional coding. T.4 also has a scheme that codes a line against the one above it. This page codes every line on its own.
- The frames of error correction mode, and colour or grey modes.
- How another program would lay out or draw your page. Fonts a PDF does not embed are drawn with a stand-in, so their text can code to a slightly different size.

## How is the file read?

A PDF is drawn by pdf.js 6.5.438, an open source PDF reader, served from this site. A TIFF is read by our own code, the reader of [the fax TIFF page](https://faxforagents.com/tools/fax-tiff/) with a decoder for its pixels. Both load only after you pick a file, and they work in separate threads of your browser. If its drawing thread fails, pdf.js draws on the page's own thread instead.

The coder behind the figures is [faxforagents-fax-time](https://github.com/faxforagents/fax-time), our open source package under the MIT licence.

A TIFF can be black and white or 8-bit grey or colour, stored uncompressed or in a fax, LZW, PackBits or Deflate coding. A file over the [upload limit](https://faxforagents.com/docs/limits/) of 25 MiB is not read, and a document is read up to 200 pages. To check a PDF's page size and smallest text, use [the fax-ready PDF page](https://faxforagents.com/tools/fax-ready-pdf/).

A file gets 120 seconds. After that the reading stops and the results show the pages done so far. A heavy page drawn on the page's own thread can take longer. The file stays on your device. The site's analytics count the visit, as on every page, and are told to leave the results out. Reload the page and the results of a file are gone.

A link to a result keeps its numbers after the # of its address, a part a browser never sends to a server. An analytics tool that records the whole address of a page can still see them.

## Which code words does the page use?

These are Tables 2 and 3a of T.4, as clause 4.1 gives them. We copied them from [the text of T.4 (07/03), in English, as a PDF](https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.4-200307-I!!PDF-E&type=items) and read them again on 2026-11-18. The EOL is `000000000001`.

White runs, 91 code words

White run lengths and their code words, Tables 2 and 3a of T.4

| Run length | Code word |
| --- | --- |
| 0 | 00110101 |
| 1 | 000111 |
| 2 | 0111 |
| 3 | 1000 |
| 4 | 1011 |
| 5 | 1100 |
| 6 | 1110 |
| 7 | 1111 |
| 8 | 10011 |
| 9 | 10100 |
| 10 | 00111 |
| 11 | 01000 |
| 12 | 001000 |
| 13 | 000011 |
| 14 | 110100 |
| 15 | 110101 |
| 16 | 101010 |
| 17 | 101011 |
| 18 | 0100111 |
| 19 | 0001100 |
| 20 | 0001000 |
| 21 | 0010111 |
| 22 | 0000011 |
| 23 | 0000100 |
| 24 | 0101000 |
| 25 | 0101011 |
| 26 | 0010011 |
| 27 | 0100100 |
| 28 | 0011000 |
| 29 | 00000010 |
| 30 | 00000011 |
| 31 | 00011010 |
| 32 | 00011011 |
| 33 | 00010010 |
| 34 | 00010011 |
| 35 | 00010100 |
| 36 | 00010101 |
| 37 | 00010110 |
| 38 | 00010111 |
| 39 | 00101000 |
| 40 | 00101001 |
| 41 | 00101010 |
| 42 | 00101011 |
| 43 | 00101100 |
| 44 | 00101101 |
| 45 | 00000100 |
| 46 | 00000101 |
| 47 | 00001010 |
| 48 | 00001011 |
| 49 | 01010010 |
| 50 | 01010011 |
| 51 | 01010100 |
| 52 | 01010101 |
| 53 | 00100100 |
| 54 | 00100101 |
| 55 | 01011000 |
| 56 | 01011001 |
| 57 | 01011010 |
| 58 | 01011011 |
| 59 | 01001010 |
| 60 | 01001011 |
| 61 | 00110010 |
| 62 | 00110011 |
| 63 | 00110100 |
| 64 | 11011 |
| 128 | 10010 |
| 192 | 010111 |
| 256 | 0110111 |
| 320 | 00110110 |
| 384 | 00110111 |
| 448 | 01100100 |
| 512 | 01100101 |
| 576 | 01101000 |
| 640 | 01100111 |
| 704 | 011001100 |
| 768 | 011001101 |
| 832 | 011010010 |
| 896 | 011010011 |
| 960 | 011010100 |
| 1024 | 011010101 |
| 1088 | 011010110 |
| 1152 | 011010111 |
| 1216 | 011011000 |
| 1280 | 011011001 |
| 1344 | 011011010 |
| 1408 | 011011011 |
| 1472 | 010011000 |
| 1536 | 010011001 |
| 1600 | 010011010 |
| 1664 | 011000 |
| 1728 | 010011011 |

Black runs, 91 code words

Black run lengths and their code words, Tables 2 and 3a of T.4

| Run length | Code word |
| --- | --- |
| 0 | 0000110111 |
| 1 | 010 |
| 2 | 11 |
| 3 | 10 |
| 4 | 011 |
| 5 | 0011 |
| 6 | 0010 |
| 7 | 00011 |
| 8 | 000101 |
| 9 | 000100 |
| 10 | 0000100 |
| 11 | 0000101 |
| 12 | 0000111 |
| 13 | 00000100 |
| 14 | 00000111 |
| 15 | 000011000 |
| 16 | 0000010111 |
| 17 | 0000011000 |
| 18 | 0000001000 |
| 19 | 00001100111 |
| 20 | 00001101000 |
| 21 | 00001101100 |
| 22 | 00000110111 |
| 23 | 00000101000 |
| 24 | 00000010111 |
| 25 | 00000011000 |
| 26 | 000011001010 |
| 27 | 000011001011 |
| 28 | 000011001100 |
| 29 | 000011001101 |
| 30 | 000001101000 |
| 31 | 000001101001 |
| 32 | 000001101010 |
| 33 | 000001101011 |
| 34 | 000011010010 |
| 35 | 000011010011 |
| 36 | 000011010100 |
| 37 | 000011010101 |
| 38 | 000011010110 |
| 39 | 000011010111 |
| 40 | 000001101100 |
| 41 | 000001101101 |
| 42 | 000011011010 |
| 43 | 000011011011 |
| 44 | 000001010100 |
| 45 | 000001010101 |
| 46 | 000001010110 |
| 47 | 000001010111 |
| 48 | 000001100100 |
| 49 | 000001100101 |
| 50 | 000001010010 |
| 51 | 000001010011 |
| 52 | 000000100100 |
| 53 | 000000110111 |
| 54 | 000000111000 |
| 55 | 000000100111 |
| 56 | 000000101000 |
| 57 | 000001011000 |
| 58 | 000001011001 |
| 59 | 000000101011 |
| 60 | 000000101100 |
| 61 | 000001011010 |
| 62 | 000001100110 |
| 63 | 000001100111 |
| 64 | 0000001111 |
| 128 | 000011001000 |
| 192 | 000011001001 |
| 256 | 000001011011 |
| 320 | 000000110011 |
| 384 | 000000110100 |
| 448 | 000000110101 |
| 512 | 0000001101100 |
| 576 | 0000001101101 |
| 640 | 0000001001010 |
| 704 | 0000001001011 |
| 768 | 0000001001100 |
| 832 | 0000001001101 |
| 896 | 0000001110010 |
| 960 | 0000001110011 |
| 1024 | 0000001110100 |
| 1088 | 0000001110101 |
| 1152 | 0000001110110 |
| 1216 | 0000001110111 |
| 1280 | 0000001010010 |
| 1344 | 0000001010011 |
| 1408 | 0000001010100 |
| 1472 | 0000001010101 |
| 1536 | 0000001011010 |
| 1600 | 0000001011011 |
| 1664 | 0000001100100 |
| 1728 | 0000001100101 |
