Sending a Fax to Africa in 2026: The Practical Guide

Short answer: sending a fax to Africa in 2026 works perfectly well — provided you accept that the first-attempt delivery rate will be lower there than in Western Europe. The three causes of failure are almost always the same: a number entered incorrectly in international format (the national leading zero mistakenly kept), a noisy analogue line at the far end that can't handle 14,400 bit/s, and a transmission launched at the wrong time of day. The method consists of normalising the number, slimming down the document, forcing a low modem speed and retrying during an off-peak window. In that order.

Document flows between France and the African continent are substantial: consular files, notarial deeds, medical record transfers, customs clearance papers, letters of credit, bank confirmations, marine insurance contracts. And in a good share of these circuits, the fax isn't a relic: it's the channel officially listed on the form. A government office in Abidjan, a bank in Douala, a law firm in Casablanca, a mining authority in Kinshasa — many still publish a fax number next to a generic email address that, for its part, never replies.

So the question isn't whether you should fax. It's how to get the fax through without losing three hours and twelve attempts to it.

Why Africa is a fax destination unlike any other

Highly uneven infrastructure

Talking about "Africa" as a single destination makes no technical sense at all. Between a landline in Rabat connected to a modern IP exchange and a bush line in Central Africa routed over a radio loop, the quality gap is the one that separated France in 1985 from France in 2005.

Three families emerge in practice:

This ranking isn't a judgement: it follows from a fact documented by the International Telecommunication Union (ITU) and by the GSMA in its Mobile Economy Sub-Saharan Africa reports — across much of the continent, telephony was built directly on mobile, skipping the stage of mass wireline deployment. Where there is almost no analogue line, fax exists mainly through gateways and "logical" fixed numbers routed over VoIP. And fax does not naturally get along with VoIP.

Mobile is not a fax carrier

A very concrete consequence: an African fax number starting with a mobile prefix is almost always a typing error in the source document. The fax protocol (T.30) assumes a stable narrowband channel; mobile networks apply compressed codecs (AMR in particular) that destroy the modulation tones. If the number you've been given is a mobile, don't push: call the recipient back and ask for their fixed-line fax number, or their email address.

Dialling the number correctly: the leading cause of failure

It's mundane, and yet it accounts for half the failures reported to us.

The rule is universal and admits no exceptions: country code, then the national number stripped of its leading zero.

• Morocco: +212 — a local number 0522 XX XX XX becomes +212 522 XX XX XX
• Algeria: +213
• Tunisia: +216 (no national zero to remove, 8-digit numbering)
• Senegal: +221 (no leading zero either)
• Côte d'Ivoire: +225 — numbering has moved to 10 digits, check that your contact has given you the current format
• Cameroon: +237
• DRC: +243
• Egypt: +20
• South Africa: +27

Two pitfalls come up again and again. The first: numbers published on old documents. Several countries on the continent have reformed their numbering plans over the past decade by adding one or two digits. A number printed on a 2014 form may be structurally obsolete. The second: local notation such as "00 221 …" copied as-is. The 00 is a French international dialling prefix; an online fax service expects a canonical + format. Combining both produces an immediate error tone.

If you regularly send to several countries, our supported countries page summarises the destinations available and the expected formats. When in doubt about an unusual destination, it's better to test with a cover page alone before committing a forty-page file.

Preparing a document that gets through on a fragile line

On a good-quality line, a fax negotiates at 14,400 bit/s and swallows a page in twenty seconds. On a noisy link, negotiation drops back to 9,600, then 7,200, even 4,800 bit/s. At that rate, a dense page can take two minutes — and every extra minute increases the likelihood of a drop mid-transmission.

Hence a golden rule: the more fragile the destination, the lighter the document must be.

Scan cleanly, not heavily

A fax's weight doesn't depend on the PDF's file size but on the amount of virtual ink: a greyscale scan of a murky photocopy produces a fax riddled with stray black pixels, and therefore a far larger data volume than a clean black-and-white document.

In practice:

• scan in black and white (bitonal), 200 dpi, never in colour;
• favour a crisp original; a photocopy of a photocopy is the enemy of fax;
• avoid page backgrounds, screen tints, solid logos and heavy stamps;
• if the document came from a phone, straighten and crop it before exporting.

For bulky, recurring files, a document scanner with an automatic feeder is a game changer: it outputs clean bitonal, at the right resolution, without going through a camera. And for stiff items, passports or bound deeds that a feeder refuses, a simple neutral-light desk lamp placed beside the work surface is enough to eliminate the shadows that, on a smartphone scan, turn into black bands that are unreadable on arrival.

Split large transmissions

A 60-page file sent to Kinshasa in a single session is an invitation to failure: if the line drops at page 47, everything is lost and the recipient has received 46 orphaned pages. Split it into batches of 10 to 15 pages, number them explicitly on the cover page ("batch 2/5 — pages 16 to 30"), and leave thirty seconds between transmissions so the remote fax machine can free up its memory.

Timing, time zones and congestion: the most underestimated factor

International lines to Africa have very pronounced traffic peaks. Sending a fax to Dakar at 11 a.m. Paris time means hitting mid-morning locally on a trunk shared with all business voice traffic.

A few time-zone benchmarks (French winter time, UTC+1):

Three additional precautions:

