What Is IMAP Server for Gmail Explained Clearly

The IMAP server for Gmail is imap.gmail.com on port 993 with SSL/TLS, the address a mail app uses to sync the mailbox on Google's servers rather than keep a private downloaded copy. You're probably staring at a setup screen in Outlook, Apple Mail, or a phone app right now, with empty boxes for server, port, and encryption, and a password prompt that keeps coming back. Your laptop shows one inbox, your phone shows another, and a message you read this morning still looks new somewhere else.

That drift is exactly what asking what is IMAP server for Gmail should help you fix. The hostname gets you connected, but it doesn't explain why sync stalls on a large mailbox, why one message shows up twice, or why deleting in one app removes mail everywhere. Treat Gmail IMAP as a sync contract, with rules for bandwidth, labels, and deletion, and the setup starts to make sense.

Gmail IMAP Server Address Port and Encryption

Type imap.gmail.com as the incoming server, 993 as the port, and SSL/TLS as the encryption. That's the lookup many readers came for, and you can copy it before you read anything else. If your app separates incoming and outgoing settings, don't reuse the IMAP line for sending.

Gmail IMAP and SMTP settings

What Each Column Means

The hostname is the address your app contacts on the internet. The port is the numbered door on that server where the encrypted IMAP service listens. Encryption isn't optional here, because Gmail expects a secure connection from the first packet, not a plain connection that upgrades later.

Your username is your complete Gmail address, not just the part before the @ sign. That detail trips up manual setups in Thunderbird and older versions of Outlook. If the app asks for a display name separately, that's the name recipients see, and it has nothing to do with signing in.

According to Google's Workspace mail client setup guide, Google identifies the incoming server as imap.gmail.com on port 993 with SSL, while SMTP sends mail through ports 465 or 587 depending on the encryption method. That same guide notes that users authenticate with an authorized method, and that Workspace organizations may apply administrative controls to third party access. Correct values in every box still won't connect if an admin has blocked your client.

Practical rule: If you can receive mail but can't send it, stop retyping the IMAP line. Check the outgoing server instead, because receiving and sending are two different connections.

What a Working Connection Looks Like

Success doesn't look like a folder full of downloaded files on one computer. It looks like agreement. A message you read in Apple Mail shows as read in Gmail on the web, a folder you check on your phone matches the one on your laptop, and nobody forwards mail by hand to keep devices aligned.

That happens because your app is interacting with the mailbox stored on Google's servers. The app keeps a local cache so you can search and scroll quickly, but the server copy is the one that counts. Lose the laptop, and the mailbox is still there when you sign in somewhere else.

For a small business or sales team, that consistency is the value. Shared workflows, inbox monitoring, and follow up status stay aligned across desktop and mobile apps, without someone maintaining a separate copy of the mail. You still need to understand the limits and deletion rules covered later, but the three values in the table are the correct starting point.

One last check before you save the account. If your app offers a choice between SSL/TLS, STARTTLS, and None for the incoming server, pick SSL/TLS with port 993. Choosing STARTTLS with 993, or leaving encryption off, produces the vague connection errors that send people hunting for a new password they don't need.

How IMAP Sync Differs From POP and SMTP

Think of your mailbox as a shared filing cabinet that lives in one office. POP takes folders home to one computer, so the cabinet can end up empty for everyone else. IMAP lets your laptop, phone, and browser open the same cabinet, and a note you leave on a folder in one place is visible in the others.

The diagram below shows the download model that causes most multi device trouble.

A Read Message, Step by Step

Say you open a client invoice in Apple Mail on your laptop. With IMAP, the app tells Gmail to change that message's flag from unread to read on the server. When your phone checks in a minute later, it sees the updated flag, and Gmail on the web agrees.

Nothing was forwarded or copied between your devices. They all read the same server state. IMAP clients can also list folders and labels, search messages, fetch headers and bodies, and change flags such as starred or deleted, which is why a well behaved app feels like a window onto Gmail rather than a separate mailbox.

POP works differently because it's built around downloading. A POP client pulls messages down to one device, and depending on its settings it may remove them from the server. Your phone can grab the morning's mail before your desktop checks, leaving the desktop looking empty and your read status split across machines.

