BCC stands for blind carbon copy. Anyone you put in the BCC field receives the email, but nobody else on the message can see that they got it. The To and CC recipients see each other, and the BCC list stays visible to you alone. Our companion guide to sending one message to a whole list without exposing addresses covers the recipient caps that apply once the list gets long.

That one sentence covers about 80% of what people need. The rest of this guide covers the parts that bite you, and I’ve watched every one of them bite someone.

It helps to picture a mail room clerk sitting between you and your recipients. You hand over one envelope with three lists taped to it. BCC judgment is one slice of a bigger set; our email etiquette rules cover the rest.

The clerk copies the To list and the CC list onto every outgoing copy. Then the clerk peels the BCC list off and throws it away, before a single message leaves the building.

Wait, the clerk throws it away? Yep. That’s the real mechanism, and it explains nearly every strange thing BCC does.

What Does BCC Mean in Email?

BCC means blind carbon copy, a term inherited from carbon paper and typewriters. RFC 5322 is the standard that defines email message format. RFC 5322 defines the BCC field as holding addresses “not to be revealed to other recipients of the message.”

The standard also spells out what the mail room clerk does with that list. RFC 5322 section 3.6.3 gives mail systems three permitted options for handling BCC at send time.

• Strip the BCC line from every copy, so all recipients get the message and nobody sees the BCC list.
• Strip it from the To and CC copies, but leave a BCC line on the copies sent to BCC recipients.
• Send an empty BCC line to signal that blind copies went out, without naming anyone.

RFC 5322 closes the section with a line worth remembering: “Which method to use with ‘Bcc:’ fields is implementation dependent.” Your provider picks. You don’t.

Key Insight

BCC is a delivery instruction, not a security feature. The standard permits mail systems to handle the field three different ways. The RFC’s own security section warns that a blind recipient can reveal themselves by replying.

What Is the Difference Between BCC and CC in Email?

CC recipients are visible to everyone on the message, and BCC recipients are hidden from everyone but the sender. Both fields deliver an identical copy of the email.

Think of the CC line as the peanut gallery with the lights on. Every name is legible to every other name. Any one of them can hit reply all and comment in front of the whole room.

Behavior	CC	BCC
Recipients see this list	Yes, everyone sees the full CC list	No, only the sender sees it
Recipient knows how they were added	Yes, they see their own name in CC	Yes in Gmail, per Google’s documentation
Can see other hidden recipients	Not applicable	No, BCC recipients can’t see each other
Receives replies sent to reply all	Yes	No, Google confirms BCC recipients don’t see reply-all responses
Counts toward the per-message recipient cap	Yes	Yes
Common use	Keeping a colleague informed on the record	Hiding a distribution list from itself

Google’s own Gmail documentation states the visibility rules plainly. “Anyone you add to the ‘Bcc’ field will see that they were added using ‘Bcc.’ They will also see message recipients in the ‘To’ and ‘Cc’ fields.”

Google also confirms that BCC recipients can’t see each other’s names or addresses.

I wrote a separate guide on using CC in email covering the visible half of this pair.

Google flags one caveat itself, and it matters more than people expect. If your recipients don’t use Gmail, they may not see that they were added to the BCC field. The clerk’s habits change from building to building.

How Do You Access the BCC Field in Gmail and Outlook?

In Gmail, the BCC field sits in the compose window alongside To and CC. Google’s support documentation confirms you can click the “To,” “Cc,” or “Bcc” labels to add recipients or manage your contact labels.

In the new Outlook for Windows, BCC is hidden until you turn it on. Microsoft’s official instructions are three steps.

1. Open a new message or reply to a message in new Outlook.
2. Go to Options, then Show fields, then select Show Bcc.
3. Add the names of the people you want on the BCC line.

Once you switch it on, Microsoft says the BCC field stays visible for every new message until you turn it off. Sweet. That’s one less setting to hunt for at 8am.

If you use both Outlook and Gmail, expect the field to behave the same way in both. The hiding happens at the mail server rather than in the interface you’re looking at.

How Many People Can You BCC in One Email?

A free Gmail account caps you at 500 recipients per message and 500 emails per day. Google’s sending limits page puts the trigger at “more than 500 recipients in a single email” or more than 500 emails per day.

Google Workspace raises that ceiling, with a catch that trips up B2B senders constantly. The limit is 2,000 recipients per message across To, CC, and BCC, but no more than 500 of them can be external to your organization.

Account type	Recipients per message	Daily cap
Free Gmail	500 across To, CC, and BCC	500 emails per day
Google Workspace	2,000, of which 500 may be external	2,000 messages, 10,000 total recipients
Exchange Online	Up to 1,000, set by your administrator	10,000 recipients per day

Microsoft’s published limits set the Exchange Online recipient limit at up to 1,000. Microsoft calls it “the maximum number of recipients allowed in the To:, Cc:, and Bcc: fields for a single email message.” Administrators can set it anywhere between 1 and 1,000 per mailbox, and the message rate is 30 per minute.

Both companies caveat their own numbers. Google states that sending limits can change without notice, and that daily limits apply over a rolling 24-hour period rather than a fixed clock. These figures were verified on 28 July 2026.

Pro Tip

Distribution groups in your organization’s shared address book count as one recipient against these caps. Members of a personal distribution list count individually, so a 400-person personal list eats most of a free Gmail send.

When Should You Use BCC Instead of To or CC?

