---
title: "ShareX is being rewritten in Rust, and here is the branch plan"
url: https://endomint.com/p/m7-SR53DUEzikiaFnzGngA/sharex-is-being-rewritten-in-rust-and-here-is-the-branch-pla
published: 2026-11-16
updated: 2026-11-16
tags: ["avalonia", "branches", "cross-platform", "release", "rust", "sharex"]
---

# ShareX is being rewritten in Rust, and here is the branch plan

ShareX is going to be rewritten in Rust. The plan for how that happens is four steps long, and none of them are dated yet.

The branch names in the plan are the ones it proposes, not the ones the repository has today. The release branch is `master`, and there is no `rust` branch yet.

[![ShareX branch plan: four steps across four branch lanes, from releasing Classic and tag it, through starting the Rust rewrite and folding cross-platform into develop, to making Rust the main line](https://endomint.com/images/sharex-branch-plan.png)](https://endomint.com/embeds/sharex-branch-plan.html)

## Why Classic and Avalonia keep going

Classic keeps existing for people who want a stable build, and once it takes hotfixes only it stops costing anything but maintenance.

Avalonia work is not blocked while Rust gets written, and that work is already substantial: [the cross-platform branch](https://endomint.com/p/N4xxaUOZ8ONPFKy2adktpw/how-sharex-itself-goes-cross-platform) is the one that puts ShareX on Windows, macOS and Linux behind a single abstraction layer, and the repository's own roadmap records Windows, Linux and macOS all at 100%. Folding it into `develop` leaves one Avalonia line instead of two while Rust matures.

## The rename is the sharpest edge

`develop` is the default branch of the repository today, and renaming `rust` over it means the old `develop` history has to go somewhere else first. The plan assumes `rust` starts with its own fresh history, which is what a from-scratch rewrite means, and that is why every contributor has to back up and reset their local `develop` afterwards.

## The part that has to be true

Two things are still open, and they are the ones worth arguing about before any of this starts.

The gate criteria are not written down. "Good state" and "ready" are doing a lot of work in a plan with no dates attached, and the region capture and image editor example is a starting point rather than a definition.

The tag-or-branch choice for Avalonia has a consequence. A tag named `avalonia-final` freezes the code and makes it read-only in practice. A branch named `avalonia` keeps it open, and it is the only option if open Avalonia pull requests are to be retargeted rather than closed.
