How to Generate a Gmail Signature for Google Workspace Across Web, iOS, and Android

Start with the Gmail surface and sending identity

Gmail signature setup depends on two choices: the Gmail surface you use and the address you will send from. Start there before entering any text. A signature created in Gmail on a computer follows the web settings path, while a signature created in the Gmail app applies to messages sent from that app. Alternate sending identities also need their own preparation in Gmail’s Send mail as settings.

Use this order:

1. Choose the message surface. Decide whether you need the Gmail web signature, a mobile-app signature, or both. Gmail app signatures are configured separately from the computer workflow, and a signature created in the app appears only in messages sent from the Gmail app.
2. Choose the Google Workspace account. On mobile, open the Gmail app settings for the specific business email account, identified in the mobile instructions as the Google Workspace email account.
3. Choose the sending identity. If you will send from an alias or another address, prepare that identity in Gmail before testing the signature. Gmail places that setup under Send mail as.
4. List the message paths you need to support. Include a new message, a reply, and a forward. Also include each intended sending address and each client you expect to use.

The practical consequence is simple: do not treat one successful desktop test as proof that the same signature will appear in every Gmail app, account, or sending identity. Configure the surfaces and identities that your Google Workspace users will actually use, then test each path.

Choose the Gmail signature route by client and sender

Choose the signature route by client, sending identity, and message type before entering signature text. Use this order:

1. Select the client. Use Gmail on a computer for the web signature editor and default controls. Use the Gmail app when the message will be sent from a mobile device.
2. Select the account and address. Identify the Google Workspace account and the address that will appear as the sender. Configure an alternate Send mail as address on a computer before testing it.
3. Select the message paths. Decide separately whether the signature should appear in new emails and in replies or forwards.
4. Verify the selected combination. Test the actual client, account, sender address, and message type rather than relying on a different configuration path.

This creates a client-and-sender plan instead of treating Gmail signatures as one universal setting. The computer branch creates and assigns the web signature. The Gmail app branch uses its account-specific Mobile Signature setting, while a missing app-specific signature can cause new app messages to use the computer-created signature. For Google Workspace Business and Enterprise plans, Android installation is handled server-side, so check that deployment separately from the app setting.

Use the web editor and defaults for the computer branch, the Mobile Signature setting for a mobile-app branch, and the Send mail as settings for an alternate address. Then verify each combination that the Google Workspace rollout will use.

Create the web signature template

For Gmail on a computer, open Settings > See all settings > General > Signature and click Create new.

Create the signature in this order:

1. Enter a name and click Create. The name identifies the signature template; it is not the signature text.
2. Add the signature text in the editor.
3. Optionally use Gmail’s format bar for text colors, links, and images.
4. Click Save Changes at the bottom of the settings page.

Keep the template name separate from the text that will appear in an email. After saving the web signature, set the defaults for new messages and replies or forwards; creating the template does not by itself specify both message paths.

Assign web defaults by message type

After saving the web template, choose its default separately for new emails and for replies or forwards.

1. In the Signature section, choose the template for new emails if it should be inserted there.
2. Choose the template for replies and forwards if it should be inserted in those messages.
3. Select No signature for either field when that message path should not insert one. Gmail allows No signature for both FOR NEW EMAILS USE and ON REPLY/FORWARD USE.
4. Click Save Changes after setting the defaults.

The decision is now explicit for each web message path: a new email can use one template, a reply or forward can use another, or either path can remain unset. Open a new message and a reply or forward on the web to verify the choices before checking another client or sender address.

Configure an alternate Gmail sending address

If you will send from an alternate address, configure that identity before testing the signature. On a computer, go to Settings > See all settings > Accounts and import or Accounts, then choose Add another email address under Send mail as.

Complete the address setup as Gmail requests:

1. Enter your name and the address you want to send from.
2. Click Next Step, then Send verification.
3. For a school or work account, enter the SMTP server and that account’s username and password when requested.
4. Finish the verification or account steps before testing the signature.

Starting in January 2027, Gmail will no longer support Send as for third-party email addresses such as addresses ending in @yahoo.com or @outlook.com; this change does not affect Google Workspace aliases or other Gmail addresses you own.

After the address is ready, select that exact sender in a new message and check the signature. Repeat the check in a reply or forward when that message path uses the alternate address.

Choose the mobile app or Android deployment path

Choose the mobile path that matches how the message will be sent. Configure the Gmail app separately from the web defaults. In the Gmail app, open Menu > Settings, choose the business email account identified as the Google Workspace account, and select Mobile Signature.

1. Open Menu, then Settings.
2. Select the intended Google Workspace account.
3. Open Mobile Signature and enter the text for messages sent from that app.
4. If multiple accounts are present in the Gmail app, change the setting separately for each account.
5. Send a test message from the app.

A signature created in the Gmail app appears only in emails sent from the Gmail app. If you do not create one in the app, new messages use the signature created on your computer. Use either an app-specific signature or the computer-created signature for new app messages, then verify which result the account produces.

