Filmscript Composer 1.5.1

August 31, 2026 · 2 min read · Version Updates · Filmara Team

Filmscript Composer 1.5.1 is out. This release reshapes how a project describes its own world, fixes a handful of bugs worth knowing about, and — finally — opens without macOS warning you about it.

Projects define their own vocabulary

Until now, every project shared the same fixed idea of what it could contain. That never quite fit: a documentary doesn't need the same building blocks as a music video, and a short film doesn't need the same ones as a series.

The new Project Settings page lets each project define what its entities are. Characters, props, locations, vehicles — whichever of them your project actually uses, named the way you name them. One place to manage the whole vocabulary, and one door into it.

A script is a timeline

The second half of that change is placements. A filmscript is a timeline, and a placement is a claim about an entity at a moment in it — this character, in this location, at this point in the story.

That sounds abstract until you need it. It's what lets the app answer questions like where does this prop appear, or which scenes has this character been in since the rewrite, without you tracking it by hand.

Import lands a real project

Importing a screenplay now produces an actual project rather than a loose document, and the title page has moved back into script config, where it's edited. A second import path that used to quietly drop the title page no longer does.

Fixes

Fixed a crash on launch caused by the quota cache being restored in a bad state.
Fixed a project-delete path that, in the wrong circumstances, could reach beyond the project it was deleting.
Buttons across the app now render at the weight they were asked for — 226 of them were quietly ignoring it.
Settings theme swatches show the actual colours instead of describing them.

No more security warning

Every previous release was ad-hoc signed, which meant macOS greeted new installs with "Apple could not verify this app is free of malware" and a Move to Trash button. Not a great first impression.

1.5.1 is signed with an Apple Developer ID and notarized by Apple. It opens normally.

If you're on 1.4.1, please read this

This one needs a manual step, once.

1.5.0 changed the key used to sign updates. Apps built before that change verify updates against the old key, so the in-app updater cannot install this release — it will offer the update and then fail.

If you're on 1.4.x, download 1.5.1 directly and install it over your existing copy. Your projects are untouched. After that, in-app updates work normally again — this is a one-time interruption, not a new state of affairs.

Apologies for the friction. It was the cost of a signing key that could not be recovered, and the alternative was leaving everyone on 1.4.1 indefinitely.