Almost every email client has a To, Cc, and Bcc field. They look similar, behave differently, and the difference matters - for politeness, for clarity, and occasionally for not getting sued. This is the practical version: what each one does, when to use which, and the etiquette traps to avoid.

The short answer

To - the people you're writing to. Reply is expected from these recipients.
Cc (carbon copy) - people who should know this conversation is happening but aren't expected to act. Their addresses are visible to everyone else on the thread.
Bcc (blind carbon copy) - people who should get a copy without other recipients knowing. Their addresses are hidden from everyone except the sender.

The two-word version: Cc is "heads up", Bcc is "heads up, secretly".

Where the term "carbon copy" comes from

Before email, "Cc" meant a literal carbon-paper copy of a typed letter, mailed to a second recipient with the original addressee's knowledge. "Bcc" was the same idea, but the original recipient didn't see it on their letter. Email kept the abbreviations long after carbon paper disappeared, which is why the meaning isn't obvious from the words anymore.

When to use Cc (with examples)

Use Cc when someone has a stake in the outcome but you're not asking them to act. Three concrete situations:

Looping in a manager. "Hi [vendor], I'm following up on the invoice we discussed - Cc'ing [manager] for visibility." The vendor knows the manager is watching without being directly addressed.
Introducing two people. "Hi Alex, meet Sam who runs growth at Acme. Sam, Alex was the engineer who built the dashboard you liked. I'll step back and let you take it from here." You're Cc'd on the response chain but you don't need to reply.
Closing a thread with a status update."Confirming we shipped this. Cc-ing the original requesters for the record."

When to use Bcc (with examples)

Use Bcc when adding a recipient privately is the point. The most common legitimate uses:

Mass emails to people who shouldn't see each other's addresses. A newsletter to 200 people, a course announcement, an event invite to a group who aren't in a contact relationship with each other - always Bcc. Putting them in Cc leaks 200 email addresses and invites a chain of "reply-all unsubscribe" disasters.
Moving someone out of an active thread."Bcc'ing Sam now that I've looped them in - no need to keep them on future replies." A small etiquette touch: it's polite to mention in the body that you're Bcc'ing someone off, so they know.
Internal record-keeping. Some companies have a shared mailbox they Bcc on outbound sales emails so the team has a record. Just be aware your recipient can't see this.

When NOT to use Bcc

Bcc has a bad reputation because it's often misused. Avoid it in these cases:

Letting a third party silently watch a conversation.Bcc'ing your manager on a difficult message to a colleague is almost always a bad idea. If your manager needs to see it, forward the thread afterwards or Cc them openly. Silent surveillance is what makes Bcc feel sneaky.
Cc'ing yourself. You don't need to. The sent message is already in your Sent folder. The exception is if your IT setup makes that folder unreliable and you need a deliverability check - use Bcc to yourself in that case.
As a shortcut to forwarding. If you want someone to see a message after the fact, forward it. Bcc is for messages going out, not messages going back.

The reply-all trap

Cc recipients are part of the visible thread. Anyone hitting Reply All will email them too. That's usually what you want - but not when you've Cc'd a sensitive party for record-keeping and a recipient hits Reply All and forwards them into a discussion they shouldn't see.

Bcc recipients are NOT part of any thread. If they hit Reply All, their reply goes only to the original sender and any visible Cc / To. The other Bcc'd recipients won't see it. This is by design but it surprises people - so if you Bcc somebody and they reply, they've effectively moved the conversation to a one-on-one with the sender without realising.

Cc vs Bcc: side by side

Aspect	Cc	Bcc
Visible to other recipients	Yes	No
Gets the reply if someone hits "Reply All"	Yes	No
Used for "heads up, watch this"	✓	Awkward
Used for mass mailings to a list	No (leaks addresses)	✓
Common etiquette gripe	Cc-overload (everyone on every thread)	Silent surveillance

What "FYI" means in email context

FYI is shorthand for "for your information" - a signal that you're forwarding something for awareness, no action required. It pairs naturally with Cc ("FYI - Cc'ing you on this thread") and is the soft version of "you need to know about this but I'm not asking you to do anything".

The etiquette rules that actually matter

Don't Cc people who don't need to be there.Cc bloat is the most common email complaint in surveys of knowledge workers. Every Cc multiplies the number of reply chains. Be ruthless about removing people once they've been informed.
If you Bcc someone, mention it. In the body, say something like "moving X to Bcc, no need to follow replies." This avoids the surveillance feeling and signals to the recipient that you used Bcc legitimately.
Never Bcc your manager on a charged message.If a thread is going sideways and you want backup, talk to your manager directly or forward the relevant emails after the fact. Bcc'ing them while the conversation is live makes you the bad actor if it ever comes out.
For mailing lists, Bcc is the minimum bar.For anything larger than 20 people, use a proper mailing tool. Bcc works for one-off broadcasts but doesn't handle unsubscribes, deliverability, or List-Unsubscribe headers - which means it'll start hitting spam folders quickly.

How AI assistants handle Cc and Bcc

Modern email assistants treat Cc differently from To when deciding what needs your attention. A message where you're only on Cc is rarely something you need to answer - the To recipient is usually responsible. Inboxer's AI triage uses your position on the recipient line as one signal in deciding whether a thread is actionable for you specifically, which is why Cc-bombing inboxes still gets surfaced as "FYI" rather than "To Respond". It's a small thing but it removes a lot of low-grade decision fatigue.

The two-second rule for picking the right field

Before sending, ask:

Do they need to reply? → To
Should they see this is happening but not be on the hook? → Cc
Should they get a copy without anyone knowing? → Bcc

That covers 95% of cases. The other 5% is judgement, and getting it wrong on Bcc is almost always worse than getting it wrong on Cc - so when in doubt, err on the side of Cc and explain in the body.