> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/support/mark-all-emails-as-read-in-gmail.md).

# How to Mark All Emails as Read in Gmail

Mark all emails as read in Gmail using Missive's bulk actions.

You can mark all unread emails as read in Gmail using a simple search filter and bulk action. Changes sync automatically to any email client connected to your Gmail account.

[Missive](https://missiveapp.com) is a collaborative email app that syncs with Gmail. When you mark emails as read in Gmail, the changes are reflected in Missive automatically. You can also use Missive's bulk actions to mark multiple conversations as read directly.

## Steps to mark all emails as read in Gmail

1. Open [Gmail](https://mail.google.com) in your browser
2. In the search bar, type `is:unread` and press Enter
3. Click the **Select All** checkbox (top-left of the email list)
4. Click **Select all conversations that match this search** (the blue link that appears)
5. Click the **Mark as read** button (envelope icon)

All your unread emails will now be marked as read.

## Mark emails as read in Missive

In Missive, you can select multiple conversations by holding <kbd>Shift</kbd> and clicking, then use the **Mark as read** action from the toolbar.

***

**Related:** [Gmail / Google Workspace](/docs/core-features/connected-accounts/email-accounts/gmail-google-workspace.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://missiveapp.com/docs/support/mark-all-emails-as-read-in-gmail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.