Gmail gives you three ways to add a signature image — upload, Drive, or a URL. Here's which one actually survives forwarding, replies, and Google's 2024 Drive change.
The MailSigCraft Team
MailSigCraft
Gmail's signature settings quietly offer three separate ways to insert an image, and picking the wrong one is why a logo that looked fine in Settings shows up as a broken icon, a stray attachment, or nothing at all once it reaches someone else's inbox. The three methods aren't interchangeable — one of them was effectively broken by a Google infrastructure change in 2024, and most people don't find out until a client or coworker mentions it.
In Gmail's signature editor, click the image icon and choose the "Upload" tab instead of "Web Address (URL)" or "My Drive." Gmail re-hosts the file the moment you insert it, so there's no external dependency for a recipient's mail client to fail to reach later. This is the closest thing to a "just works" option among the three.
Google no longer reliably serves Drive-hosted images to external embeds the way it used to. If your signature currently pulls an image from Drive, replace it — don't wait for it to break for everyone at once, because it often fails inconsistently (works for some recipients, not others) before it fails completely.
The "Web Address (URL)" option only works when the link resolves directly to an image file (ending in .png, .jpg, .gif, or .webp), served by hosting you control and don't expect to take down. A link to a webpage that merely displays the image won't insert correctly.
Google's own guidance recommends a signature image between 70–100 pixels high and 300–400 pixels wide, with 100 pixels high by 1,000 pixels wide as the hard maximum. Resize before uploading — Gmail will accept an oversized file, but replying with it can quietly push you toward the signature length problems in the next section.
Gmail re-hosts the file itself the moment you insert it, so there's nothing external for a recipient's client to fail to reach.
Not your current source, but worth knowing: this is the method Google itself quietly broke for many embedding cases in 2024.
Works well once your image has a stable, direct file URL — many signature tools (including MailSigCraft) give you one automatically when you upload a logo.
Based on Gmail's three official signature image-insertion methods and Google's own guidance on Drive sharing scope. Not a live check of your actual image — a reliability read on the method itself.
Starting January 10, 2024, Google stopped supporting the classic drive.google.com/uc?id=... pattern that let a Drive file render like a normal hosted image inside an <img> tag — the method most "how to add a signature image from Drive" guides had relied on for years. Google gave affected integrations until May 1, 2024 to migrate off it. Signatures built on that pattern didn't get an error message; the image just started failing to load for some or all recipients, because embedding a Drive file this way was never an officially supported use case in the first place — it worked until Google changed how Drive serves that content, and then it didn't.
Gmail's own signature editor states that an inserted image counts toward your signature's character limit, the same 10,000-character HTML cap covered in our post on Gmail's character limit. A large uploaded image (which Gmail encodes as part of the signature's stored HTML) can eat meaningfully into that budget before you've added a single social icon or disclaimer line — which is why "my signature got cut off right after I added a logo" is a common support pattern, not a coincidence.
When an email is composed or rendered in plain text rather than HTML — an old client, a "Plain text mode" toggle, or a stripped-down inbox — there's no way to embed an image inline, because plain text has no concept of an <img> tag. Whatever image would have displayed inline gets attached to the message as a file instead. This is a property of the message format, not a bug in your signature, and it's the most common reason a signature "looks fine to me" but shows up as a random attachment for one specific recipient.
Even setting aside the 2024 hotlinking change, a Drive-sourced signature image only ever worked when its sharing was set to "Anyone with the link" → Viewer. If it's scoped to "people in your organization," it renders for your coworkers and shows a broken-image icon for every external recipient — which is most of the people a signature is actually for.
Some Google Workspace admins restrict signature image sources to Web Address (URL) only, to keep control over what gets embedded in outbound mail. If your Gmail signature settings only show a URL field and no Drive or Upload tab, that's an admin-level restriction, not a bug — ask your Workspace admin rather than troubleshooting the image itself.
Gmail hosts the file itself once inserted. No external link to go stale, no sharing settings to misconfigure. The image does still count toward the 10,000-character signature limit.
Works cleanly as long as the URL is a direct link to the image file on hosting you control. This is effectively what MailSigCraft and similar tools give you automatically — a stable, direct image URL you can paste straight into Gmail's field.
Requires exact "Anyone with the link" sharing, and even then is the least dependable option since Google's January 2024 change to how Drive serves embeddable content. Not recommended for new signatures.
Upload from your computer, or a direct Web address (URL) pointing at hosting you control. Both are self-contained and don't depend on Google Drive's sharing behavior. Avoid Google Drive for any signature you're setting up today.
Most likely Google's January 2024 change to how Drive serves embeddable content, which broke the classic drive.google.com/uc?id=... embedding pattern many older signature guides relied on. The fix is to switch to Upload or a properly hosted URL rather than trying to restore the old Drive link.
That happens when the message is sent or displayed in plain text rather than HTML — plain text has no way to embed an image inline, so it gets attached as a file instead. It's a property of the message format on that particular send, not a broken image.
Yes — Gmail's own signature settings note that an inserted image counts toward the same 10,000-character HTML cap as your text. A large image can meaningfully shrink how much room you have left for social links or a disclaimer.
Google recommends roughly 70–100 pixels high by 300–400 pixels wide, with 100 pixels high by 1,000 pixels wide as the absolute maximum it will accept. Resize before uploading rather than letting Gmail scale a much larger file down.
Gmail will accept and display one, but treat it as a display case, not a reliability case — the underlying insertion method (Upload, Drive, or URL) still determines whether the file survives forwarding, and some recipients' mail clients will only ever show the first frame regardless of how the GIF was inserted.
Gmail's image field gives you three options, but they aren't equally reliable: Upload is the most self-contained, a direct-hosted URL is close behind it, and Google Drive has been the risky choice since Google changed how it serves embeddable content in January 2024. Pick one of the first two, size the image to Google's recommended range first, and check that it survives an actual forward and reply — not just the preview in Settings.