How to Send a Calendar Invite in Gmail

Gmail and Google Calendar are two halves of the same product, but the seam between them shows. There are at least three different ways to send a calendar invite from Gmail, they produce slightly different results, and the one most people reach for first is the one with the most limitations.

Here is how each route works, what your recipients actually see depending on which email provider they use, and what to do when the invite never arrives.

How to send a calendar invite in Gmail from the compose window

This is the fastest option when you are already writing an email to the people you want to invite.

1. Open Gmail and click Compose.
2. Add your recipients in the To field first. Gmail carries them across, so doing this before the next step saves retyping.
3. In the toolbar along the bottom of the compose window, click the calendar icon (the tooltip reads "Set up a time to meet").
4. Choose Create an event. The other option, Offer times you're free, does something different: it inserts a picker so the recipient chooses a slot, and no event is created until they do.
5. A Google Calendar side panel opens with the recipients already added as guests. Set the title, date, time and duration.
6. Click More options if you need the description field, guest permissions or a meeting room.
7. Click Save. Gmail inserts an event summary block into your draft.
8. Send the email. The invitation goes out with it.

The limitation of this route is that the side panel is a cut-down editor. You cannot set guest permissions or attach files from it without clicking through to the full editor, and the event block in the email body is a summary rather than the invitation itself.

Route two: create an event from an email you have received

If a thread has turned into "we should meet about this", Gmail will lift the context for you.

1. Open the email.
2. Click the three-dot More menu in the top toolbar of the message, next to the reply arrows.
3. Choose Create event.

Google Calendar opens a new event with the email subject as the title, the message body pasted into the description, and everyone on the thread already added as guests. That last part catches people out: if the thread had a wide CC list, you have just invited all of them. Check the guest list before saving.

Sending a Gmail calendar invite from Google Calendar directly

This is the one to use for anything that matters, because it exposes every setting.

1. Go to calendar.google.com.
2. Click Create in the top left, then Event.
3. Click More options to open the full-page editor.
4. Enter the title, date and start and end times.
5. Click the timezone name shown next to the time. Set it explicitly if any guest is in another country.
6. In the Guests panel on the right, type each email address and press Enter after each.
7. Set the Guest permissions checkboxes (covered below).
8. Add a location, a Google Meet link if you need one, and the agenda in the Description box.
9. Click Save. Google asks "Would you like to send invitation emails to Google Calendar guests?". Click Send.

If you skip that final Send and choose "Don't send", the guests are attached to the event but never receive an email, which is a surprisingly common cause of "nobody turned up".

Guest permissions, explained properly

The three checkboxes under the guest list are more consequential than they look.

• Modify event. Guests can change the time, title, location and guest list, and those changes propagate to everyone. Grant this only to co-organisers. It is the most common source of an event mysteriously moving.
• Invite others. Guests can add people. Handy for "bring whoever needs to be there", risky for anything confidential, because the new attendees also see the description and any attachments.
• See guest list. On by default. Turn it off when you are inviting people who should not see each other's email addresses, such as customers or candidates. With it off, guests see only the organiser and the total count.

What recipients actually see

This is where the same invite diverges depending on the recipient.

Recipient	What arrives
Gmail or Google Workspace	An inline card with Yes, No and Maybe buttons. The event is often added to their calendar automatically, marked as needs action.
Outlook or Microsoft 365	Usually renders as an invitation, but often as an email with an invite.ics attachment they must open first. Times occasionally display shifted if the timezone data is misread.
Apple Mail on iCloud	Generally renders correctly with accept and decline, though the event may not appear on the calendar until accepted.
Yahoo, Proton, or a work system on an older server	Frequently just a plain email with an attachment, and no obvious way to respond.

If you want to see exactly what you sent someone, forward the invite to yourself, save the .ics attachment and drop it into the ICS file viewer. It will show the method, the sequence number, the timezone and the full attendee list, which usually explains the problem in about ten seconds. If the format itself is unfamiliar, the guide to what an ICS file is is the place to start.

Tracking RSVPs in Google Calendar

Open the event from your calendar grid and look at the guest list. Each name carries a status:

• A tick for accepted
• A cross for declined
• A question mark for maybe
• No mark at all for no response yet

The header above the list summarises it, for example "3 yes, 1 no, 2 awaiting". Google emails you when someone responds, unless you have turned that off under Settings > General > Notification settings > Event responses.

Two caveats worth knowing. First, "awaiting" is ambiguous: it covers both "saw it and has not decided" and "never received it". Second, external guests on non-Google systems often respond in a way that never makes it back to your event, so they sit at awaiting forever even though they replied. If reliable headcounts matter, a proper RSVP flow gives you an answer that does not depend on two mail servers agreeing.

Common failures and how to fix them

The invite went to spam

Invites to personal addresses at Gmail, Yahoo or Hotmail regularly get filtered, because an .ics attachment from an unfamiliar sender looks like a phishing pattern. Ask the recipient to search for has:attachment ics or check the Spam and Promotions tabs, then mark it not spam so future ones land.

It never appeared on their calendar at all

Google has a setting at Settings > Event settings > Add invitations to my calendar with three values: from everyone, from known senders only, and when I respond in email. Many accounts default to known senders. If you have never emailed the person before, you are not a known sender and the invite quietly does not appear. Tell them to check that setting, or send a plain-text version of the details as well.

The Outlook recipient sees an attachment instead of buttons

Nothing is broken. Their client did not parse the invitation inline. They can open the attachment, which will offer accept and decline, but many people never do. For an external audience, send a link they can click rather than a file they have to open.

Updates are not propagating

When you edit an event, Google sends a fresh request with an incremented sequence number. It only applies if the recipient's calendar holds a matching copy with the same UID. If they added the event manually, forwarded it, or their original copy was never created, the update has nothing to update and silently does nothing. This is why a changed start time so often reaches only some of the room.

The guest list is wrong after a forward

Forwarding a Google invite to a third party sometimes adds them as an attendee and sometimes does not, depending on the forwarder's client. Add people yourself in the event editor instead.

Where the Gmail approach runs out

Everything above works well for internal meetings. It gets shaky the moment the audience is outside your organisation, and it has three hard limits.

The event belongs to your Google account, so it cannot be handed over or managed by someone without access to that account. You cannot update it in the recipient's calendar with any confidence once cross-provider delivery is involved. And you cannot see who genuinely added it, only who clicked a button inside Google's ecosystem.

For anything sent to a list, a newsletter, a customer base or an audience you do not control, the more reliable pattern is a single link. An add to calendar link detects the recipient's calendar and opens the right one, so Outlook, Apple and Yahoo users get the same clean experience as Gmail users. The event details stay editable after sending, and you get a real count of how many people added it rather than a guess. The free link generator will produce one without an account.

The same logic applies in the other direction too: if you are on the receiving end of these invites, accepting a Google Calendar invite has its own set of quirks. And if your recipients are on Microsoft, the Outlook side of the story explains what they are seeing.

Use the Gmail route for your team, and a link for everyone else. That split avoids most of the failures above.