Use BCC when the recipients have no relationship to each other and no reason to see each other’s addresses. That’s the whole rule, and three situations cover most legitimate uses.

Announcements to a list of people who don’t know each other. A notice to 40 external contacts about an office move belongs in BCC. Publishing 40 email addresses to 40 strangers is a privacy problem you created for no reason.

Removing yourself from a thread. Reply, move the original CC list to BCC, and add a line saying you’ve moved everyone to BCC. They get the closing message, and their reply-all doesn’t restart the thread for the whole group.

Introductions, once the introduction is done. When you want to introduce new people and then step back, move yourself to BCC on the handoff message. That’s the polite exit.

Notice what these have in common. In each case the hidden recipient isn’t being hidden from a conversation they’re part of. That distinction does most of the ethical work.

When Is It Inappropriate to Use BCC in Email?

BCC turns ugly the moment you use it to hide a person from a conversation they’re a party to. The classic version is BCC’ing a manager on a complaint to a colleague.

Ouch. And it gets worse. The person you hid can hit reply all by reflex and expose the whole arrangement in one click.

The RFC anticipated this. Its security section warns that a blind recipient who replies could “accidentally reveal that the message went to the blind recipient.”

The clerk removed the evidence on the way out, and your BCC’d manager just mailed it back in.

Three uses to avoid outright:

• BCC’ing someone’s supervisor to build a case without telling them.
• BCC’ing yourself at a personal address to remove records from a work account.
• Using BCC to circumvent a disclosure or retention obligation, which in regulated industries is a compliance problem rather than a manners problem.

Getting caught doing any of these reads as unprofessional at best. It also destroys the thing that made your email useful, which is that people believed what it said about who was reading.

There’s a second cost too. Work in hidden copies doesn’t show up in any shared view of team workload. Managers lose sight of who’s carrying which conversations.

Our own product exists to make that visible, and the way EmailAnalytics reads team email activity depends on messages being addressed openly. Across the 10,000+ teams using it, the average response time improvement is 42.5%.

Does Using BCC Send Your Email to Spam?

Microsoft says yes, and says it in its own documentation. Google says nothing at all.

Microsoft’s support page on the BCC field is blunt: “Using Bcc is a favorite technique of spammers.” It adds that “many junk email filters flag messages that use the Bcc box as junk.” Unless you’re on the recipient’s Safe Senders List, Microsoft warns the message may land in Junk.

Google publishes no equivalent claim. I checked its sender guidelines, its bulk email best practices page, and its Gmail spam and abuse policy. None of them mention BCC.

Treat “BCC hurts deliverability” as a Microsoft position rather than an industry law.

What both companies do agree on is the alternative. Microsoft states that “Exchange Online isn’t suited to accommodate bulk-mailing scenarios” and directs bulk senders to third-party providers. Google’s bulk email guidance steers users toward mail merge.

What Is a Safer Alternative to Using BCC?

Send separate messages instead of one hidden pile. Mail merge does this natively in both Gmail and Outlook, giving each recipient a message addressed to them alone.

For anything that resembles a newsletter, use an email marketing platform. Those systems handle unsubscribes, authentication, and bounce processing. Google now requires all three from bulk senders at 5,000 messages per day and above.

Mail merge in Google Workspace carries a lower daily cap than regular sending, at 1,500 messages, so plan around it if your list is large.

Start Here: Four Steps Before Your Next BCC

1. Ask whether the hidden person is a party to this conversation. If they are, don’t BCC them.
2. Count your recipients against your account’s cap: 500 for free Gmail, 2,000 for Workspace with 500 external, up to 1,000 for Exchange Online.
3. If the message is an announcement to more than about 50 strangers, switch to mail merge before you send it.
4. Turn the BCC field on permanently in new Outlook through Options, Show fields, Show Bcc. You’ll stop pasting addresses into the wrong box.

Do not skip the first step. Every BCC disaster I’ve seen started with someone answering it too fast.

Frequently Asked Questions About BCC in Email

What does BCC mean in email?

BCC stands for blind carbon copy. Addresses in the BCC field receive the message, but the other recipients can’t see them. RFC 5322 defines BCC as holding addresses of recipients whose addresses are not to be revealed to other recipients of the message.

What is the difference between CC and BCC?

CC recipients are visible to everyone on the message, and BCC recipients are hidden. Everyone in the To and CC fields can see the full CC list. Nobody except the sender can see who was BCC’d.

Can BCC recipients see each other?

No. Google’s documentation states that people you add in BCC can’t see the name or email address of anyone else you add in the BCC field. Each BCC recipient sees only the To and CC lists, plus their own address.

How many people can you BCC in one email?

A free Gmail account allows 500 recipients per message across To, CC, and BCC combined. Google Workspace allows 2,000 recipients per message, of which a maximum of 500 can be external. Exchange Online sets the limit at 1,000, adjustable by an administrator.

What happens if a BCC recipient hits Reply All?

Their reply exposes that they received the message, because their address appears in the reply. Google documents the reverse case as well: when other recipients reply all, people in BCC won’t see the reply.

Does using BCC send an email to spam?

Microsoft states that many junk email filters flag messages that use the BCC box as junk, because BCC is a favorite technique of spammers. Google publishes no equivalent warning about BCC.

What is a safer alternative to using BCC?

Send individual messages through a mail merge, or use a dedicated email marketing platform for anything resembling a newsletter. Both Google and Microsoft point bulk senders toward mail merge and third-party sending services rather than the BCC field.