Honest sticky notes status on Ubuntu
PinnyNotes publishes Windows pinned notes assets only. Cork Latch records no AppImage, deb, rpm, Flatpak, or Snap on verified tags. Upstream README explains Linux is not planned.
Prefer the Windows install door
Take PinnyNotes-Setup-*-x64.msi from releases on a Windows PC, or use winget. Windows walkthrough: install on Windows.
Do not invent package names
Avoid pasting guessed apt or dnf lines for pinned reminders. They will fail or pull unrelated packages. Keep lab cards honest with brew NONE and no Linux binary notes.
Wayland and always-on-top
Always-on-top PinnyNotes is a core PinnyNotes feature. Upstream README notes modern Linux Wayland desktops do not allow reliable always-on-top and window positioning the way Windows does. That is why sticky notes here stays Windows-first.
Related pages
macOS note: macOS. Download safely: download safely. Home: pinned notes. Guides: guides. About: about. Editorial: editorial policy. Safety: is sticky notes safe. For this computer: for this computer.
Imaging lab fleets
Document Windows as the PinnyNotes standard. Do not send Ubuntu volunteers hunting for a PinnyNotes package that does not exist on verified tags.
Summary
No official pinned notes Ubuntu binary for PinnyNotes on verified Releases. Prefer Windows Setup MSI or winget. Keep honesty on the machine card.
Desk workflow that survives a reimage
Write the install door on the machine card before you change colours. Reminder work fails when a substitute invents a second Downloads mirror during SmartScreen friction. Prefer returning to GitHub Releases for PinnyNotes-Setup-*-x64.msi or the verified winget id 63BeetleSmurf.PinnyNotes every time.
Shared apartments and classroom desks should document which Windows user owns the tray session. Two people sharing one profile will collide on pin defaults and note colours. Separate OS accounts keep maps honest and make uninstall tickets shorter.
Travel laptops benefit from a single documented installer door written beside the notes folder. Lab images drift when someone installs a Softonic-style wrapper that only ranked for reminder-pad searches. Prefer the named Setup MSI filename on the ticket.
PinnyNotes features worth proving early
Prove pin always-on-top first. Then prove auto-save by typing a line, restarting the app, and confirming the text returned. Only after those two prove steps should you explore colours, transparency, dark mode, and right-click tools such as Base64, Hash, JSON, Case, and DateTime.
Spell checking on current releases uses Windows APIs, which improves performance versus older approaches. Tray bring-to-front helps when note windows are buried under browsers. Block minimizing helps when Show Desktop would otherwise hide reminders you still need.
Honesty about rivals
Windows Sticky Notes remains the right choice when Microsoft account sync is the job. Stickies remains a long-running freeware option with its own habits. Simple pinned notes and Notezilla serve other feature sets, including paid tiers on some rivals. This guide does not invent scores; it maps stranger-safe PinnyNotes install doors.
Cutover from any rival means paste text by hand. There is no documented importer in the PinnyNotes README for rival databases. Plan a quiet half hour. Keep a text backup if your team requires rollback.
Package honesty for fleets
winget id 63BeetleSmurf.PinnyNotes is YAML-verified in microsoft/winget-pkgs against the same MSI and portable zip URLs on GitHub Releases. Homebrew has no PinnyNotes cask. Linux binaries are not published on verified tags, and upstream README states Linux is not planned for this client.
Write brew NONE on printed cards. Write Windows-only on the standard. That prevents weekend chat storms when a volunteer hunts for a package that does not exist.
Security posture without invented audits
Prefer official GitHub Releases assets and the verified winget id. Skip claiming third-party audits the README does not publish. Licence is GPL-2.0. Security contact surface is the GitHub security page for 63BeetleSmurf/PinnyNotes. Note text lives locally on the Windows PC you manage after install.
Links that keep work on one host
Pillar: home. Releases: releases. GitHub: GitHub. Download safely: download safely. For this computer: for this computer. Installed: installed. Guides: guides. About: about. Editorial: editorial policy. Safety: is it safe.
Closing checklist
Confirm the tag, the MSI filename, the winget id if used, one pinned note, and auto-save after reboot. That five-box checklist outperforms a three-page essay nobody finishes under stress.
Frequently asked questions
Can I install sticky notes on Ubuntu?
No official PinnyNotes sticky notes Ubuntu binary is published on verified Releases tags. Prefer Windows with PinnyNotes-Setup-*-x64.msi or winget. Prefer official GitHub Releases or the verified winget id, write the Setup MSI filename on the machine card, and prove pin always-on-top plus auto-save once before trusting the desk.
Why no Linux sticky notes build?
Upstream README states Linux is not planned for PinnyNotes because WPF is Windows-only and Wayland limits reliable always-on-top positioning for sticky notes. Prefer official GitHub Releases or the verified winget id, write the Setup MSI filename on the machine card, and prove pin always-on-top plus auto-save once before trusting the desk.
Is there a Flatpak or Snap?
No Flatpak, Snap, AppImage, deb, or rpm is attached to the non-prerelease tags verified for sticky notes here. Prefer official GitHub Releases or the verified winget id, write the Setup MSI filename on the machine card, and prove pin always-on-top plus auto-save once before trusting the desk.
Where do I get Windows sticky notes?
Use GitHub Releases PinnyNotes-Setup-*-x64.msi or winget id 63BeetleSmurf.PinnyNotes. See the Windows install guide. Prefer official GitHub Releases or the verified winget id, write the Setup MSI filename on the machine card, and prove pin always-on-top plus auto-save once before trusting the desk.