Comment pins stack up fast on a file that’s been through a few review rounds, and there’s a two-key shortcut that clears them off the canvas without touching a single thread. Shift C, pressed anywhere on the canvas.
Nothing gets deleted. Nothing shifts for the people you share the file with. The pins just stop rendering on your screen until you press the same two keys again.
It behaves identically in a design file you have edit rights to and in a FigJam board someone dropped you into with view access only. Figma splits file access across Full, Dev, Collab and View seats, and each carries its own rules about who can hide, resolve, or delete a comment (Figma pricing page, 2026). Hiding is the one action none of those tiers gate.
What does it mean to hide comments in Figma?
Think of it as a visibility switch that sits with the canvas display controls, nowhere near the comment thread itself. Pins disappear from view. The threads underneath keep existing exactly as they were, and everyone else’s screen carries on unchanged.
No data moves. Replies, reactions, mentions, all of it stays stored in the file.
- A comment pin is that small marker on the canvas, the one that opens a thread when you click it.
- The thread is the conversation hanging off that pin. Replies, reactions, the lot.
- Comment mode you enter by pressing C on its own, which also swings the comment panel open in the right sidebar.
By default comments render on the canvas whether or not comment mode is active. Figma’s help documentation says as much.
How is hiding a comment different from resolving a comment?
Hiding changes what you see. Resolving changes what everyone with access sees, which is a much bigger action than the interface makes it look.
The hide toggle is personal and applies canvas wide, and Shift C reverses it whenever you feel like it. Resolving happens per comment and pulls the thread out of the default view for the whole file. Deleting is the permanent one, and only the person who wrote the comment can do it.
Resolved threads aren’t gone either. They come back through the Show resolved comments filter in the right sidebar, which the hide shortcut has no bearing on.
Figma’s Community Support team clarified in 2022 that file owners can delete their own comments but can only resolve threads left by others, never delete them.
Have you seen the latest Figma statistics?
Discover comprehensive Figma statistics including revenue growth, market share, user demographics, and funding data.
Check them out →Replying inside a thread works the same whether comments are hidden or visible.
The mechanics of that back and forth, replies, mentions, reactions, sit in a separate guide on chatting inside Figma files.
How do you hide comments in Figma step by step?
Same behavior in every file, project and page. There’s no per-file variation to learn.
- Click anywhere on the canvas outside of comment mode, so no object is mid edit
- Press Shift and C together to toggle every comment pin off the canvas
- Check the canvas for confirmation, since pins and open threads disappear immediately
- Press Shift C again whenever the same pins need to come back
Clicking the comment icon in the main toolbar does the same thing as pressing C, if you’d rather not touch the keyboard at all.
Worth being clear on this: C by itself opens comment mode and the sidebar. It hides nothing. Two shortcuts, two different jobs, one letter apart.
This one sits alongside dozens of other Figma keyboard shortcuts built to keep designers off the mouse during focused work.
How do you show comments again in Figma?
Shift C toggles both directions, so bringing comments back uses the same two keys.
Press it once more and every pin returns to its original position. Nothing gets moved, edited, or renumbered along the way. Right clicking empty canvas space also gets you a menu with a broader interface visibility control, though that one covers more than comments.
If a specific comment refuses to come back, that’s almost always a resolve status issue rather than a broken shortcut.
Does hiding comments in Figma affect what your collaborators see?
No. It’s a personal setting that never reaches anyone else’s screen.
One Figma Community Forum member described having to explain the Shift C shortcut to more than 30 collaborators across their organization, since most people simply didn’t know comments could be hidden and the pins were cluttering navigation for everyone (Figma Community Forum, 2024).
On your screen, pins and threads vanish the second Shift C lands. On theirs, every pin sits exactly where it was, because a local toggle can’t touch a remote session.
That distinction earns its keep during stakeholder walkthroughs. You get a clean canvas to present from while the client’s own view stays untouched.
A guide on running client presentations in Figma covers the broader setup around that scenario.
Do hidden comments stay hidden when you reopen a Figma file?
No, and this is the part that annoys people. The hidden state resets every time the file opens back up.
- Comments are visible on open, every time, confirmed in Figma’s own help documentation
- Shift C has to be pressed again after every reopen
- The toggle is personal to whoever is viewing, and it never gets written to the file
- Persistence across sessions doesn’t exist by current design
A Figma Community Forum thread from February 2026 asked for a permanent hide by default preference, something along the lines of a light or dark theme switch, and pointed to the manual Shift C repetition as the main friction (Figma Community Forum, 2026).
Nothing like that exists in Figma’s settings as of this writing. The workaround stays the same shortcut, pressed again, every session.
Who can hide or resolve comments in Figma?
Hiding needs no permission at all. Resolving and deleting do.
| Access level | Hide comments locally | Resolve a comment | Delete own comment |
|---|---|---|---|
| View access | Yes | No | Yes |
| Edit access | Yes | Yes | Yes |
| Dev seat | Yes | No | Yes |
Dev seat holders carry the same resolve restriction as viewers, a limitation Figma’s own community forum shows has persisted since Dev seats were introduced in 2024. Engineers hit this constantly, and it surprises them every time.
View access costs nothing on Figma’s Starter plan, per the platform’s own pricing page.
Full seat access on the Professional plan runs about $16 per user each month, the tier most design teams use for edit access (Figma pricing page, 2026). Dev seats sit closer to $12 per user each month on the same plan, built for engineers working mainly inside Dev Mode rather than the main canvas.
A closer breakdown of what each tier unlocks sits in a separate comparison of Figma’s free and professional plans. The specifics of that developer facing workspace are covered in a dedicated Figma Dev Mode guide.
FigJam plays by looser rules. Its documentation states that anyone with view or edit access can resolve a comment there, which is not how standard Figma design files handle it.
When should you hide comments instead of resolving them?
Hiding clears your screen. Resolving clears the file for everyone. Pick based on which one you actually mean.
Hide comments
What works in its favor: it reverses in one keystroke with no confirmation dialog in the way, it never changes status for teammates so nothing gets marked closed by accident, and you can fire it mid task without breaking flow to open a menu.
Where it falls short is the reset on every reopen, plus the obvious one. Hiding signals nothing to the team. Feedback you’ve dealt with looks identical to feedback you’ve ignored.
Resolve comments
Resolving updates the shared record, not just your own screen.
| Resolve comments | Detail |
|---|---|
| Pro | Marks feedback closed for the whole team at once |
| Pro | Recoverable later through the Show resolved comments filter |
| Con | Needs edit access, so viewers and Dev seats cannot do it themselves |
| Con | Skips any formal sign off record some teams still track outside Figma |
Figma’s own design review page describes an assistant that can turn open comment threads into action items directly inside a file, without switching tools mid critique (Figma, design review page).
For a stakeholder walkthrough, hide. Nothing about the file’s status needs to change just because you presented it. Structured reviews with a defined sign off step are the opposite case, since resolving leaves a record every collaborator can check later.
How do you hide comments on the Figma mobile app?
No Shift key on a touchscreen, so the keyboard shortcut is out. Figma put a dedicated toggle inside the same comments view you use to read and reply to threads, confirmed in its help documentation.
| Control | Desktop or browser | Mobile app |
|---|---|---|
| Toggle method | Shift C keyboard shortcut | Icon inside the comments view |
| Scope | Personal to the viewer | Personal to the viewer |
| Syncs across devices | No | No |
Hiding on a laptop won’t carry over to your phone. Each device keeps its own local setting.
Figma’s official app listing confirms the mobile client covers the same core actions as desktop, adding comments, mentioning teammates, and resolving threads on the go (Apple App Store, Figma).
When does hiding comments not work in Figma?
Shift C only touches open, visible comments. Resolved ones are already out of view through a different mechanism, so the shortcut has nothing left to do there.
Permission limits don’t change either. The access levels above apply the same way whether pins are showing or hidden.
Three things trip people up in practice.
- The separate Show or hide UI command gets mistaken for this one. It hides panels and toolbars too, not just comment pins, and the exact key has shifted across Figma versions and keyboard layouts.
- A pin reappearing seconds after you hide everything is usually just a fresh comment a collaborator posted. Not a bug.
- Older tutorials describe a top left comment button or a right click Hide comments menu. Those predate the UI3 toolbar move to the bottom of the screen.
Figma began rolling UI3 out to every account starting October 2024, following a beta shown at its Config conference (Figma, Config 2024).
The REST API ignores the toggle completely. A request to a file’s comments endpoint returns every open and resolved comment, resolved\_at timestamp included, regardless of what any single viewer has hidden on their own screen (Figma REST API specification).
Teams pulling that data into a separate workflow, covered in a guide on developer handoff in Figma, see the same unfiltered results every time.
FAQ on How To Hide Comments In Figma
What happens to comment notifications when comments are hidden?
Nothing. Hiding pins is a canvas view change and stops there.
New comments, replies and mentions all still come through Figma’s normal alerts. Silencing those means changing a notification preference, which lives somewhere else entirely.
Does FigJam use the same shortcut to hide comments?
FigJam opens comment mode with the same C key as Figma Design.
Figma’s documentation presents Shift C as the general hide shortcut across its canvas products, with no separate FigJam version. Resolve permissions are where the two products actually diverge.
Does Dev Mode show comments differently than the main canvas?
No. Dev Mode layers an inspect panel over the same canvas, and you enter it with Shift D rather than Shift C.
Pins, threads and the hide toggle work identically in Dev Mode and in standard Design Mode.
Where Does Hide Comments In Figma Break Down at Scale?
The shortcut stops being enough the moment a review outgrows one screen. It’s a personal display setting, and it marks nothing as seen, tracked, or closed for anybody else.
A team of thirty-plus collaborators, the scale one Figma Community Forum member described navigating in 2024, cannot close a review through hiding alone. Resolving is what closes it, and resolving needs edit access, priced from $16 per user each month on Figma’s Professional plan.
- Check whether you actually have edit access before assuming a comment can be resolved
- Keep hiding for personal focus. It was never a status signal and it won’t become one
Once feedback lands in that resolved state, the design is ready to move into building an interactive prototype in Figma for the next round of stakeholder review.
