| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| latest-mac.yml | 2026-11-10 | 339 Bytes | |
| latest.yml | 2026-11-10 | 335 Bytes | |
| latest-linux.yml | 2026-11-10 | 534 Bytes | |
| WeftCut-win-x64.exe.blockmap | 2026-11-10 | 270.6 kB | |
| WeftCut-linux-amd64.deb | 2026-11-10 | 295.2 MB | |
| WeftCut-linux-x86_64.AppImage | 2026-11-10 | 372.3 MB | |
| WeftCut-mac-arm64.dmg | 2026-11-10 | 244.9 MB | |
| WeftCut-mac-arm64.dmg.blockmap | 2026-11-10 | 257.7 kB | |
| WeftCut-win-x64.exe | 2026-11-10 | 257.2 MB | |
| README.md | 2026-11-10 | 5.1 kB | |
| WeftCut 0.7.0 source code.tar.gz | 2026-11-10 | 23.5 MB | |
| WeftCut 0.7.0 source code.zip | 2026-11-10 | 25.1 MB | |
| Totals: 12 Items | 1.2 GB | 0 | |
Install
- Windows — run
WeftCut-win-x64.exe. The app keeps itself current: new versions download in the background and install when you quit. - Linux —
WeftCut-linux-x86_64.AppImage(mark it executable first) orWeftCut-linux-amd64.deb. Self-updates like Windows. - macOS (Apple Silicon, macOS 13 or newer) — open
WeftCut-mac-arm64.dmgand drag WeftCut into Applications. The build is ad-hoc signed and not notarized (WeftCut has no Apple Developer ID), so macOS blocks the first launch: open the app once, click Done, then go to System Settings → Privacy & Security and click Open Anyway. If macOS calls the app damaged instead, clear the download quarantine in Terminal and open it again:
sh
xattr -dr com.apple.quarantine /Applications/WeftCut.app
macOS builds do not self-update; watch this page for new versions.
What's new in 0.7
Projects from 0.6 open as they are; the project format and the MCP tool list did not change. Cached Motif frames are rebuilt once after the update.
Motifs play back faster
- Several Motifs at once. WeftCut now renders Motifs in up to eight capture hosts instead of one, opening them as the timeline needs them and only while memory has room. Two Motifs playing together went from under 4 fps each to 10–30 fps on an M1 8 GB Mac and a mid-range Windows PC. Many Motifs playing at once can still drop frames the first time through; a pre-baked range plays from disk.
- Faster first frames. A Motif frame is taken from the paint that carries its number, without the screenshot and the settle wait before it. On Linux, macOS and Windows machines without shared textures a frame takes about a third of the time it did.
- Playback you have seen once is kept. Every Motif frame the preview captures is stored, on every platform, so playing a range again reads it from disk. Pre-bake all motif content now only decides whether frames you have not played yet are prepared in the background.
- Smaller, faster stored frames. Stored frames decode on several threads: a 4K frame reads in 11 ms instead of 15 ms. Pre-baking is faster as well.
- No black flash on a seek. Seeking onto a Motif, or playing into one, keeps the previous picture until the Motif's frame arrives, the way a video clip does.
In the editor
- Highlights. A new colour effect with a keyframeable Amount from -100 to 100, in preview, export and MCP.
- Edits stay quick in large projects. A project with dense keyframes used to stall for about 90 ms on every edit; an edit now sends only what changed.
Fixes
- A Motif no longer stops rendering for the rest of the session with "no motif.define() called" after several Motifs were edited or switched quickly.
- A Motif's first frame in a new capture window no longer comes out transparent, and such a frame is no longer stored.
- Motifs narrower than 56 pixels render.
- Pre-bake now is kept when the preview is rebuilt, and is no longer lost when it is clicked while the preview is still loading.
- A video whose hardware decoder could not open for lack of memory no longer loses hardware decoding until restart; it retries.
- SRT files that separate cues with a line of spaces import as separate cues.
- WebVTT character references such as
&and'import as the characters they name. - The splash screen's text fade ends with its motion.
- On macOS and Linux, ffmpeg processes also end when the app is killed during its first moments.
After updating
- Motif caches rebuild. The stored-frame format changed, so frames baked by 0.6 are not read. Motifs render live again the first time they play, and pre-baked layers bake again. The old frames are removed from the project's cache by the usual cleanup.
- Agent users: nothing to change. Tool schemas were corrected for Codex, which could not see the arguments of
set_positionandrestack_layer, and the descriptions of the move and restack tools now say which one to use.
What's Changed
- perf(state): a project publication crosses as a difference by @UncleChair in https://github.com/WeftCut/WeftCut/pull/127
- feat(effects): add native Highlights adjustment strength control by @ej05388 in https://github.com/WeftCut/WeftCut/pull/114
- chore(effects): highlights in the gate notes and test names by @UncleChair in https://github.com/WeftCut/WeftCut/pull/128
- fix(mcp): every schema field reaches Codex, and siblings route both ways by @UncleChair in https://github.com/WeftCut/WeftCut/pull/129
- fix(subtitles): WebVTT character references read back as the text they name by @mecrimino in https://github.com/WeftCut/WeftCut/pull/130
- fix(subtitles): a whitespace-only line between SRT cues separates them by @mecrimino in https://github.com/WeftCut/WeftCut/pull/132
New Contributors
- @ej05388 made their first contribution in https://github.com/WeftCut/WeftCut/pull/114
- @mecrimino made their first contribution in https://github.com/WeftCut/WeftCut/pull/130
Full Changelog: https://github.com/WeftCut/WeftCut/compare/v0.6.0...v0.7.0