Guides for using a signature in PDF, Word, Google Docs, and Gmail
These pages pick up after the generator. Each guide handles one exact follow-up task so users can move from exported PNG to finished document or email without extra hunting.
- One guide, one task
- Transparent PNG first
- Direct tool CTA on every page
Need the signature image?
Open the generator before following the guides so you already have a transparent or white PNG ready to insert.
Open the generatorUse the signature where it matters next
Generate before you install
Complete the workflow, not just the asset
The generator solves the first job. The guides solve the second: actually placing the signature where the user needs it. That creates topical depth without bloating the tool pages above the fold.
Questions about the guides layer
Do I need a transparent PNG for every guide?
Transparent PNG is the default recommendation because it removes the white box problem in PDFs, Docs, Word, and Gmail. The white background fallback is there if a specific editor behaves better with it.
Why does the guides hub focus on four tasks?
These are the highest-value follow-up tasks for the MVP: PDF, Word, Google Docs, and Gmail. They give the generator clear downstream use cases without expanding into a full email-signature product yet.