IMAP, POP, and SMTP for a Gmail account

Where the Standard Comes From

IMAP isn't a Gmail invention. The Internet Engineering Task Force published RFC 3501, the IMAP4rev1 specification, as a proposed standard on March 20, 2003, defining a protocol that lets a client access and manipulate remote mailboxes, including syncing an offline client with the server. That specification puts a standard IMAP server on port 143 for an unencrypted or upgradeable connection, while Gmail uses the encrypted endpoint on port 993 instead.

That single number answers a common setup question. Port 143 is the old internet default, not a fallback you should try when Gmail refuses a connection. If your app fills in 143 automatically, change it.

This short walkthrough shows the same protocol choice from inside a mail app.

Choosing the Right Protocol for the Job

Choose IMAP when you check one account on a phone, a laptop, and the web, which describes nearly everyone reading this. Choose SMTP alongside it in every setup, because without smtp.gmail.com your app can read perfectly and still fail to send. A correct incoming setup gives you no sending ability at all.

Reserve POP for a deliberate single machine archive, and understand the risk before you enable it. If that one device downloads and removes mail, other devices and teammates may never see those messages. For a shared sales or support inbox, that's not a backup strategy, it's a way to lose track of customer replies.

POP answers the question of how to move mail onto one computer. IMAP answers how to keep every device looking at the same mailbox.

Be honest about the cabinet metaphor, though. IMAP isn't a guaranteed perfect mirror, because Gmail labels, daily bandwidth limits, and client deletion behavior can make the view diverge from what you expect. If your real problem is coordinating messages across several people, it also helps to understand how to send emails to multiple people cleanly, so replies land where the whole team can see them.

How to Connect a Mail App to Gmail IMAP

Most modern apps find Gmail's settings on their own when you choose Google as the account type. Manual setup matters when the wizard guesses wrong, when you're configuring Thunderbird or a custom tool, or when a Workspace policy forces you to check every value. Work through the steps in order and test at the end, not halfway through.

The Setup, in Order

1. Add the account as IMAP: In your mail app, choose Add Account, then manual setup or IMAP if it asks. Don't accept POP if the wizard suggests it.

2. Enter the full address: Use your complete Gmail address as the username, in both the incoming and outgoing sections if the app asks twice.

3. Set the incoming server: Enter imap.gmail.com, port 993, and SSL/TLS. If there's a root folder or path prefix box, leave it empty unless your admin tells you otherwise.

4. Set the outgoing server: Enter smtp.gmail.com with port 465 and SSL, or port 587 with STARTTLS. Turn on outgoing authentication so the app signs in before sending.

5. Sign in with Google: Prefer the browser based Google sign in your app offers, instead of typing your Gmail password into a form inside the app.

6. Use an app password only as a fallback: If the app can't do that sign in and your account allows app passwords, generate one and paste it where the password goes. Don't store your everyday Gmail password in the client as the normal approach.

Why OAuth Is the Default, Not a Preference

Google's developer documentation explains the modern model clearly. Per Google's guide to OAuth 2.0 for Gmail IMAP and SMTP, clients should authenticate with OAuth 2.0 through the SASL XOAUTH2 mechanism using the Gmail scope https://mail.google.com/, presenting a short lived access token during the IMAP AUTHENTICATE XOAUTH2 exchange instead of collecting your password. That guide also describes Gmail IMAP as a state synchronization interface on imap.gmail.com port 993 with SSL/TLS required from connection start.

In plain terms, you approve the app in a Google sign in window, and the app receives a token it can use and renew. You can revoke that access later from your Google account. A stored password gives you none of that control, which is why password prompts that loop forever usually mean the app is trying an old sign in method.

Workspace Accounts and Custom Tools

On a Google Workspace account, an admin policy can block third party IMAP access entirely. Ask the admin before you spend an hour retyping a hostname that's already right. One question about allowed clients saves a long round of guessing.

