Gmail Email Signature With Image or Logo: 2026 Working Recipe

Gmail Help documents a hard 10,000-character cap per signature, and the image you insert counts against that cap — a single oversized logo can swallow the entire budget before you type your name. As of 2026, Gmail’s signature editor offers three ways to drop a logo into your block (a public URL, a local upload, or a Google Drive picker), and only one of them survives forwards across every device cleanly. This walks through the native insert options, the dimensions and file size that render crisply without breaking the limit, the hosting trick that keeps your logo alive years later, the Mobile Signature trap that doubles your block on Android, and a complete recipe that produces a branded signature both you and your recipients can read.

The three ways Gmail lets you insert an image

Gmail’s signature editor exposes an Insert Image button that opens a three-tab picker: Web Address (URL), My Drive (Google Drive), and Upload. Each route stores the image differently and survives forwards differently. Web Address keeps a remote reference to your hosted URL. My Drive links to a Drive file via a sharing URL. Upload converts the file into a remote image stored on Google’s user-content servers tied to your account.

To find the picker: open Gmail on the web, click the gear icon top-right, hit See all settings, scroll to Signature on the General tab, and click into an existing signature or create a new one. The toolbar above the editor includes an Insert image icon (a small picture frame). Clicking it opens the three-tab dialog.

What each tab actually does behind the scenes:

• Web Address (URL). You paste the public HTTPS URL of an image. Gmail inserts an <img src="https://..."> tag that points at your URL. Recipients fetch the image from your server every time they open your email. The image lives as long as the URL stays reachable.
• My Drive. You pick a file from your Google Drive. Gmail rewrites the reference to a Drive lh3.googleusercontent.com or drive.google.com/uc?id=... URL. The image must be shared publicly (Anyone with the link can view) or recipients see a broken-image placeholder.
• Upload. You select a file from your computer. Gmail uploads it to its own user-content servers and inserts an <img> tag pointing at the resulting URL. The URL is tied to your Google account; it remains reachable as long as the account exists and Google does not migrate the storage backend.

I tested all three in May 2026 against Gmail web on Chrome 126. Upload was the easiest path for a one-off personal signature. Web Address was the cleanest for a team that controls its own hosting. My Drive worked but is the most likely to surface “image blocked” warnings in stricter recipient clients (Outlook desktop in particular).

The generic Gmail signature setup guide walks through the editor end to end if you have never opened it before. This article picks up specifically with the image-or-logo workflow.

Right dimensions and file weight for a logo

A signature logo renders cleanly at 100 to 200 pixels wide and 30 to 80 pixels tall, exported as PNG with a transparent background or JPEG with a white background, and weighing 10 to 30 KB. Anything wider than 300 pixels or heavier than 50 KB starts costing you on mobile rendering, signature character budget, and email-client trust scores.

The reasoning behind those numbers:

• Width. Gmail’s reading pane on a 13-inch laptop is roughly 600 to 800 pixels wide. A logo above 300 pixels dominates the signature visually and pushes contact text to a second line on narrow viewports. 150 pixels is the sweet spot for a wordmark; 60 to 80 pixels for a square icon.
• Height. Keep the logo roughly the height of three to four lines of text. Beyond 80 pixels, the signature starts to look like a banner ad.
• Format. PNG with transparency wins for wordmarks and icons because it blends into both light and dark mode reading panes. JPEG works for photographic logos but locks you into a single background color. SVG is supported in some email clients but stripped or rendered inconsistently by others — avoid it for signatures.
• File weight. Under 30 KB keeps your signature snappy and well under the 10,000-character cap documented by Gmail Help. Heavier files compound across thousands of sent messages and increase the chance recipients on mobile data block remote images.

Resolution matters less than dimensions because Gmail does not natively support srcset in signatures. Export at the actual display size (or 2x for retina sharpness) — do not upload a 2,000-pixel master and resize via the width attribute. The 2,000-pixel file still ships to every recipient and burns bandwidth.

Try Mailbird free

Hosting the image so it survives forwards

