How to Share a Tier List: Link, PNG and the Context That Gets Lost

Sharing a tier list is not just sending the image. The roster, the criterion and the date are part of the argument. Without them, the reader sees coloured rows and supplies their own assumptions.

Share the link when the board is interactive

A link lets the reader see the full roster, the vote table and the maker. It also lets you update the page later without reposting the image. Use the share link from the maker or the page URL, not a screenshot of the URL bar.

Use a PNG when the board needs to travel

A PNG works in group chats, forums and social posts where a link may be ignored. Export at a readable size and check that the item names are legible on a phone before posting. A board that requires zooming is a board that will be misread.

Add the missing context

Include three things in the post or message: the criterion, the date and the roster scope. “Best Genshin characters for a new account, October 2026” is a shareable claim. “Genshin tier list” is not.

If the board is intentionally subjective, say so. “My favourites, no objectivity claimed” prevents a pointless argument about method.

Credit the source roster

If you started from someone else's board, link it. The maker is designed for remixing: the original page stays intact, and your version is a separate board. That is better for the reader than an uncredited copy with three items moved.

Share the update, not a silent edit

When the patch or season changes, publish a new board and link the old one. A silent edit makes old screenshots look wrong and erases the reason the ranking changed. The comparison is often the most useful part.

Where each format works. A link is best for forums, Discord and anywhere the reader can click. A PNG is best for group chats and image-first feeds. A short text summary is best for a message where neither link nor image will be opened.

A share checklist. Criterion, date, roster scope, link, and an image that is readable at phone size. If one of those is missing, the reader will fill the gap with an assumption.

The one-line context that saves the board

The most useful line in a shared tier list is not the title. It is the context: “best supports for ranked, patch 7.3, solo queue”. That line tells the reader what the board is measuring and who it is for.

Without it, the reader supplies their own criterion. A board made for beginners gets judged as a tournament list. A favourites board gets judged as an objective ranking. The argument that follows is about a claim nobody made.

Write the context before the image. If it does not fit in one line, the board is trying to answer too many questions.

Image readability is not optional

A tier list image has to survive a phone screen, a group chat preview and a repost. That means large item names, strong contrast and a limited number of rows. A board that looks sharp on a 27-inch monitor can be unreadable at 360 pixels wide.

Test the export at the size it will actually appear. If the names are too small, remove items or split the board into two images. Do not solve the problem by making the image taller; most feeds will crop or shrink it.

Keep the S and F rows visually distinct. The letters should be readable without relying on colour alone, especially for readers with colour-vision deficiency.

Sharing in Discord

Discord compresses images and buries long messages. Put the board in the first message, the criterion in the same message, and the link in a thread or follow-up. If the board is for a specific channel, say which patch or season it covers.

Use a PNG for the quick reaction and the link for anyone who wants to vote or remix. Do not post the same board in five channels; it reads as spam and the discussion fragments.

If the server has a tier-list channel, follow its format. A board with the criterion in the title is easier to search later than a bare image with no context.

Sharing on forums and Reddit

Forum readers expect a method. Put the criterion, roster scope and date in the post body, not only in the image. A short paragraph explaining the biggest disagreement gives people something to reply to.

Link the published page if it has a vote or a maker. A static image invites one round of comments; an interactive board invites a longer thread and gives the reader a reason to return.

Do not title the post “objective tier list”. It invites the one reply you cannot win. “My patch 7.3 support board, criteria inside” is easier to defend and more likely to produce a useful discussion.

Updating a shared board

When the board changes, share the new version with a short note about what moved. Do not silently replace the image in the original post; anyone who saved it will think the old ranking is still current.

If the change is small, a comment on the original post may be enough. If the top row changes, a new post with a link to the old one is clearer. The comparison is part of the value.

Keep the old page online. Deleting it breaks links and makes the new board look like the only version that ever existed, which hides the reason for the update.

A post template that works

Title: the roster and the criterion. First line: the date and patch or season. Image: the board, readable at phone size. Body: two or three sentences on the biggest disagreement. Link: the interactive page or maker.

That is enough for most platforms. The template is deliberately short; a long essay before the board makes the reader scroll past the thing they came for.

If the board is intentionally subjective, say “my favourites” in the title. It prevents a method argument that the board was never trying to have.

Avoid link rot

A shared board can outlive the page it points to. Use a stable URL for the published version and avoid links that expire or require a login. If the board is a temporary image, say so and keep the method in the post text.

When you update the page, keep the old URL working or redirect it to the new version. A reader who finds a two-year-old post should land on something that explains what changed, not a 404.

Link rot is especially bad for tier lists because the screenshot often survives longer than the page. The image may be the only record of the argument; make the surrounding text self-contained.