Blog
Why Keyframe is built the way it is.
RSS feedEvery post
Design noteWhy Keyframe doesn’t copy After Effects everywhereWe kept the best of After Effects and changed course only where its history holds it back.
Design noteBones without expressions: how Keyframe rigs a characterIn After Effects, bones are pieced together from layers and expressions; in Keyframe a skeleton is a layer, solved by the editor itself.
Design noteFrom one picture to layers you can animate: why splitting lives in the editorIn After Effects, layers are split in Photoshop first; Keyframe splits a picture into layers you can animate, in the editor, and keeps the original.
Design noteWhy the Agent gives you a draft first: how AI takes part in editing in KeyframeAfter Effects’ AI Assistant edits the project directly; Keyframe’s Agent uses the operations you use and makes a draft that you look at before applying.
Design notePictures written as code: why Keyframe’s shaders are project dataIn After Effects, writing a shader means compiling a plug-in; in Keyframe the program is data in the project, run in a sandbox on your graphics card.
Design noteNo plug-ins needed: why Keyframe builds its features into the editorMany of After Effects’ features come from third-party plug-ins; Keyframe builds them into the editor, so a project opens the same on any computer.