Transforms

A Transform reshapes a value just before SimpleFill inserts it. It can capitalize a name, turn a page title into a URL slug, move a date forward a week, or format it exactly how you like. Transforms work on Smart Fields, Fields, and plain-text snippets.

How to use a Transform

Add a | (a pipe) and the Transform’s name after a value.

Typed on a page, after a shortcut:

;title|uppercase

As soon as you type the |, the shortcut dropdown lists the Transforms that fit that value, each with what it does. Pick one with the arrow keys, and Enter writes its full name for you. Press Enter without picking one to insert the value as it is.

In a snippet, inside the curly braces:

{{page.title | uppercase}}

On a pill in a rich snippet: click the pill, then Add transform under Transforms.

Chain them

Add as many as you like. They run left to right, each one working on the result of the one before:

{{page.title | slugify | truncate(30)}}

Getting Started with SimpleFill: Fill Any Form becomes getting-started-with-simplefil, exactly 30 characters.

Give them details

Some Transforms need a detail, like how many days to add. Put it in parentheses. Put text in quotes, and separate several details with commas:

{{date | addDays(7)}}
{{page.title | replaceAll("-", "/")}}
{{page.title | truncate(40)}}

When typing on a page, the last ) can be left off: ;date|addDays(7 works too. Until the details are complete, with no quote left open or comma with nothing after it, SimpleFill inserts nothing and says what’s missing, so a half-typed Transform never fills in the wrong thing.

All Transforms

You can browse them all in the dashboard under Transforms, each with an example.

Text

Format dates

The patterns formatDate understands:

Month and day names follow your browser’s language.

A few things worth knowing about dates:

• A date stays a date. After addDays, addMonths, startOfMonth, and the like, {{date | addDays(7)}} is still written in your date format, just a week later. Use formatDate when you want a different look.
• The value keeps its shape. A date stays a date, a time stays a time (23:45 + 30 minutes is 00:15), and a date and time keeps its time.
• Days and longer need a date; hours and minutes need a time. ;time|addDays(1) and ;date|addHours(2) don’t run, rather than quietly dropping part of the value.
• Dates are read as SimpleFill writes them: 2026-10-23, 09:45, or 2026-10-23T09:45, with or without a time zone like Z or +05:30. Text such as Oct 23, 2026 isn’t read as a date, so nothing that merely looks like one, like Ticket 42, gets turned into one.

Numbers

Numbers are read using the Number format in Settings, so 1.234,56 works if that’s how you write numbers.

Encoding

When something doesn’t fit

Each Transform works on certain kinds of values. You can’t uppercase a number, for example. If a Transform can’t run, SimpleFill inserts the value as it was before that step and tells you what went wrong, so you never lose your text.

A Transform that’s still being typed is different. If its name could mean several, or its details are missing or wrong, a typed shortcut inserts nothing yet, and the dropdown shows what’s needed.

Examples

A search link. https://www.google.com/search?q={{clipboard | urlEncode}} turns whatever you copied into a ready-made search link.

A due date in words. Due {{date | addDays(14) | formatDate("dddd, D MMMM")}} gives Due Friday, 6 November.

A clean branch name. ;title|slugify on a GitHub issue gives a branch name like fix-login-redirect-loop.

Names that look right. Put titleCase on a customer-name Field, and it doesn’t matter how you type it.