Picsart
The blog doubles as a model catalog: every video model worth using, one prompt bar.
A side-by-side editorial comparison of FontForge and Shotcut — release velocity, themes, recent moves, and the top alternatives to consider.
FontForge releases when it releases — years apart, and the last one was mostly CI repair.
FontForge publishes a dated release roughly once a year at best, and the gaps have stretched to three years more than once. The October 2025 release is dominated by keeping the project buildable — CI runners updated, Python made consistent on the macOS runner, Windows CI repaired — with a handful of real fixes around lookup flag parsing and glyph file naming. The substantive feature work in this window is older than the release cadence suggests.
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.
FontForge publishes a dated release roughly once a year at best, and the gaps have stretched to three years more than once. The October 2025 release is dominated by keeping the project buildable — CI runners updated, Python made consistent on the macOS runner, Windows CI repaired — with a handful of real fixes around lookup flag parsing and glyph file naming. The substantive feature work in this window is older than the release cadence suggests.
The pattern is a mature editor maintained by a small group of contributors, where large capability jumps arrive in single bursts and then nothing for years. The 2020 stroke expansion rewrite and the 2022 plugin and Unicode 14 release are where the actual capability moved; the releases on either side are fixes and packaging. Notably, plugin support was removed in 2019 and rebuilt on Python three years later, which is the clearest signal of how this project resolves architectural questions — by deleting and revisiting rather than iterating.
Given a cadence measured in years and a most recent release weighted toward CI maintenance, the next publication is more likely to be another consolidation of accumulated fixes than a new capability.
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 FontForge 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.
Pinta is still paying down the GTK4 port while shipping real features on top of it.
Natron's last real release was 2024, and the feed since then is build infrastructure.
See all FontForge 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 FontForge alternatives in Design are ranked by recent ship velocity. Browse the "FontForge alternatives" section above for the current picks, or visit /alternatives/fontforge 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.