Why Is My Gmail Signature Not Showing on Mobile? A Google Workspace Troubleshooting Guide

Start a message-path trace

The most useful first question is where the signature disappears in the message path: while composing, in the sent copy, or only in the recipient's view. Record whether the message was composed in Gmail on the web, on an iPhone or iPad, or on Android, then record the account, alias, or send-as identity selected in that compose window. This trace keeps a desktop result, a mobile compose result, and a recipient view from being treated as the same test.

The sending identity determines which account or alias must contain the relevant signature. Gmail can send from another Gmail address, a work, school, or business domain or alias, and some non-Gmail addresses. Check the From identity in the affected compose window before editing settings.

Use this baseline before changing anything:

1. Record whether the failed message was composed on Gmail web, iOS, or Android.
2. Record the Google Workspace account shown as the sender.
3. Record whether the sender is the primary address, an alias, or another send-as identity.
4. Open a new message on that same surface and note whether the signature is absent immediately or appears only after sending.

The baseline keeps a browser setting from being mistaken for a mobile fix. It also gives you a precise account and surface to retest after every change.

Find where the signature disappears

The difference between compose-time insertion and message viewing determines the next check. A signature inserted while composing in desktop Gmail is already embedded in the sent email, so it displays in the recipient's message regardless of the recipient's email app. A mobile display problem therefore does not necessarily mean the sender's signature was absent.

The sent message can contain a signature below the visible message body. Gmail separates the signature from the body with two dashes, so inspect the area beneath the body before concluding that the signature was not inserted. Compare the sent copy with the recipient view as well; the recipient's phone is not the same test as the sender's mobile compose screen.

Run two separate checks:

• Compose check: Open a new message on the affected device and inspect the message before sending.
• Sent-message check: Send a test to an account you can inspect, then look below the message body and in the recipient view.

A signature that appears in the sent message but not where you expected during composition points to a viewing or placement question. A signature missing from both the compose window and the sent message keeps the account, surface, setting, or deployment path open.

Repair Gmail web settings without treating them as mobile settings

Gmail web settings control the signature inserted by browser Gmail. On a computer, open Gmail, select Settings, choose See all settings, and find the Signature section. Add or edit the signature text there; Gmail also permits optional image or text styling. Select Save Changes when the web configuration is complete.

The Gmail web signature section has separate choices for new messages and replies or forwards. Make sure No Signature is not selected, assign the intended signature to the message types that need it, and save the change. Gmail web can also let you choose a different signature for an individual email, so inspect that message-level choice when a default appears to be missing.

The browser test must stay on the browser surface. After saving, compose a new message in browser Gmail from the intended account and inspect the new draft. A successful browser result confirms what browser Gmail inserted; it does not confirm what Gmail on iOS or Android will insert. If the original failure occurred on a phone, continue with the mobile path for that device instead of treating the browser result as the final acceptance test.

Configure the separate iPhone or iPad mobile signature

The Gmail app on an iPhone or iPad uses a separate Mobile Signature setting. A desktop signature can therefore look correct in browser Gmail while the iOS compose window remains empty. Make the change on the affected iPhone or iPad and keep the account identity the same as the identity recorded in the baseline.

Use the iOS Gmail app to configure the mobile signature:

1. Open the Gmail app on the iPhone or iPad.
2. Tap Menu, then tap Settings.
3. Under Compose and Reply, tap Signature settings.
4. Turn on Mobile Signature.
5. Add or edit the mobile signature.
6. Tap Back to save the change.

The setting must be changed in the mobile app, not only in Gmail web. Keep the text appropriate for the mobile message you are testing.

The iOS acceptance test is a new message from the same account on the same iPhone or iPad. Close the settings path, open a fresh compose window, and check whether the mobile signature appears before sending. If the test succeeds, send a message and inspect the result separately; if it fails, return to the sending identity and confirm that the setting was changed for the affected account.

Test Android as its own configuration path

The Gmail Android path requires its own mobile test. A mobile signature has to be created separately in the device's Gmail settings, and a browser draft does not show what the Android compose screen inserted. If Gmail provides a Mobile Signature setting for the affected account, open the Gmail app, open its settings, and select Mobile Signature before testing a new Android message.

A similar Android signature can be created by copying the signature from an email sent from a computer and pasting it into the Gmail Mobile Signature setting. Android does not support text formats such as fonts, color, or boldness in the copied mobile signature, so a formatting difference does not by itself show that the signature failed to insert. Compare the actual text and placement first.

Test the Android change with a new message from the same account on the same Android device. Do not use a browser draft from a different surface as the Android acceptance test. Check the compose window before sending, then inspect the sent message for the signature. If Android still produces no signature while browser Gmail does, keep the two results separate and move to the deployment check rather than repeatedly editing the web setting.

Remove local app and browser causes before changing deployment

The Gmail signature setting must be enabled for the account and message type being tested. A missing signature can result when the setting is not enabled or when No sign-off is selected as the default. On Gmail web, confirm the selected defaults for new messages and replies or forwards; on mobile, confirm the separate mobile setting for the affected account and device.

Browser settings or extensions can interfere with Gmail and prevent a signature from appearing. Use a private browsing window to test a browser-only symptom after confirming the intended account. This check applies to the browser surface; it does not replace the same-device compose test for iOS or Android.

A signature configured on desktop may not sync automatically to a mobile device. Treat the desktop-to-mobile difference as a surface distinction until a mobile test proves otherwise. One published estimate puts the share of all messages accessed on mobile devices at 42%; that figure describes all messages in the estimate, not your organization's users, so use the same-device result for your operational decision.