A Gmail signature image needs a publicly reachable HTTPS URL to render in recipients’ inboxes. The most durable hosting is your own website or a CDN you control, where you pin the file to a stable path (e.g., yourcompany.com/email/logo.png) and never replace or rename it. Free uploaders, expiring image hosts, and Drive folders that get reshuffled are the leading causes of broken-image signatures three to six months after setup.

The mechanic is simple: when you use the Web Address tab, Gmail inserts the URL you provided. When you use Upload, Gmail inserts a URL on its own user-content servers. Either way, the recipient’s email client fetches that URL when they open the message. If the URL stops resolving — because you cancelled a hosting service, moved the file, or the provider expired the link — every email you ever sent shows a broken-image placeholder where your logo used to be.

Practical hosting choices, ranked by longevity:

• Your own domain. Upload logo.png to a stable path on your website. The image lives as long as the domain does. Best for organizations.
• A managed CDN. Cloudflare, Bunny, AWS CloudFront. Stable, fast, cheap. Best for teams without a website’s static asset folder.
• Google Drive (public file). Workable if you treat the file as permanent, but watch the share-link URL format (covered next section). Test before relying on it.
• Gmail’s own Upload tab. Convenient. Stable as long as your Google account stays active. The URL format is undocumented and could in theory change, but in practice has held for years.
• Free image hosts (Imgur, ImgBB, etc.). Risky. Some strip hotlinking, some expire inactive files, some change URL schemes. Avoid for anything you care about long-term.

For a wider take on signature templating including the HTML signature recipe that wraps your logo into a custom branded layout, that companion guide covers the table-based markup and inline styles you need.

Using Google Drive as the host

Google Drive can host a signature logo, but the file must be set to “Anyone with the link can view” and the URL Gmail uses is in the lh3.googleusercontent.com format rather than the standard drive.google.com/file/d/… share URL. Some recipient email clients (notably older Outlook desktop) flag Drive-hosted images as suspicious or block them by default, so test deliverability before deploying to a team.

The setup, step by step:

1. Upload your logo to Google Drive in an account you control long-term. Personal accounts are fine; Workspace accounts are better because they tie to a business domain.
2. Right-click the file and choose Share. Set general access to Anyone with the link and access level to Viewer. Click Done.
3. In Gmail’s signature editor, click Insert Image, switch to the My Drive tab, navigate to your file, select it, and click Insert.
4. Gmail places the image in the signature using a Drive-backed URL. Save Changes at the bottom of the General tab.

Why some teams avoid this path despite the convenience:

• Stricter recipient clients can block the image. Outlook on Windows with default security settings sometimes refuses to load remote content from Google Drive URLs without explicit user approval.
• Drive share-link URL formats have changed over the years. Long-lived URLs have continued to work, but the format Google generates today is not the format from five years ago. A future migration is not impossible.
• Public Drive files leak metadata. The filename, file owner (in some cases), and last-modified timestamp can be readable by anyone with the URL. Keep the filename neutral (logo.png, not logo-final-v3-FOR-SARAH.png).

For most one-person operations, Drive is fine. For teams shipping branded outreach at volume, owning the hosting on your domain is the safer call.

The Mobile Signature trap on Android and iOS

Your Gmail web signature with logo is stored server-side and used by the Gmail mobile apps when they compose a reply or forward, but the Gmail mobile apps also have a separate Mobile Signature setting per account that, when filled in, appends a plain-text signature to new messages composed in the app. The result is recipients see your full HTML signature followed by a plain-text signature stacked below it. Clear the Mobile Signature field in the app to stop the doubling.

How to clear it:

• Android: open Gmail → tap the hamburger menu → Settings → tap your account → Mobile Signature → clear the field → tap OK.
• iOS: open Gmail → tap the hamburger menu → Settings → tap your account → Signature Settings → toggle off.

After clearing, the Gmail mobile app uses your web-configured signature (logo included) on replies and forwards. New messages composed in the mobile app may also pick up the web signature depending on the Gmail app version. The doubling stops either way.

Two related caveats:

