How to Copy an Email Signature Without Losing Formatting

Updated June 2026

You built a signature, copied it, pasted it into Gmail or Outlook settings — and got a wall of <table> and <td> code. Or the paste “worked” but the columns collapsed, the photo vanished, and everything turned Times New Roman.

Both failures come from the same misunderstanding: what the clipboard is actually carrying. Here’s how copy-paste really works for signatures, and the two methods that don’t break.

Rich text vs. HTML source: the root cause

The signature box in Gmail settings, new Outlook, and Outlook on the web is a rich-text editor — the same kind of editing surface as the email compose window. It expects a rendered signature on the clipboard: formatted text, links, images, table structure. In clipboard terms, that’s the text/html flavor.

It does not expect HTML source code. If you copy raw markup out of a code editor, a .html file opened in Notepad, or a generator’s “view code” box, the clipboard carries plain text that merely looks like HTML. The signature editor faithfully pastes it as literal characters — which is why you see <table border="0"... printed in your signature instead of an actual table.

So the rule is simple:

Method 1: Use the generator’s copy button

The most reliable path. A proper copy button uses the browser’s clipboard API to write the complete signature HTML to the clipboard as text/html — the whole table, every inline style, every image reference, nothing missing. When you paste into Gmail or Outlook settings with a normal Ctrl+V (Cmd+V on Mac), the editor receives exactly the markup the signature was built with.

This is how the copy button in the OnceSig editor works: one click writes the rendered signature to your clipboard, and the markup underneath is already table-based with inline styles only, so it survives both Gmail and Outlook’s Word renderer. The exact paste steps for each client are in the install guides — see Gmail and new Outlook.

Method 2: Render in a browser, select all, copy

If you have a signature as an HTML file (from a designer, an old backup, anywhere):

1. Open the .html file in Chrome, Edge, or Firefox — double-clicking it usually does this. You should see the signature, not code.
2. Click once anywhere inside the rendered signature.
3. Press Ctrl+A (Cmd+A) to select all, then Ctrl+C to copy.
4. Paste into the signature box with a plain Ctrl+V.

The select-all step matters. A click-and-drag selection across a rendered page often starts or ends mid-table, so the browser copies a fragment without the outer wrapper — and the paste arrives with its layout half gone. Ctrl+A grabs the complete document, wrapper included.

Ctrl+Shift+V: never, for signatures

Ctrl+Shift+V is “paste without formatting.” It exists to deliberately discard the text/html clipboard flavor and paste only the plain-text fallback. That’s useful when pasting quotes into a document; for a signature it destroys the very thing you’re trying to transfer — colors, fonts, links, the table layout, everything. If your signature pasted as unstyled plain text, this shortcut (or a “paste as plain text” right-click option) is almost always why.

The same applies to a detour through Word or Google Docs. Both rewrite pasted HTML into their own bloated markup, which can push a signature past Gmail’s 10,000-character limit and breaks the careful spacing rules signatures need. Go straight from the rendered source to the signature box.

When pasting isn’t the answer: classic Outlook

Classic Outlook for Windows renders email with Word’s engine, and its signature editor mangles pasted HTML more often than any other client. The robust route skips pasting entirely: classic Outlook reads signatures as .htm files from %APPDATA%\Microsoft\Signatures, and a file you place there is used exactly as written — no paste step to corrupt it.

OnceSig exports this .htm file directly, alongside the rich-text copy path. The classic Outlook guide walks through the folder install step by step.

Why the source markup still matters

A clean copy only preserves what’s there. If the underlying HTML uses <div> layouts, <p> tags, or external stylesheets, it will paste fine and still fall apart in Outlook — Word’s renderer ignores most CSS, doubles <p> spacing, and stretches line heights unless mso-line-height-rule:exactly is set. Every OnceSig template is built against those constraints from the start: tables, inline styles, explicit image dimensions, no <p> tags. The full editor is free to try in your browser (your data stays in localStorage, never on a server), and a one-time license — no subscription — unlocks clean export.