If you're connecting Gmail to a CRM or support tool rather than a mail app, the shape is the same but the responsibility is bigger. Request the user's consent, store refresh tokens securely, refresh access tokens before they expire, and treat full mailbox access as a broad permission. Build the workflow to touch only the mail it needs.

Test Before You Trust It

Send one message to yourself from the new account. Mark it read in the app, then open Gmail on the web and confirm it shows as read there too. That single check proves incoming sync, outgoing sending, and flag changes in about a minute.

Then check where the app stores Sent and Drafts. Point both at Gmail's own folders so a draft you start on your laptop is waiting on your phone, and so sent mail doesn't split into a local copy plus a server copy. Folder mapping screens hide in different places, under mailbox behaviors in Apple Mail and under account folders in Thunderbird, but every serious client has one.

Bandwidth Caps Labels and Folder Limits

A big mailbox can connect perfectly and still fail to sync. The reason is usually arithmetic, not a wrong password. Gmail caps how much data IMAP can move each day, and a first sync that tries to download years of mail can burn through that budget before lunch.

Gmail IMAP quota and label limits

Google Workspace's Gmail bandwidth limits documentation lists a daily IMAP download limit of 2,500 MB and an IMAP upload limit of 500 MB per account, and exceeding them can interrupt synchronization until the quota window resets. The same documentation notes 500 labels as a best practice ceiling for avoiding IMAP download limit problems. Those are per account limits, so two apps syncing the same mailbox draw from the same budget.

What Burns the Budget

Three habits do most of the damage. Downloading every message body on the first sync, polling every folder for changes on a short timer, and re-fetching attachments that haven't changed all consume bandwidth without improving what the app knows. A mailbox full of scanned contracts and photo attachments reaches the cap far sooner than the message count suggests.

The symptom is distinctive once you've seen it. Sync runs happily for hours, slows, then stops, and the app reports a server problem that mysteriously clears the next day. Nothing is broken. The account has used its allowance and has to wait.

How a Resilient Sync Behaves

A better connector performs an incremental first sync, pulling recent mail and headers first instead of the entire archive. It syncs only the labels the app needs, caches message identifiers and metadata, and fetches full bodies or attachments when someone opens them. Most desktop clients offer a simpler version of this as a setting to download only recent mail or to skip large attachments until requested.

For a small team, the practical move is turning off All Mail and low value labels in the client. All Mail contains everything, so syncing it alongside your other folders means downloading most messages again under a second name. A faster internet connection doesn't help, because the ceiling is on Google's side.

The Label Problem Nobody Warns You About

Gmail doesn't really have folders. It has labels, and it shows each label to IMAP clients as if it were a folder. One message labeled both Inbox and Clients can therefore appear in two IMAP folders, even though it's a single message sitting in Gmail.

A careless importer treats those two appearances as two emails and logs the customer conversation twice. Apps should key off a stable message ID and ignore the second folder appearance, so the same message never becomes two CRM activities. If you're evaluating a tool that syncs Gmail, ask how it deduplicates mail that carries multiple labels. A blank look is an answer.

Watch for this: A label for every client, campaign, and year feels organized in Gmail and behaves like hundreds of extra folders in an IMAP client. Organization on one side becomes load on the other.

Consolidating labels you no longer use, and syncing a short list of labels that matter, reduces bandwidth use, retries, and duplicate records at the same time. It's dull maintenance, and it's the difference between a mailbox that syncs in minutes and one that stalls every afternoon.

Fixes When IMAP Gmail Com Will Not Connect

Start by abandoning the search for an Enable IMAP switch. Many older guides send you into Gmail settings to flip a toggle that may not be there anymore. If you can't find it, that isn't your problem, and hunting for it wastes the time you should spend on the hostname, port, encryption, and sign in method.

According to Google's guidance on checking Gmail through other email platforms, the Enable/Disable IMAP option is being removed from the consumer interface beginning January 2025 because IMAP access is always on, while existing connections remain unaffected. Google also documents controls for folder size limits, automatic expunging, and what happens when a client marks a message as deleted. So the missing toggle tells you nothing, and the settings that remain are the ones worth checking.

Match the Symptom Before You Change Anything