1. Avoid Monday morning and Friday afternoon, congested everywhere.
2. Factor in the local weekend: in several North African and Gulf of Guinea countries, Friday afternoon is very quiet on the administrative side — good for the line, bad for getting the document read.
3. Anticipate movable religious holidays (Ramadan, Eid, Orthodox Christian feasts in Ethiopia): a fax machine out of paper on Friday evening stays out of paper until Monday.

If your file has a deadline — a filing cut-off, a tender closing date — apply the same discipline as for any time-constrained transmission: send the day before, not on the day itself. Our recommendations on proof of sending and the delivery receipt apply fully here, and even more so: to a destination with a moderate delivery rate, the transmission report is your only defence.

Setting the speed and retrying intelligently

Most serious online fax services expose, in their advanced options, a maximum modem speed setting (or "fax rate") and a number of attempts.

The strategy that works:

• First attempt: default settings, 14,400 bit/s.
• Second attempt (if it fails): force 9,600 bit/s, and disable ECM (Error Correction Mode) if the option exists. ECM is excellent on a clean line, but on a very noisy one it causes retransmission loops until timeout.
• Third attempt: 4,800 bit/s, document split, different time slot.
• Beyond that: the problem is no longer the line. Call the number by voice: you'll hear either a fax tone (the machine exists), or a voice (wrong number), or nothing at all (machine unplugged).

That last manual test is the most rewarding of all. It costs one minute and saves half a day of stubbornness. A small USB headset sitting beside the workstation makes the exercise less painful when you have to listen to eight tones in a row.

A repeated fax failure with the code "no answer" means, nine times out of ten, that the remote fax machine is switched off. A "training failed" or "line error" failure, on the other hand, points to a genuine line-quality problem — and only in that second case does lowering the speed make sense.

Fax, VoIP and T.38: what's different on the African side

In France, the issue is well known: the shutdown of the legacy PSTN pushed everyone towards VoIP, with the fax transport difficulties that Arcep had identified from the earliest phases of migration. On the African side, the same shift is under way, often faster, because operators have deployed IP network cores without going through decades of electromechanical switching.

The paradoxical result: a fax can fail not because the remote line is too old, but because it is too new and badly configured — a gateway that doesn't negotiate T.38 properly, a compressed voice codec imposed on one leg, a jitter buffer that's too short. On this terrain, the symptoms and the remedies are exactly those described in our dedicated article on fax over VoIP and T.38 failures.

One practical consequence: if your African recipient tells you "our fax is on the internet now", simply ask whether they can give you a receiving email address. Many organisations have migrated to a fax-to-email service without updating their public documents. You'll save yourself everything else.

Receiving from Africa: the other half of the flow

The return direction is often overlooked. A contact in Ouagadougou or Antananarivo who needs to send you back a signed document generally has no alternative: they go to the local internet café, which has a fax machine, and send to your number.

For this to work:

• give your number in full international format (+33 …), never in national format;
• state it both in separated digits and in words on the cover page — a handwritten 1 reads as 7 across half the French-speaking world;
• use a fax-to-email receiving number rather than a physical fax machine: it never runs out of paper, and it time-stamps. The receive a fax page explains how it works;
• send a message warning that the fax is coming, so you can follow up if nothing arrives within two hours.

For teams handling these flows daily, two accessories make a real difference: a compact UPS for the workstation and the router — micro power cuts are the number one enemy of a transmission in progress — and, on the filing side, expanding file folders to keep the signed originals you may have to produce again years later.

Frequently asked questions

Can I send a fax to an African mobile number?

No, not reliably. Mobile networks compress voice and destroy the fax protocol's tones. Some operators offer "fax SMS" or notification services, but that isn't a fax in the legal sense. Ask for a landline number.

Why does my fax get through to Casablanca but fail to Kinshasa?

Because the two destinations have nothing technically in common. Morocco has a dense, largely migrated fixed network; in the Democratic Republic of the Congo, most fixed numbers run through IP or radio gateways, with highly variable channel quality. Lower the speed, lighten the document, change the time slot.

Does a fax carry the same legal weight in French-speaking Africa as in France?

National laws differ, but most French-speaking African countries have rules of evidence inspired by French civil law, under which a fax constitutes prima facie evidence supported by the transmission report, without amounting to a signed original. For an authenticated instrument, it's the paper original or a qualified electronic signature that counts. Always keep the transmission report and the PDF you sent.

Does faxing to Africa cost more?

Routing rates to certain African destinations are indeed higher than to the European Union, because call termination costs more there. Above all, the actual bill depends on the number of minutes consumed: a page that takes two minutes to get through costs as much as six pages to Germany. Slimming down the document is therefore also a cost-saving move.

How many attempts before giving up?

Four, spread over two distinct time slots and two separate days. Beyond that, the problem is at the recipient's end: wrong number, unplugged machine, discontinued service. Switch to the phone or email. Our answers to specific cases are gathered in the FAQ.

Key takeaways

• Normalise the number: +country code then the national number without its leading zero. This is failure cause no. 1.
• Check the number's age: several African numbering plans have changed over the past ten years.
• Never to a mobile: the fax protocol does not survive mobile codecs.
• Lighten up: black and white, 200 dpi, crisp original, no screen tints or solid logos.
• Split files into batches of 10 to 15 pages, numbered on the cover page.
• Target off-peak windows: early morning or late afternoon Paris time, factoring in the time difference and the local weekend.
• Step the speed down progressively (14,400 → 9,600 → 4,800) and switch off ECM on a noisy line.
• Test by voice after two failures: you'll know in a minute whether the fax machine still exists.
• Keep the transmission report: for these destinations, it's your only proof.