A fork is your own editable copy of a recipe. The author's updates don't automatically change it, which is the point of forking, but it also means you miss their bug fixes and improvements.
With forked syncing, author changes trigger a notice on your plugin's settings page. You can see what changes were made, decide which ones you want to take, and all the while your own edits stay in place.
Prerequisites
A fork of a recipe. An install already follows the author and never needs this. See Installing community recipes for the difference.
The recipe is still published or unlisted.
Step 1 - Spot the change
Go to Plugins, then Private Plugin, and open your fork. When the author has changed the recipe since you copied it, the info box on the settings page says The recipe has changed since you copied it. Click See what changed.
When nothing changed, the line isn't there.
Step 2 - Read what changed
The Recipe changes page lists each file the author changed: Full, Half horizontal, Half vertical, Quadrant, Shared markup and Transform script, plus the canvas for a Tidbyt or Vestaboard recipe.
Each file shows What the recipe changed since you copied it, with removed lines in red and added lines in green. If you edited the file too, What you changed sits below it, folded closed. A line under the file name tells you where you stand, for example "You changed this file too. Taking the recipe's changes keeps yours."
Step 3 - Take the changes
Click Take these changes on a file. TRMNL puts the author's changes and yours together and saves the file. When two or more files can be taken, Take all changes at the top does them in one click.
Each file you take drops off the list. When none are left, the page says "Your copy has every change from the recipe."
Step 4 - You're done!
Your fork now has the author's changes and keeps yours. Every take saves a snapshot in the markup editor, so you can step back if you don't like the result.
When you both changed the same lines
This is the one case the page can't settle for you. If you and the author edited the same lines, TRMNL can't tell whose version should win, so it doesn't guess. The file says "You and the recipe changed the same lines, so the two cannot be put together", nothing is saved, and What you changed opens so you can compare the two.
You have two options:
Use the recipe's version. The file becomes exactly the author's, and your edits to that file are gone. Copy anything you want to keep from What you changed first, then add it back in the markup editor.
Leave it. Your fork keeps working as it is, and the notice stays on the settings page until you decide.
Undo a change
Open your fork, click Edit Markup and go to the tab of the file you changed. In the bar at the bottom of the editor, open Snapshots, pick the one from before you took the change, click Load into editor, then save.
Forks made before November 20, 2026
TRMNL began recording copied forks on November 20, 2026. An older fork has no such record, so TRMNL can't tell the author's changes apart from yours.
The settings page says Your copy is different from the recipe instead, and the page compares your file with the recipe's as they are now, which means your own edits show up as differences too. A file shows only if the author saved it after you forked. The only option is Use the recipe's version.
Once you use it on a file, TRMNL records that copy, and the author's later changes to that file can be taken the normal way.
For recipe authors
When you save a change to a recipe, installs pick it up on their next refresh, and every fork's settings page shows that the recipe changed. Forks take it when they choose, so a fix reaches them without you contacting anyone.
Troubleshooting
The author changed a setting, but my fork shows nothing.
Only the code files are compared: the four layouts, Shared markup, Transform script and the Tidbyt or Vestaboard canvas. Form fields, polling URLs and other settings stay as you set them in your fork, so copy those over by hand.
My installed recipe has no notice.
Installs follow the author and update on their own. The notice is for forks only.
The notice went away before I took the changes.
The author unpublished the recipe, or changed the file back to what you copied. Your fork keeps working either way.
Take all changes is missing.
It shows only when two or more files can be taken. Take the others one at a time, or use the recipe's version.
A file only offers Use the recipe's version.
Either you and the author changed the same lines, or your fork is older than November 20, 2026. The line under the file name tells you which.