For Google Workspace Business and Enterprise plans, Android installation is handled server-side. Keep that deployment path separate from the Gmail app’s Mobile Signature setting, and test an Android message with the intended account and sender address after the deployment is ready.

Verify new messages, replies, forwards, and sender addresses

A Gmail signature verification check should cover every message path and sending identity you intend to use. Run the checks after saving the web settings, after changing a mobile setting, and after adding an alternate address.

Use this short checklist:

• Web, new message: Open a new message in Gmail on the web. Confirm the intended sender address, signature text, links, images, spacing, and placement.
• Web, reply: Reply to an existing message and check whether the selected reply default appears. Gmail lets you set a default for replies separately from new emails.
• Web, forward: Forward a message and check the signature position and surrounding quoted content. If the path should not include a signature, confirm that the relevant default is No signature.
• Alternate sender: Select each configured Send mail as address in a new message and confirm that the signature matches the identity. Gmail’s address setup is performed under Accounts and import or Accounts, in the Send mail as section.
• iOS app: Create a new message from the intended Google Workspace account in the Gmail app and inspect the mobile signature. Repeat for each account used in the app. ()
• Android app: Repeat the new-message test on Android. If an administrator-controlled server-side installation is part of the rollout, test the result after that deployment path is active.
• Reply and forward on mobile: Check both message types when your mobile workflow requires them. Do not infer their output from the new-message test.

Record the result by surface, account, message type, and sender address. A compact record can use four columns: surface, account, message type, and observed signature. Mark the exact path that passed or failed instead of recording only that “Gmail works.”

A failed test identifies a path to investigate. It does not, by itself, identify whether the cause is the selected default, the account, the sending identity, the app setting, or the signature content.

Resolve image and stale-signature problems by the affected message path

Gmail image and stale-signature symptoms need to be investigated through the message path that produced them. Start with the exact client, account, sender address, and message type instead of changing every signature setting at once.

When a mobile image fails

A Gmail Community user reported copying a JPEG or PNG image into Gmail mobile signature settings, saving it, and seeing the text in the sent signature while the image appeared as “<inline image>.” If you see that symptom, capture the device, Gmail app account, image insertion method, and sent-message result. Then test a text-only signature from the same account and app. Add the image again only after the text-only path passes. This isolates the image path from the account and message path.

When an old signature remains in replies

A Gmail Community user reported that an old signature still appeared in some, but not all, replies after the signature was changed. () Treat that symptom as message-specific. Compare a reply that shows the old text with a new reply from the same account, then check the reply or forward default in Gmail Signature settings. If the affected path should contain no signature, Gmail allows No signature for ON REPLY/FORWARD USE.

Use a controlled repair sequence:

1. Save the intended signature and defaults.
2. Open a fresh message or reply that reproduces the issue.
3. Compare the account and sender address with a passing test.
4. Change only the setting that matches the affected path.
5. Send another test and retain both results.

A symptom that appears only in replies should not lead you to rewrite the new-message signature. A symptom that appears only with an image should not lead you to change the sending identity first. Match the repair to the failed path.

Verify Gmail signature behavior by client, account, sender, and message

Gmail signature creation is ready when the client, Google Workspace account, sending identity, defaults, and test messages line up. Check the affected combination in a new message, a reply, or a forward, and compare the configured default with the signature that actually appears. Then test the exact message paths you plan to use, including new messages, replies, forwards, alternate senders, iOS, and Android.

The next step should follow the failed or missing path rather than repeat the entire setup. A web-only issue belongs in Gmail’s web settings; a mobile-only issue belongs in the relevant app account; an alternate-sender issue belongs in Send mail as; and an image or stale-reply issue belongs in the affected message path. Individual suitability for an organization’s account structure and deployment plan should be decided by a qualified administrator or professional.

Once those checks are complete, use the selected Gmail surface and sending identity to create the signature and run the verification checklist before relying on it for routine messages.

Which Gmail signature path should an administrator use for each client and address?

What should a Google Workspace Gmail signature include?

Start with the sender’s name, role, organization, and a way to contact them. Add links, colors, or images only when they support the message and display correctly on the Gmail surfaces your users rely on. A clear text-first version is easier to test before adding formatting.

Can I use different Gmail signatures for new emails and replies?

Yes. Gmail provides separate defaults for new emails and replies or forwards. Choose the appropriate template for each message type, or select No signature for either path, then save the settings and test both a new message and a reply or forward.

How do Gmail signatures work with aliases and shared mailboxes?

Prepare an alias or other sending address under Gmail’s Send mail as settings, verify it, and test the signature with that exact sender selected. Use the supported administrative arrangement for the mailbox and verify the resulting sender path separately.

Why might a Gmail signature appear on the web but not in the Gmail app?

Web and app signatures use different settings. A signature created in the Gmail app applies to messages sent from that app, and the setting must be checked for the specific account. If no app signature is created, new app messages use the computer-created signature described by Gmail’s instructions. Test the affected account and message surface instead of relying on a web-only check.