Semnătură E-mail
Creează o Semnătură E-mail Profesională în Câteva Secunde
Creează o semnătură e-mail completă cu nume, funcție, logo și contact. Copiază HTML și lipește în Gmail sau Outlook.
How to add your signature to Gmail, Outlook or Apple Mail
Pasting a signature into an email client is where most of them go wrong, because the clients do not agree
on what HTML they will accept. Gmail rewrites what you paste into it. Desktop Outlook renders it with
Microsoft Word rather than a browser. Apple Mail renders it with the same engine as Safari. The steps below
are for each client specifically, followed by the things that actually break in that client.
1 Gmail (on the web)
Gmail's own sanitiser, on top of your browser engine
- Click the gear icon at the top right and choose See all settings.
- Scroll down to the Signature section and click Create new. Give it a name such as “Work”.
- Paste with Ctrl+V (Windows) or Cmd+V (Mac). Do not use Ctrl+Shift+V — that pastes as plain text and throws the formatting away.
- Set the dropdowns under Signature defaults for new messages and for replies, so it appears automatically.
- Scroll to the very bottom and click Save changes.
What goes wrong here
- Gmail strips
<style> blocks and ignores CSS classes when it renders a signature, so every style has to be inline. The HTML this tool produces is inline for exactly that reason. - Gmail will not load an image embedded as a
data: URL. If your signature image comes through blank, paste the text first and then add the image with Gmail's own Insert image button — Gmail then hosts the file itself and it loads for everyone. - The Gmail mobile app has no signature editor. Whatever you set on the web is what your phone sends.
2 Outlook for Windows (classic)
Microsoft Word's HTML engine
- Open File → Options → Mail → Signatures…
- Click New, give the signature a name, and paste with Ctrl+V.
- Under Choose default signature, set it for both New messages and Replies/forwards.
- Click OK, then open a new message to confirm it appears.
What goes wrong here
- This is the client that breaks the most signatures, because it does not use a browser engine. It has no support for
float, unreliable padding on some elements, and no data: images. Table-based markup with inline styles — what this builder produces — is the only layout that survives it. - Outlook blocks remote images until the recipient chooses to download them. If your signature is mostly one large image, it can arrive looking empty. Keep the contact details as real text and let the image be an accent.
- If the editor will not accept your formatting, close Outlook. Signatures are stored as
.htm files with an asset folder under %APPDATA%\Microsoft\Signatures, and you can place the HTML there directly.
3 Outlook on the web / new Outlook
Your browser engine — far more forgiving
- Click the gear icon, then Mail → Compose and reply.
- Paste your signature into the Email signature box.
- Tick the boxes to apply it to new messages and to replies and forwards.
- Click Save.
What goes wrong here
- Outlook on the web renders in the browser, so it is much closer to the preview you see above than desktop Outlook is. A signature that looks right here and wrong in desktop Outlook is normal, and the desktop behaviour is the one to design for.
4 Apple Mail (macOS)
WebKit — the same engine as Safari
- Open Mail → Settings… (older versions: Preferences) and go to Signatures.
- Select the account on the left, click +, and name the signature.
- Paste into the right-hand pane.
- Drag the signature onto the account name so it is the one used, and untick Always match my default message font if macOS is overriding your formatting.
What goes wrong here
- Apple Mail renders closer to a browser than any other major client, so what you see in the preview is roughly what recipients on Apple devices get.
- Signatures sync between your Macs through iCloud, but they do not sync to iPhone or iPad. Those have their own plain-text field under Settings → Mail → Signature, with no rich editor and no reliable image support.
Why your signature looks wrong in one client and fine in another
There is no single way an email signature renders, because there is no single engine rendering it. A
signature is HTML, and email clients pick and choose how much of the HTML specification they honour. The
table below is the short version of what each one does to your signature.
How each major email client renders an HTML signature | Client | Rendering engine | What it does to your signature |
| Gmail (web and apps) | Own sanitiser over your browser engine | Removes <style> blocks and class attributes, drops data: images, clips the message past 102 KB. |
| Outlook for Windows | Microsoft Word | Ignores much of CSS, needs tables for layout, no data: images, blocks remote images until allowed. |
| Outlook on the web | Your browser engine | The most forgiving Outlook. Still drops data: images. |
| Apple Mail | WebKit | Closest to a browser preview. Closest to the preview shown above. |
| Yahoo Mail, AOL | Own sanitiser over your browser engine | Behaves much like Gmail — inline styles only, no data: images. |
Three of these behaviours are worth knowing about before you design anything, because they cause almost
every complaint about a broken signature.
Transparent backgrounds and dark mode
A signature exported with a transparent background is the correct choice for a PDF and the risky choice for
email. On a dark-mode client the message is drawn on a dark surface, and a transparent PNG keeps whatever
ink you drew it in. Dark ink on a dark background is invisible, and the recipient sees an empty gap where
your signature should be. Some clients invert images to compensate and some do not, and that behaviour has
changed from version to version, so it is not something to rely on. For email, either export the signature
with a white or very light background so it stays legible on any theme, or leave the image out and let
styled text carry the signature instead. If you are making the signature on this site, the
signature generator lets you choose the background before you
download.
The 102 KB limit in Gmail
Gmail truncates any message whose HTML goes past roughly 102 KB and replaces everything after that point
with a single “…”. The recipient then sees a clipped email with no indication that anything is missing. A
base64-encoded image is about a third larger than the file it came from, so a 60 KB signature image can push
an otherwise short reply over the limit. That is why the builder above reports the size of the HTML it
produces — if it warns you, use a smaller image rather than discovering the problem in a sent message.
Images that never load
Outlook blocks remote images by default until the recipient allows them, and both Gmail and Outlook refuse
to load an image that is embedded directly in the HTML as a data: URL. A signature built as one
large graphic therefore arrives broken for a meaningful share of recipients. Keeping your name and contact
details as real text, with the image as an accent, means the signature still communicates even when it
cannot load a single image.
What a professional email signature should contain
A signature is read in about two seconds, usually on a phone, usually by someone deciding whether to reply.
Everything in it competes for that attention, so the test for every line is whether it helps the recipient
reach you or remember you.
- Your name, as you actually want to be addressed.
- Your role and company — the context that tells the reader why you are writing.
- One primary way to reach you. Pick the channel you genuinely answer. A phone number you
never pick up is worse than no phone number.
- One link to the place that matters — your site, your calendar, your LinkedIn profile. Not all three.
- An optional logo, only if it is still legible at 60 to 100 pixels wide. Most logos are not.
Four lines covers that. If yours is longer than the emails you send, it is working against you — see the
fuller email signature best practices guide for what to
cut and in what order.
How big should an email signature be?
Size is where signatures quietly cause problems, so here are concrete numbers rather than advice.
- Signature graphic: 200 to 300 pixels wide. Larger than that and it dominates the message on a phone.
- Logo: 60 to 100 pixels wide, and check it at that size before you commit to it.
- Total HTML: stay under 102 KB, which is Gmail's clipping point. The builder shows you the figure.
- Line width: keep the signature block under about 600 pixels so it does not wrap awkwardly on mobile.
- Text size: 12 to 14 pixels. Below 11 pixels is unreadable on a phone at default zoom.
What to leave out
- Long confidentiality footers. There is no general legal duty in the United States or the
European Union to attach a confidentiality notice to every email, and six lines of small print bury the
contact details they sit next to. Where a regulator or a client contract does require one, keep it to a
single short line.
- Tracking pixels. They are a data-protection problem, a spam-scoring problem, and most
clients strip or proxy them anyway.
- Every social network you have ever joined. Three icons compete; five become noise.
- Oversized images. A heavy image is one of the more common reasons a reply lands in spam,
because an image-led message with little text scores badly with filters.
- Animated GIFs, quotations and taglines. Most corporate clients show the first frame of an
animation, if anything, and the rest is decoration the reader scrolls past.
Related guides