• Mobile data and image blocking. Some recipients on mobile data networks see remote images blocked by default in their mail client. Your logo shows as a placeholder until they tap “Display images.” There is no workaround in Gmail’s signature editor — this is a recipient-side setting.
• Dark mode. Gmail iOS and Android show messages in dark mode for users who enabled it. A logo with a transparent background blends in. A logo on a white box becomes a glaring rectangle against the dark UI. Export with transparency if you want it to behave on both light and dark.

For teams running heavy inbox volume on top of branded signatures, the organize work emails guide covers filters and labels that keep replies tidy regardless of signature rendering.

Aligning the logo next to your text

Gmail’s basic signature editor cannot natively place a logo to the left of your contact text — it inserts the image inline at the cursor position, and the text wraps to its right awkwardly on narrow viewports. To get a clean side-by-side layout (logo left, name and contact right), use a table-based HTML signature pasted in via the render-and-copy method, not the native Insert Image button.

What the basic editor can do with a logo:

• Insert the image inline with your text (Small, Medium, Large, or Original size).
• Center, left-align, or right-align the entire signature block (image included).
• Add line breaks above and below the image.

What it cannot do:

• Place the image and text in side-by-side columns with controlled padding.
• Vertically center the text against the image.
• Apply a specific font, color, or weight to the contact text right of the image.

If you need any of those, you have two options. First, the cleanest: build a table-based HTML signature with the logo in the left <td> and the contact block in the right <td>, render it in a browser, and paste it in. That is the method the HTML signature guide covers in detail. Second, use a signature generator (HubSpot Email Signature Generator, MySignature, WiseStamp, Mailbutler) that outputs table-based HTML and provides a one-click Copy-to-Gmail flow.

The basic editor is fine for a vertical signature: logo on top, three lines of contact below. The moment you want logo-left/text-right with brand fonts and consistent padding, the HTML route is the only reliable path in 2026.

Testing across clients before you trust it

A Gmail signature with a logo that renders perfectly on Gmail web can still break in recipients’ inboxes — Outlook desktop blocks remote images by default, Apple Mail respects dark mode differently, and Gmail mobile apps on iOS sometimes resize images differently from Android. Before you rely on a new signature for outreach, send test emails to a Gmail account, an Outlook account, an iCloud account, and an Apple Mail account, and view each on both desktop and mobile.

A practical test matrix:

Recipient	Desktop	Mobile
Gmail	Web + Chrome	Gmail iOS + Android
Outlook	Outlook for Windows	Outlook iOS
Apple iCloud	Mail.app on macOS	Mail.app on iOS (dark mode on)
Yahoo	Yahoo web	Yahoo iOS

What to look for at each:

• Logo loads (no broken-image placeholder).
• Logo dimensions are correct (not stretched, not pixelated).
• Logo positions correctly relative to contact text.
• Signature is legible in dark mode.
• No doubled signature (mobile signature trap).
• Hyperlinks in the signature still work.

Anything that fails sends you back to either the hosting (URL not reachable), the dimensions (logo too wide for narrow viewports), the format (transparency missing for dark mode), or the mobile signature setting. Two hours of testing here saves three months of recipients seeing a broken-image placeholder where your brand should be.

A clean end-to-end recipe

The reliable recipe: export the logo at 150 pixels wide as transparent PNG under 30 KB, host it on your own domain or CDN at a stable HTTPS path, open Gmail Settings General Signature, click Insert Image, paste the URL, set defaults for new emails and replies, scroll to the bottom and Save Changes, then test across Gmail web, Gmail mobile, Outlook, and Apple Mail before relying on it.

The full sequence as I run it:

