# Tusk: an Electron wrapper that turns Evernote's web client into a desktop app for Linux

> Tusk is an unofficial open source Evernote desktop client built on Electron. It adds themes, keyboard shortcuts, note export and Yinxiang login on top of the web app, but it is a wrapper, not a sync engine, and its last release was in 2019.

**klaudiosinani/tusk** — Refined Evernote desktop app

- Repository: https://github.com/klaudiosinani/tusk
- Website: https://klaudiosinani.com/tusk
- Stars: 3,153 · Forks: 242
- Language: JavaScript
- License: MIT
- Published: 2026-09-24 · Updated: 2026-09-24 · Language: en
- Canonical page: https://hysenlabs.com/projects/klaudiosinani-tusk

## What Tusk actually is, and who it is for

Tusk is an unofficial, community-driven Evernote desktop app. The README describes it as "Refined Evernote desktop app" and states that Evernote itself lists it as an alternative client for Linux environments. That single sentence explains the audience: people who use Evernote as a service but have no official Linux desktop client to open it with.

The distinction matters more than the feature list. Tusk is not a note database and it is not a sync client. It is an Electron shell around Evernote's web interface, with local behaviour layered on top: window chrome, themes, keyboard handling, and export paths. Everything about your notes still comes from Evernote's servers through the web app. If Evernote's web client changes, Tusk changes with it, because Tusk is rendering that client.

So the target user is narrow and specific. You need an Evernote account. You need to be on a platform where the official client is missing or unsatisfying, which in practice means Linux. And you need to accept that the project's own README points to a homepage for the full feature description rather than documenting everything in the repository.

## The Electron wrapper mechanism and where state lives

The repository layout is a conventional Electron application. There is an index.js entry point at the top level, a src/ directory for application code, a static/ directory for assets, and a build/ directory used by electron-builder. The package.json declares electron 6.0.11 as a dev dependency and electron-builder 22.9.1 for packaging, with appId com.klaudiosinani.tusk.

The runtime dependencies reveal the shape of the wrapper. electron-context-menu supplies a right-click menu, electron-dl handles downloads from inside the embedded page, electron-debug adds developer tooling, auto-launch registers the app at login, and electron-settings persists preferences. turndown is the interesting one: it converts HTML to Markdown, which is how the Markdown export feature works. The note content arrives as HTML from the web client and gets converted on the way out.

Configuration lives in a single JSON file in the user's home directory. The README states that shortcut keys can be modified by navigating to ~/.tusk.json or by pressing Cmd/Ctrl and the period key, and that deleting ~/.tusk.json and restarting the app resets them. That file is the whole customisation surface for keyboard behaviour. There is no server component, no local database and no background sync process described anywhere in the documentation.

## Installing Tusk and rebinding a shortcut

The README gives three installation routes. On Ubuntu Linux you install from Snapcraft, which is the channel the README treats as officially maintained. On macOS you install through Homebrew Cask, with an explicit caveat that the cask version may not be the latest because it is not officially maintained. Otherwise you download an installer from the GitHub releases page for your system.

The Snapcraft route is one command:

```bash
snap install tusk
```

On macOS the README gives the cask command as:

```bash
brew cask install tusk
```

Note that this is the form printed in the README. Newer Homebrew versions moved cask handling under the brew command itself, so if that invocation is rejected, the README's own advice applies: download directly from the releases page instead of relying on the cask.

Once the app is running and you are signed in to Evernote, the first real customisation is a shortcut rebind. Press Cmd/Ctrl and the period key to open the shortcut editor, or edit the file directly:

```json
{
  "shortcuts": {
    "exportNoteAsMarkdown": "CmdOrCtrl+O"
  }
}
```

The README states that the file lives at ~/.tusk.json and that deleting it and restarting the app restores the defaults. The exact key names inside the file are not enumerated in the README, so open the file the app writes first and edit the entries you find rather than inventing new ones. After saving, restart Tusk for the change to take effect.

## Themes, shortcuts and export are the real feature surface

Strip away the wrapper framing and Tusk's value is a set of local conveniences that the web client does not offer. There are three themes beyond the default: Black, Dark and Sepia, each bound to a shortcut. There are three view modes: Focus, Compact and Auto-Night, where Auto-Night adjusts to the environment on a keypress. There is a scalable interface with zoom controls.

The shortcut count is the headline claim: the README says 70+ local keyboard shortcuts. Many of them are editing commands you would expect in a rich text editor, such as bold, bulleted lists, alignment, indentation, code blocks and date stamps. Others are application-level: note navigation with Cmd/Ctrl+Tab and Cmd/Ctrl+Shift+Tab, direct jumps to notes with Cmd/Ctrl+1 through Cmd/Ctrl+9, and printing. Global shortcuts are opt-in through the File menu's Enable Global Shortcut Keys option, which means they work when Tusk is not focused.

