Nine times out of ten it's the install method. Copy for Outlook and Gmail; use the .htm file-swap for Apple Mail; install on desktop, not mobile. The rest is below.
The steps don't match my Outlook.
Microsoft ships two Windows Outlooks right now: Classic (the old Word-engine app, signatures live on the compose ribbon) and New Outlook (the WebView2 rewrite, signatures live under Settings → Accounts). Tell them apart by the top strip — Classic has the colored tabbed ribbon; New has a slim toolbar and a New Outlook toggle in the corner.
The Outlook guide has both paths side by side — pick your version there. Good news: your signature renders correctly in both; only the menu path differs.
I downloaded the file for Gmail and nothing happened.
Gmail has no file-install path, so the .htm download does nothing there. Gmail renders real HTML — you install by copying and pasting. Ignore the downloaded file, press Copy signature in the builder, and paste into Gmail's signature box.
Full steps: the Gmail guide.
My Apple Mail signature reverts after I set it.
Apple Mail rewrites its signature files on save, so it overwrites your edit unless you lock the file. After you swap the .htm contents into the .mailsignature file, select it, press ⌘ + I, and tick Locked before reopening Mail. That one checkbox is what makes it stick.
Full method: the Apple Mail file-lock step.
My logo or headshot isn't showing.
Usually the recipient's client is blocking remote images — a normal privacy default, not a Sigquill fault. Ask them to click “Display images”, or send a test to a second address of your own to confirm the image loads there. A text-only signature (no logo/headshot) sidesteps image-blocking entirely and always renders.
There's a big gap between the lines in Outlook.
That's Outlook adding paragraph spacing around a pasted signature — a classic Outlook behavior, and one Sigquill's nested-table layout is built to avoid. If you see it, the paste likely picked up an empty paragraph. Delete the blank line above or below the signature in the signature editor, or re-paste with the cursor at the very start of an empty signature box.
The font looks different from the preview.
Email clients don't load web fonts — that's a hard limit across the board, not a bug. Sigquill signatures are built on Arial-family fallback stacks chosen to look composed, not accidental, when a custom font can't load. What you're seeing is the intended fallback; it will look consistent to your recipients regardless of their system.
My signature is plain text on my phone.
Phone mail apps use plain-text signatures by design — a platform limitation, not something Sigquill can override. Install your rich signature on the desktop; it's carried on the mail you send from there. There's nothing broken to fix on mobile, and nothing to install. See the mobile note.
Not your issue? Email support@sigquill.com — we reply as soon as we can.