Retest after each local correction:

1. Keep the account and sending identity unchanged.
2. Open a new message on the surface that failed.
3. Check the compose window before sending.
4. Send the message and inspect the sent copy below the body.
5. Record whether the result changed.

A browser-only failure can justify the private browsing check. A mobile-only failure requires the affected mobile app and device to remain in the test.

Recognize when Android requires a deployment decision

Gmail for Android can present a deployment limitation rather than a user-setting error. Some mobile apps do not allow external tools to modify the signature in the compose window, and Scribe's documentation identifies Gmail for Android as one example. In that situation, repeated client-side changes cannot make an external tool inject a signature into the Android compose window.

Client-side installation depends on the email app. Scribe's client-side installation works in the Gmail iOS app, but not in Gmail for Android. Server-side installation adds the signature after the message is sent, so it works from any app. The two methods act at different points in the message path, which is why an Android deployment decision cannot be settled by checking only a browser draft.

Gmail for Android requires server-side installation on Google Workspace Business and Enterprise plans. The Android server-side route is an advanced setup requiring IT. If your organization needs a signature added to messages sent from Gmail on Android, assess that route against the organization's plan and deployment method instead of treating the missing client-side insertion as an ordinary local setting.

Our Google Workspace integration installs signatures in Gmail on the web and iOS on Free, Business, and Enterprise plans. For Gmail on Android, our installation requires server-side installation on Business and Enterprise plans. Apply those conditions only to Scribe's Google Workspace integration; they do not describe every Gmail configuration or every third-party deployment.

Interpret the message-path trace

Read the comparison from the earliest checkpoint that fails. If the signature is present while composing on one surface but absent while composing on another, the surface-specific path is the unresolved part of the trace. If it is present in the sent copy but not in the compose window, distinguish a post-send insertion or a viewing issue from a compose-time insertion failure. If it is absent from both, keep the recorded account, identity, setting, and deployment conditions in the next investigation.

Use this comparison to keep the acceptance tests separate:

A browser result cannot establish the Android result. A sent message can show whether a signature was added after sending, but it cannot replace the compose test when the issue concerns what the mobile app inserts.

Choose the next action from the pattern:

• Only browser Gmail fails: repeat the web account, default, and private browsing checks.
• Only iOS fails: repeat the iOS account and Mobile Signature checks on the affected device.
• Only Android fails: check whether the organization is relying on client-side injection, then assess server-side installation and its plan boundary.
• Every surface fails: return to the sending identity and signature content before changing deployment.

Run the next test on the same account and surface that produced the failure.

Seek professional evaluation when the test path cannot isolate the cause

The unresolved failure is ready for support when the intended account is selected, the relevant mobile or web setting is enabled, and a new same-device message still lacks the signature. Contact Google Workspace or Scribe support with the test record rather than describing the problem only as a missing mobile signature.

Give support a compact record:

• The affected Gmail account and the selected alias or send-as identity.
• The exact surface: Gmail web, iOS, or Android.
• Whether the signature was visible in the compose window.
• Whether the sent message contained the signature below the body.
• The result from each same-account, same-device test.
• The Google Workspace plan and the deployment method used for Android.

This record separates an account or setting issue from a surface or deployment issue and gives the next evaluator a reproducible path.

Ask for an implementation review when Android coverage conflicts with the organization's plan or when the deployment method depends on client-side injection in Gmail for Android. For Scribe's Google Workspace integration, the relevant Android route is server-side installation on Business and Enterprise plans. Keep the escalation focused on the failed surface, account identity, and deployment condition.

Preserve the verified message path

The verified result is a reproducible message-path trace: the signature appears at the point expected for the selected deployment method, remains in the sent copy, and is visible in the recipient view. If it is absent during composition but present after sending, interpret those results separately rather than treating the compose window as the only test. Preserve the recorded surface, account, identity, and checkpoint results when applying the confirmed configuration to affected users.

Before applying the path to more users, preserve the acceptance test: same account, same sending identity, same device type, new message, and sent-message inspection. If the test succeeds, apply the confirmed configuration to the affected users. If it fails, keep the deployment unchanged and seek a professional evaluation using the recorded surface and account results.

What should I check if Gmail mobile still omits the signature?

Why is my Gmail signature missing while I compose on mobile but visible after sending?

The signature may be inserted or displayed below the message body rather than where you expected. Check the compose window first, then inspect the sent message below the body, where Gmail separates the signature with two dashes. A signature embedded before sending should also appear in the recipient’s message.

Does a Gmail desktop signature automatically appear in the mobile app?

No. Gmail web, iOS, and Android use separate signature paths. Configure and test the signature on the same mobile device, app, account, and sending identity that produced the failure; a successful browser test does not confirm a mobile result.

Why is the signature missing when I send from a Gmail alias?

Check the From identity before changing settings. Retest with a new message from that same identity.

Can Scribe add a signature to Gmail on Android?

For Gmail on Android, Scribe’s installation requires server-side installation on Google Workspace Business or Enterprise plans. Android server-side installation is an advanced setup requiring IT. If the organization is using client-side injection, the missing signature may be an app limitation rather than a local Gmail setting.

How should I test whether a Gmail mobile signature fix worked?

After each change, compose a new message from the same account or alias on the same device and app that failed. Check the compose window before sending, then inspect the sent message and recipient view. Do not use a browser draft to confirm an Android result.