Share a routine in the KeyRoutines Library
5 min read · Updated
To share a routine, export it from KeyRoutines as a file, then upload it at keyroutines.com/library with a free account. A moderator reviews every upload before it goes public, and people who install it see exactly what it does first, with the routine switched off until they turn it on.
Before you start
You'll need:
- KeyRoutines with the routine you want to share, working the way you like
- a free account on this site, to upload
- optionally, up to four screenshots of your setup
Give the routine a clear name and label its steps ("Open Discord", "Side monitor layout"). The Library shows step labels in quotes, so good labels make your routine much easier to understand.
Export the routine
Export the routine from KeyRoutines. You get a .krroutine file; several routines exported together make one .krpack file. Exporting is built to make a routine safe to share and able to work on someone else's PC:
- Saved secrets are left out. If a step uses a password or token from your secrets vault, only its name goes in the file. Whoever installs it is asked for their own value.
- Your folders become general ones. A path inside your user folder is written so it points to the same place in theirs.
- Apps are named by what they are, not where you happened to install them, and monitors keep a hint about their role, such as your main or side monitor.
Upload it
Sign in and open Share a routine
Go to the Library, sign in, and choose to share a routine. Your routine is shown as made by your account's name, which you can change in your profile.
Add the file and the details
Choose your .krroutine or .krpack file, then fill in:
- Name: short and plain, like "ARC Raiders setup".
- What it's for: a sentence or two on what it does and who it's for.
- Category: Gaming, Streaming, Work or System.
- Screenshots (optional): up to four PNG, JPEG or WebP images, 1 MB each. Leave out names, chats and notifications.
- Notes for this version (optional): anything people should know, like which apps it expects.
Send it for review
Submit the form. The site checks the file straight away and tells you if something needs fixing. Then your upload waits for a moderator, usually for a few days.
What gets checked
Automatic checks, the moment you upload:
- the file must be a real KeyRoutines export that matches the routine format, and within size limits (5 MB)
- it must have a name and at least one step
- it must not hold a password, key or token. Keep those as saved secrets instead
- it must not contain folders from your own PC. Paths should start from your user folder in general form, which export does for you
A summary of what it does. The site reads the routine itself, not your description, and lists every app it opens, every website it calls, every file location it touches and every script it runs. Reviewers and visitors both see this.
A person reviews it. Nothing is public until a QaemDev moderator approves that exact version. Routines that run scripts, such as Run PowerShell, make web requests, such as HTTP request, or need administrator rights, such as Run as administrator, get a closer look.
What isn't allowed:
- anything that harms the person installing it, like deleting or encrypting their files, changing security settings, downloading and running programs they didn't ask for, or sending their data anywhere
- routines that play games, send input into games, or try to get around anti-cheat
- passwords, keys, tokens or personal information
- descriptions that hide what a routine does, spam, or someone else's work without permission
The full list is in the Library rules.
Your uploads and their status
Your uploads page shows each routine with its status:
| Status | Meaning |
|---|---|
| In review | Waiting for a moderator. Not public yet. |
| Public | Approved and listed in the Library. |
| Public · update in review | People see the approved version while your new one is reviewed. |
| Not approved | The moderator turned it down, with a reason you can read. |
| Unlisted by a moderator | Hidden from the Library. You can still see it. |
Updating with a new version
Every upload of a file is a new version, numbered v1, v2, v3 and so on. Upload the new file to your existing item and add a note under What's new. The new version is reviewed like the first, and until it's approved, the Library keeps showing the last approved one. If you upload again while a version is still waiting, the new file replaces the waiting one.
Changes to the name, description, category or screenshots of a public routine are reviewed too. The routine's page lists every approved version with its date and notes.
You keep ownership of what you share, and you can unlist it from your account at any time.
What people see when they install it
Your routine's page shows its summary, its permissions and its versions. When someone installs it, KeyRoutines opens and shows its own permission preview, one plain line per kind of thing the routine can do, such as "Launches: Discord" or "Deletes files in: Downloads (to the Recycle Bin)". Scripts and administrator rights stand out in red. The routine is then added switched off, and only runs once they turn it on.
That's why an honest name and description matter: anything your description leaves out, the preview will show anyway. See Install from the Library for the installer's side.