How to Send Messages to Multiple Recipients Without Showing Email Addresses

Written by robin reetz
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Send Messages to Multiple Recipients Without Showing Email Addresses
Use BCC to protect the email addresses of other recipients. (e-mail image by fotoman_65 from

When you're sending e-mails to multiple recipients, you may not want to expose the email address of each recipient. The blind carbon copy (BCC) feature allows you to send e-mails to multiple addresses without displaying the email of each addressee. This feature is available in most e-mail account services and is simple to use.

Skill level:


  1. 1

    Log on to your e-mail account and click "Compose Mail" to create a blank e-mail document.

  2. 2

    Compose your message. When you are ready to send the message, look for a button titled "Add BCC." This is usually located near the "To" field on an e-mail composition page.

  3. 3

    Fill in the BCC field with the email addresses. You may add multiple e-mail addresses in one "Add BCC" field. Do this in the same manner that you would enter e-mail addresses in the "To" field.

  4. 4

    Enter your e-mail address in the "To" field if you wish to receive a copy of the email when you send it, although it is not necessary to enter anything there. If you wish, you may also enter another recipient's e-mail address.

  5. 5

    Click "Send" to e-mail your message to all listed recipients. If you listed your e-mail address in the "To" field, you will receive a copy of the message in your inbox.

Tips and warnings

  • Send messages via "CC" (carbon copy) if you wish other recipients to see the email address or addresses listed in the "CC" field. Otherwise, do not include names in the "CC" field.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.