A plain-English guide to creating, testing, and using snippets.
Snippet = the saved text block. Shortcut = what you type to trigger it. Command = a dynamic piece inside a snippet, like today's date or a form field. Template = a ready-made snippet you install from the library.
Create a folder from the left panel.
Create a snippet inside that folder.
Give it a short trigger, such as /thanks or /intro.
Write the text you want TextRhino to insert.
Use the Playground to type the trigger and test the result.
Click Save when the snippet works the way you want.
This is the name you see in the left panel. Use a clear name such as Support reply, Invoice reminder, or Meeting notes.
This is what you type to run the snippet. Shortcuts usually start with /, such as /reply. Keep them short, memorable, and unique.
This is the message TextRhino will insert. You can type normal text, format it, add lists, add links, and insert commands.
Save stores your latest name, shortcut, and snippet text. Saved snippets are what the extension and Playground use.
The Playground works like a safe practice area for the extension.
Type normal text, then type a snippet shortcut such as /reply.
If the snippet has no fields, it expands immediately. If it has fields, TextRhino opens a small form. Fill it in, review the output, then insert it.
Use the snippet list above the Playground to see which shortcuts are available.
Commands are special pieces of a snippet that change at the moment you use the snippet. They can ask for information, insert today's date, make a choice, calculate a value, or show optional text.
Use date and time commands when the snippet should always use today's date, the current time, or a future date.
What you put in the snippet
{time: YYYY-MM-DD}What the user sees
2026-08-21
Today's date in a simple format.
What you put in the snippet
{time: MMMM Do YYYY}What the user sees
August 21st 2026
A friendly full date.
What you put in the snippet
{time: YYYY-MM-DD; shift=1W}What the user sees
A date one week from today.
Follow-up dates and reminders.
Use text fields when you want TextRhino to ask for a name, company, ticket number, amount, or any one-line detail.
What you put in the snippet
Hi {formtext: name=customer; default=there},What the user sees
Hi Avery,
Personalized greetings.
What you put in the snippet
Ticket: {formtext: name=ticketNumber; default=#1234}What the user sees
Ticket: #9281
Support and operations notes.
Use paragraph fields when the answer may be longer than one line.
What you put in the snippet
{formparagraph: name=summary; default=Customer asked for an update.}What the user sees
A larger text box appears before insertion.
Call notes, summaries, feedback, and explanations.
Use menus when the user should choose from a fixed list instead of typing from scratch.
What you put in the snippet
{formmenu: Low, Normal, High, Urgent; name=priority}What the user sees
High
Priority, status, department, plan, or category.
Use toggles for optional text. If the toggle is on, the text appears. If it is off, the text is skipped.
What you put in the snippet
{formtoggle: name=includeApology; default=yes}Sorry for the delay.{endformtoggle}What the user sees
Sorry for the delay.
Optional apology, optional instructions, or optional legal text.
Use formulas when the snippet needs a simple calculation.
What you put in the snippet
Total: {=price * quantity}What the user sees
Total: 40
Quick totals, quantities, rates, or simple math.
Use if / else when the final text should change based on a field value.
What you put in the snippet
{if: priority = "Urgent"}We will prioritize this today.{else}We will review this in the normal queue.{endif}What the user sees
One of the two messages is inserted.
Different replies for different statuses.
/replyHi {formtext: name=customer; default=there},
Thanks for reaching out. I reviewed your {formmenu: Bug, Billing, Access; name=issueType} request.
Next update: {formdate: YYYY-MM-DD; name=nextUpdate}
{formparagraph: name=nextStep; default=I will check this and follow up shortly.}/invoiceHi {formtext: name=customer; default=there},
Invoice {formtext: name=invoiceNumber; default=INV-1001} is due on {formdate: YYYY-MM-DD; name=dueDate}.
Balance: ${formtext: name=balance; default=250}
{if: balance > 1000}Please contact us if you need payment plan options.{else}You can pay using the normal payment link.{endif}/notesMeeting date: {time: MMMM Do YYYY}
Attendees: {formtext: name=attendees; default=Team}
Summary: {formparagraph: name=summary; default=Main discussion points.}
{formtoggle: name=includeActions; default=yes}Action items: {formparagraph: name=actions; default=Add action items here.}{endformtoggle}Use clear field names. For example, use customer instead of x.
Reuse the same field name when you want the same answer to appear more than once.
Start with simple snippets first. Add commands only when you need changing text.
Test every snippet in the Playground before using it in real work.
Keep shortcuts unique. If two snippets use the same shortcut, TextRhino cannot know which one you mean.
Use templates when you want a ready-made starting point.
Still stuck? Contact support →