
Add a Slack Emoji Alias Without Uploading Another Image
Give one Slack emoji a short code and a descriptive name. Follow the alias controls, test both names, and keep a clear alias register.
A Slack emoji alias gives an existing emoji another code. It is useful when people remember different names for the same reaction: one person types a short code, while another searches for a descriptive phrase. You do not need to upload a second copy of the picture.
For a team checkmark, use a clear main name such as review_complete and a short alias such as rvdone. Both names should mean the same thing. An alias is a naming convenience, not a new image or a separate approval system.
One image, two names

Suggested original name: :review_complete:
Suggested alias: :rvdone:
Download the original checkmark PNG: 128 × 128 px, 2,776 bytes.
This is an original MakeEmoji sample and a proposed naming example. We have not created these names in your workspace. Check that both are free before you use them. A code that already has another meaning is a poor shortcut, even when it seems easy to remember.
Create the alias on desktop
Slack's custom emoji and aliases guide documents the desktop flow. Open the workspace name menu and choose Customize [workspace name]. Owners and admins may need Settings & administration first. Select Add Alias, then Choose Emoji. Pick the existing emoji, enter the new alias, and save.
For our example, the checkmark must already exist as review_complete. Select that image in Choose Emoji and enter rvdone as the new code. Do not use Upload Image for the second name. If you need to add the original first, follow the Slack custom emoji upload guide.
If the controls are missing, confirm your workspace and role. Slack says members can use the feature by default, but not guests, and owners can restrict custom emoji permissions. An alias in one workspace does not establish that it exists in another.
Test the result without confusing the channel
- Open a suitable test conversation or your own space for drafts.
- Type the original name between colons, then select it from the suggestion if needed.
- Try the alias in the same way. Confirm that the same image appears.
- Search the emoji picker with the words your teammates are likely to use.
- Record the original name and alias together in your team's emoji notes.
Do not assume a typed code worked just because its spelling looks right. Look at the rendered result. If you see text instead of an image, confirm the saved alias, its spelling, and the workspace where you created it. Re-uploading the PNG is not the first useful step.
Choose names that help people find it
A descriptive main name explains the intended meaning. A short alias helps frequent users type it. Keep both tied to the same action. For example, review_complete and rvdone are close; approved and seen can imply different commitments.
Use ordinary words before inside jokes. Avoid names that depend only on color, because the same checkmark might later get a new design. Avoid cryptic numbered codes unless your team already has a clear reason for them. The goal is fewer guesses when someone opens the picker.
If the existing picture does not communicate the intended reaction, fix that separately. The text emoji maker can help make a short word-based image. An alias can make a suitable image easier to find, but it cannot make tiny unreadable lettering clearer.
Remove an alias carefully
Return to the workspace's custom emoji management page and locate the alias entry. Use its delete control and check the selected name before confirming. Slack states that members with deletion permission can remove aliases they added; owners and admins can remove any alias. Keep the original image entry when you only intend to retire the shortcut.
Do not use deletion as a way to test whether the alias is linked correctly. Test both names first. If a shortcut has become common, tell the team about its replacement before you remove it. There is little value in a cleaner list if familiar typing habits suddenly stop working.
Download the alias register to track the original code, alias, meaning, owner, and test result. A small record keeps the convenience of short names without turning one clear reaction into a collection of unexplained duplicates.