Export is the feature most likely to outlive the app. Notes can be saved as Markdown with Cmd/Ctrl+O, as HTML with Cmd/Ctrl+Shift+H, and as PDF with Cmd/Ctrl+Shift+E. The Markdown path runs through turndown. Drag and drop file attachment is supported, and there is a Yinxiang login option under File > Switch to Yinxiang for Evernote's Chinese service. Update notifications are configurable by frequency.

## Where Tusk breaks down

The first limitation is structural, not a bug. Tusk renders Evernote's web client, so it inherits that client's requirements. The README does not document offline mode, a local note cache, or any sync mechanism of its own. If the web client needs a connection, Tusk needs a connection. Anyone who chose Evernote for offline notebooks will not get that behaviour from this shell.

The second limitation is maintenance cadence. The most recent release listed is v0.23.0 from 2019-05-20, preceded by v0.22.0 in February 2019 and v0.21.0 in January 2019. The repository's last push was on 2026-06-24, so the codebase is not abandoned, but the release history shows a long gap between the 0.23.0 tag and any packaged build. Electron 6.0.11 is the pinned dev dependency. That is a very old Electron line, and the README does not describe a migration plan. A wrapper pinned to an old Electron release accumulates security and compatibility debt that the project does not address in its documentation.

The third limitation is the unofficial status itself. Tusk depends on Evernote's web interface remaining stable enough to wrap. The README carries a disclaimer section, and the project is explicit that it is community-driven rather than endorsed. There is no documented fallback if Evernote changes authentication or page structure. If you need a client with a support contract or a guaranteed compatibility window, this is the wrong tool.

## How Tusk differs from the official Evernote client

The obvious alternative is Evernote's own desktop application, which the README points to as the thing Tusk is an alternative to. The difference in approach is fundamental. The official client is a first-party application with its own local storage and sync engine, maintained by the company that runs the service. Tusk is a third-party shell that loads the web client and adds local behaviour around it.

That produces opposite trade-offs. The official client can work with a local database and reconcile changes, which is what makes offline editing possible. Tusk cannot, because it never owns the data. In exchange, Tusk is not tied to a platform release schedule. It exists on Linux, where the README indicates Evernote itself recommends it as a community-trusted alternative. It also adds things the official client does not offer in the same form, such as Markdown export through turndown and a shortcut editor backed by a plain JSON file at ~/.tusk.json.

A second alternative is simply using Evernote in a browser tab. That costs nothing and always tracks the current web client, but you lose the global shortcuts, the theme switching, the drag-and-drop attachment handling and the export commands. Tusk is essentially that browser tab plus a desktop integration layer. Whether the layer is worth installing depends on how much you use those specific commands.

## Maintenance cost, licensing and what to check before adopting

Tusk is MIT licensed, per both the repository metadata and the license field in package.json. That is a permissive licence: it allows use, modification and redistribution provided the copyright notice and permission notice are preserved. It says nothing about Evernote's terms of service, which govern your account and the service Tusk connects to. Running an unofficial client is a question for Evernote's terms, not for the MIT grant, and the documentation here does not resolve that.

Upgrade cost is the practical concern. Because Tusk wraps a live web client, most upstream changes arrive without a Tusk release at all. What does require a release is anything touching the Electron shell: the pinned Electron 6.0.11, the electron-builder 22.9.1 packaging, and the runtime dependencies. The gap between the v0.23.0 release date and the repository's later commit activity means a user installing today may be running a package built years before the current source. The README's own note that the Homebrew Cask may lag behind the GitHub releases page is the same problem in miniature.

Before adopting, check the releases page for a build newer than v0.23.0, and prefer the Snapcraft channel on Ubuntu since the README identifies it as the officially maintained one. If you are on macOS, compare the cask version against the GitHub release rather than assuming they match.

## Conclusion

Adopt Tusk if you are on Linux, already pay for Evernote, and want a native-feeling window with themes, shortcuts and Markdown export. Skip it if you need offline access, if you are not an Evernote subscriber, or if you want a client that keeps pace with Evernote's web interface. Before installing, check the releases page for a build newer than v0.23.0, and confirm that the Homebrew Cask version matches the GitHub release, since the README notes the cask is not officially maintained and may lag behind.

## FAQ

### How do I install Tusk on Ubuntu?

Install it from Snapcraft with snap install tusk. The README presents Snapcraft as the officially maintained distribution channel for Ubuntu Linux users.

### Can I change Tusk's keyboard shortcuts?

Yes. Press Cmd/Ctrl and the period key to open the shortcut editor, or edit the file at ~/.tusk.json directly. To reset everything to defaults, delete ~/.tusk.json and restart the app.

### Does Tusk work offline?

The README does not document any offline mode or local note cache. Tusk renders Evernote's web client, so it depends on the same connectivity that client requires.

## Sources

- [klaudiosinani/tusk on GitHub](https://github.com/klaudiosinani/tusk)
- [License: MIT](https://github.com/klaudiosinani/tusk/blob/master/LICENSE)
- [Project website](https://klaudiosinani.com/tusk)
- [README](https://github.com/klaudiosinani/tusk/blob/master/README.md)
- [Releases](https://github.com/klaudiosinani/tusk/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/klaudiosinani-tusk