Gmail IMAP symptoms causes and fixes

The Three Fixes People Skip

Authentication errors deserve first attention because they're the most common. If the app keeps rejecting a password you're sure is right, it probably isn't a typing problem. The client is sending your regular Gmail password where Google expects an OAuth sign in, or the consent request was denied, or Workspace has blocked that app. While you're checking access, it's worth confirming that legitimate senders aren't being filtered on your side either, which is where knowing how to whitelist an email address saves a separate round of confusion.

Deletion deserves a test, not an assumption. Marking a message deleted in an IMAP client and expunging it isn't always the same as moving it to Gmail's Trash, where you could recover it. Send yourself a disposable message, delete it in the app, and watch where it lands in Gmail on the web before anyone on the team uses that setup on real mail.

Folder selection is the third quiet culprit. Syncing All Mail plus every label can look exactly like a broken server when it's really a quota being consumed by duplicate downloads. Trim the folder list, check folder size limits in the client, and confirm that Drafts and Sent point at Gmail's folders so you don't get two copies of everything you send.

A correct imap.gmail.com line cannot repair a quota, a blocked OAuth consent, or a client that deletes on sync. Diagnose the symptom in front of you instead of retyping the one setting that is already right.

Change one thing at a time and retest. If you fix the sign in method, trim folders, and remap Sent in a single sitting, sync may start working and you'll have no idea which change mattered. You'll want that knowledge the next time it breaks.

Read Mail or Send at Scale

Everything so far serves one decision. If your job is reading one Gmail mailbox on a phone and a laptop, you're done once a mail app points at the right server with OAuth sign in. If your job is sending personalized outreach from several inboxes, a mail app was never the right tool, and no IMAP setting will turn it into one.

If Reading Is the Goal, Run These Checks

Confirm one read flag matches between your app and Gmail on the web. Send one message and confirm it appears exactly once in Sent. Leave All Mail unsynced, and test delete on a disposable message before anyone else uses that profile.

Those four checks take five minutes and catch the failures that otherwise surface weeks later as missing mail or doubled conversations. Write down the settings that passed, including the folder mappings, so the next laptop setup is copying a known good configuration instead of starting from memory. Teams that skip this end up with five slightly different setups and five different versions of the truth.

If Sending at Volume Is the Goal, the Tool Changes

A mail client gives you no control over how volume spreads across inboxes, how fast each account sends, or whether replies get logged against the right contact. Sending from several accounts through ordinary mail apps also means each person babysits their own folders, and nobody sees the full picture. Comparing purpose built options is a better use of that effort, starting with a frank look at cold email infrastructure services for better deliverability and what they manage for you.

Our platform may integrate with third party services such as email providers, CRM platforms, or communication tools, so connected mailboxes sit inside one workspace instead of scattered across apps. Within that setup, Stamina's Campaigns product rotates across multiple connected sending accounts automatically to keep volume low per inbox and deliverability high. A dedicated Growth Strategist manages deliverability optimization including domain health, warmup, and inbox rotation, which are exactly the jobs an IMAP client leaves undone.

Use mailbox sync to read and track status. Use a separate, purpose built workflow to send, and keep the two jobs from blurring into one overloaded inbox.

That separation also keeps you on the right side of the rules. Bulk outbound sending belongs in a workflow that follows anti-spam requirements for identified business recipients, with pacing and reply handling built in. Blasting a list from a desktop mail app risks the account your team depends on for ordinary customer mail.

So finish the account setup if reading is what you need, and enjoy having one mailbox that agrees with itself on every device. If the goal is an outreach pipeline, choose a dedicated sending workflow rather than a second copy of the inbox. Knowing what is IMAP server for Gmail gets your mail in sync, and knowing its limits tells you when to stop asking it to do a different job.

If your Gmail mailboxes are connected and in sync but outbound still depends on someone manually spreading sends across inboxes, Stamina can take over the sending side with automatic inbox rotation, deliverability management, and every reply logged in one workspace. Connect your mailboxes, let a dedicated Growth Strategist handle domain health and warmup, and spend your time on conversations instead of server settings.