CC adds someone to an email so that every recipient can see they were added. BCC adds someone that no other recipient can see, including the other people on the BCC line.
That is the whole difference. Almost every problem with CC and BCC comes from the second half of the BCC rule, which people forget: the hidden recipients are hidden from each other too.
What CC means
CC stands for carbon copy, from the days of typing a letter twice with a sheet of carbon paper between the pages. It survived into email because the idea is still useful: a copy of a message, sent to someone who is not the main recipient.
Everyone on the message sees the CC line. The convention is that a CC is for information, not for action. If you need someone to do something, put them on the To line or ask them directly.
| Field | Who sees it | Expected to act | Usual purpose |
|---|---|---|---|
| To | Everyone | Yes | The people the message is for |
| CC | Everyone | No | Keeping someone in the loop |
| BCC | Only the sender | No | Hiding a recipient from the others |
What BCC means
BCC stands for blind carbon copy. The recipients on this line are not shown to anyone else on the message.
The part that catches people out is that a BCC recipient cannot see the other BCC recipients either. If you blind copy five people, each of them sees a message addressed to the To and CC lines, and nothing else.
People use BCC for three things:
- Privacy on a group message. Sending an announcement to a list of customers without publishing the list.
- Introductions. Copying a colleague on an email to a contact without giving the colleague’s address to the contact yet.
- A quiet record. Adding a manager or an archive address without signalling it to the recipient.
None of those are secret from your own organisation in most mail systems. A BCC leaves a copy in the sender’s Sent folder, and the address is visible to anyone who can read that mailbox.
What actually happens when you send it
BCC is not a security mechanism. It is a header field that the sending system removes before delivery.
RFC 5322, which defines the format of an internet message, spells out three ways a mail system can handle the field, and says which one is used is up to the implementation:
- The BCC line is removed for everyone, including the people on it.
- The To and CC recipients get a copy with the BCC line removed, while the BCC recipients get a separate copy that still carries it.
- A BCC field containing no addresses is sent, which tells recipients that blind copies went to somebody.
Two consequences follow. Your own copy may show the BCC line while the recipients’ copies do not. And you cannot tell from the message you receive whether a BCC line existed, unless the sender left an empty one to hint at it.
When BCC backfires
The failure mode is reply all.
The RFC is explicit that if the original message had a BCC field, those addresses may appear in the BCC field of the reply but should not appear in the To or CC fields. It then adds that how a mail application builds a reply is up to the implementation and outside the scope of the standard.
In practice that means a BCC recipient hitting reply all can put the whole hidden list in front of everyone. It does not happen every time, which is what makes it dangerous: it happens often enough that “BCC plus reply all” is a recognisable way to leak an email list.
If the list matters, do not rely on BCC. Send from a system that sends each person their own copy.
CC and BCC on a shared address
Most guides assume one person with one mailbox. Support and sales addresses break that.
CC the shared address. Do not BCC it. When support@ is CC’d, everyone with access to the inbox can see the
message, find it later, and pick up the thread if the first person is away. When support@ is BCC’d, the message
lands in the mailbox with no visible reason, so the team cannot tell whether they are the primary owner or a silent
observer, and the customer cannot tell that anyone is watching.
Decide who answers. A CC creates the same ambiguity on every team: nobody knows whether the CC’d group is expected to reply. Pick a rule and write it down. A common one is that the To line owns the reply, and a CC is watching only.
Reply all has a team meaning. On a shared address, reply all can add four colleagues to a thread that the customer only wanted one of them on. Some teams set the reply behaviour per inbox so the default matches the rule.
Chirp gives each inbox its own address, signature and access list, and it shows which inbox a thread belongs to in the list. That makes it obvious whether a message arrived as the primary recipient or as a CC.
Deciding who goes on which line
Work down this list and stop at the first match:
- The person must act on the message: To.
- The person needs to know, and nothing more: CC.
- The person needs to know, and nobody else should: BCC.
- You are introducing two people: CC both, and say in the body who each of them is.
The mistake to avoid is putting a group on the To line. Five people on To means five people think they own the reply.
When a CC thread gets out of hand
A message goes to three people. Two of them reply all. Now it reaches nine, and the ninth replies all. This is the CC pile-up, and it happens because replying all is the default in most mail clients.
Three ways out:
- Reply to the sender alone when the message was information rather than work.
- When fewer people need to see it, start a new message with a clear subject instead of continuing the thread.
- If one person needs to decide, send it to them and tell the others you have done so.
FAQ
What does CC stand for? Carbon copy. BCC is blind carbon copy.
Do BCC recipients see each other? No. Each BCC recipient sees only their own copy, and the other BCC addresses are hidden from them as well.
Is it rude to BCC someone? Not by itself. It becomes a problem when the hidden person can influence the conversation without the visible recipients knowing, or when a reply all exposes the list.
Should I use CC or BCC for a mailing list? Neither, for anything important. Use a system that sends each person an individual copy. BCC hides the addresses until someone replies all.
Can I tell if I was BCC’d? Usually not from the message itself. You can often tell from the context: a message addressed to someone else, with no acknowledgement that you were expected.
Next step
If your team answers one address, the same rules apply to every reply, and the sign-off needs a decision too. How to end an email covers the closing half. See how Chirp handles inboxes covers the rest.