1. Export the logo. PNG with transparency, 150 pixels wide (or 300 for retina), under 30 KB.
2. Host the file. Upload to your domain at a stable path (yourcompany.com/email/logo.png) or a CDN you control. Pin it; never rename or replace.
3. Open Gmail Settings. Gear icon → See all settings → General tab → scroll to Signature.
4. Create or edit a signature. Click Create new, name it, or click into the existing one.
5. Insert the image. Click the Insert image icon → Web Address tab → paste the URL → set size (Small/Medium/Large/Original) → click Select.
6. Type or paste contact text below or to the side of the image. For a side-by-side layout, build the markup separately as table HTML and paste from a rendered browser tab.
7. Set signature defaults. Under “Signature defaults,” choose which signature applies to new emails and to replies and forwards.
8. Save Changes. Scroll to the bottom of the General tab and click Save Changes. The save is page-wide, not per-section. Gmail does not auto-save.
9. Clear the Mobile Signature on Android and iOS Gmail apps to avoid the doubling trap.
10. Send test emails to Gmail, Outlook, iCloud, and Apple Mail addresses you control. View each on desktop and mobile.
11. Toggle dark mode on at least one mobile test and verify the logo still reads cleanly.
12. Document the URL somewhere your future self can find it (notes app, internal wiki). The day the logo breaks, you will want to know exactly which file lives where.

If you maintain multiple sending identities under Gmail aliases or use keyboard shortcuts for high-volume sending, each send-as identity carries its own signature slot — repeat the recipe per identity.

For the broader inbox hygiene around signature-led outreach, including the automate inbox cleaning guide, the workflow scales as your sending volume grows.

Frequently asked questions

Can I add an image to my Gmail signature without hosting it somewhere?

Yes — Gmail’s Insert Image button offers an Upload tab that lets you select a file from your computer. Gmail uploads it to its own user-content servers and the image lives there as long as your Google account stays active. The convenience trade-off is that the URL format is undocumented, so the signature is harder to migrate to another tool later compared to a URL you control on your own domain.

What is the recommended logo size for a Gmail signature?

A signature logo renders cleanly at 100 to 200 pixels wide and 30 to 80 pixels tall, exported as PNG with a transparent background, weighing 10 to 30 KB. A 150-pixel-wide wordmark is the most common sweet spot for desktop and mobile rendering. Anything wider than 300 pixels dominates the signature visually and can push contact text to a second line on narrow viewports.

Does the image count toward Gmail’s signature character limit?

Yes. Gmail Help documents that the image counts toward the 10,000-character signature limit. A base64-embedded image can blow the limit on its own, so always use hosted URLs (Web Address or Upload tab) rather than embedding image data directly in the HTML. If you hit the limit with an external image still referenced by URL, the rest of the signature markup is the issue, not the image — strip unnecessary inline styles.

Why does my Gmail signature logo show as a broken image in recipients’ inboxes?

Three common causes. First, the hosting URL stopped resolving — a moved file, an expired hosting account, or a renamed path. Second, the recipient’s email client blocks remote images by default (common in Outlook on Windows). Third, the URL uses HTTP rather than HTTPS, and the recipient’s client blocks insecure remote content. Verify the URL is reachable, stable, and HTTPS, and send test emails to multiple recipient clients before relying on the signature.

How do I align my logo to the left of the contact text in a Gmail signature?

The basic Gmail signature editor does not support side-by-side image-and-text layouts — it inserts images inline. To get a clean logo-left, contact-right layout, build the signature as table-based HTML with the logo in one cell and the contact block in another, render it in a browser tab, then copy and paste the rendered output into Gmail’s signature editor. Inline styles survive the paste; CSS classes do not.

Why does my mobile Gmail show two signatures stacked together?

The Gmail mobile apps on Android and iOS have a separate Mobile Signature setting per account. When filled in, it appends a plain-text signature to new messages in addition to the web-configured HTML signature with your logo. Clear the Mobile Signature field in the app’s per-account settings (Mobile Signature on Android, Signature Settings on iOS) and the doubling stops.

Sources

1. Google, “Create a Gmail signature” — 10,000-character limit, image-counts-toward-limit rule, Insert Image picker (URL/Drive/Upload tabs), multi-signature defaults. support.google.com/mail/answer/8395
2. Google Workspace Admin Help, “Set up Gmail compliance footers” — server-appended footers that interact with user signatures. support.google.com/a/answer/2905869
3. Google, “Share files from Google Drive” — public sharing controls for files used as signature image hosts. support.google.com/drive/answer/2494822