Picsart
The blog doubles as a model catalog: every video model worth using, one prompt bar.
A side-by-side editorial comparison of Pinta and Shotcut — release velocity, themes, recent moves, and the top alternatives to consider.
Pinta is still paying down the GTK4 port while shipping real features on top of it.
Pinta runs two tracks at once. One is a steady stream of 3.0.x and 3.1.x patches fixing icons that stop rendering, crashes, and packaging problems — most of them traceable to the GTK4 and libadwaita port and to GNOME versions moving underneath it. The other is genuine feature work: 3.1 brought an axonometric grid, a polygon selection mode for the Lasso tool, gradient handles, a layer context menu, a Cells effect and a Windows ARM64 installer, on top of a rewritten canvas widget.
A video plumbing rewrite let Shotcut restore external monitor output lost three years ago.
Shotcut ships on a monthly date-versioned cadence with a beta preceding most releases. The significant event in this window is the return of external monitor output to a second system display, which the project lost when it upgraded its UI toolkit three years ago and recovered only after reworking the video plumbing. Around it sit precision fixes that matter to finishing work: color corruption in dissolves under linear 10-bit processing, off-by-one frames in subtitles, and RNNoise misbehaving at non-48 kHz sample rates.
Pinta runs two tracks at once. One is a steady stream of 3.0.x and 3.1.x patches fixing icons that stop rendering, crashes, and packaging problems — most of them traceable to the GTK4 and libadwaita port and to GNOME versions moving underneath it. The other is genuine feature work: 3.1 brought an axonometric grid, a polygon selection mode for the Lasso tool, gradient handles, a layer context menu, a Cells effect and a Windows ARM64 installer, on top of a rewritten canvas widget.
The pattern is a small team absorbing the cost of a large architectural move. Every few months a GTK or GNOME release breaks icon loading or a pixbuf path, and Pinta ships a patch; meanwhile the feature list keeps growing at a rate that suggests the port has stopped consuming all the oxygen. The dependency floor rising to GTK 4.18 and libadwaita 1.7 in 3.1 shows the project has chosen to track the toolkit closely rather than pin behind it, which is why the breakage keeps arriving and also why it keeps getting fixed quickly.
Expect the alternating rhythm to continue — a feature-carrying minor release followed by patches cleaning up toolkit and packaging fallout — with the next round of breakage most likely arriving with the following GNOME cycle.
Shotcut ships on a monthly date-versioned cadence with a beta preceding most releases. The significant event in this window is the return of external monitor output to a second system display, which the project lost when it upgraded its UI toolkit three years ago and recovered only after reworking the video plumbing. Around it sit precision fixes that matter to finishing work: color corruption in dissolves under linear 10-bit processing, off-by-one frames in subtitles, and RNNoise misbehaving at non-48 kHz sample rates.
Two threads. The first is Shotcut paying back debt from its toolkit migration — external monitor support restored, DeckLink deadlocks fixed, Qt updated to fix Wayland popups. The second is a cautious opening toward third-party audio and video plugins: VST2 and LV2 support restored across all builds, and initial OpenFX filter support shipped with unusually frank warnings that most plugins do nothing or produce black video. Both threads point the same way — extending what the editor can plug into rather than what it does natively.
OpenFX support shipped explicitly labelled as limited, so the most likely next step is broadening that compatibility rather than new built-in filters; the video plumbing change that restored external monitor output is also the kind of foundation that tends to produce follow-on playback fixes.
Other Design products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Pinta or Shotcut.
The blog doubles as a model catalog: every video model worth using, one prompt bar.
Product news arrives buried in the marketing blog: mask frames, then agentic video.
Aseprite's 1.3.18 cycle spent its energy on the UI framework, not the drawing tools.
Half of LibreCAD's release feed isn't releases — it's download links and nightly builds.
FontForge releases when it releases — years apart, and the last one was mostly CI repair.
Natron's last real release was 2024, and the feed since then is build infrastructure.
See all Pinta alternatives → · See all Shotcut alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Shotcut is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Shotcut is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Design products to evaluate alongside.
Top Pinta alternatives in Design are ranked by recent ship velocity. Browse the "Pinta alternatives" section above for the current picks, or visit /alternatives/pinta for the full list with editorial commentary on each.
Top Shotcut alternatives in Design are ranked by recent ship velocity. Browse the "Shotcut alternatives" section above for the current picks, or visit /alternatives/shotcut for the full list with editorial commentary on each.