A lyric draft becomes an editable arrangement
Paste a chorus into JIZURA, load the song, and press Create a variation. The browser chooses a visual arrangement, including moving words and changes between shots. You can keep the timing while trying another palette or locking a line you like. That's the reason to try it: a musician with finished lyrics can get a starting composition without drawing every title animation. The primary documentation is Japanese, with an English guide and English app available.
The 32.1 MB checkout in our lab contained 158 files and roughly 79,211 lines of source. This is a substantial collection of visual machinery behind a simple entry point. The English guide describes manual cut markers, tap synchronization, and per-cut replacements. Those controls matter more than another random style: you need a way to repair a good arrangement where a word arrives late or an effect distracts from the chorus.
What happened when we ran it
Our JIZURA run installed 1 npm package in 5 seconds, using 1 MB on disk. We cloned commit fc16bfe on October 12, 2026, and the detected Node project lived in dev/. The install succeeded. Build and tests were skipped because the harness found no script or target for either. That leaves a narrow finding: the development package installed successfully, while the run provides no completed build or passing suite to cite.
The unprivileged sandbox had 3 CPUs and 8 GB of RAM, used the lab-node:22 image, and contained no secrets. Npm audit reported 0 known vulnerabilities across all severity levels. The scan found 0 CI workflow files, no Dockerfile, and no tests directory. An audit result covers known dependency advisories in that environment. It says nothing about whether a long export keeps its audio, whether the generated typography is readable, or whether an After Effects composition matches the preview.
The browser app needs no server account
JIZURA's documented user path is the hosted page or a downloaded standalone HTML file. The README says lyrics, audio, and exports stay inside the browser, while Google Fonts loads the typefaces the arrangement uses. Locally installed fonts provide an offline fallback. That makes it appealing for unreleased songs: the normal workflow described in the guide doesn't ask you to upload the source audio or obtain a hosted rendering credential.
Our 1 MB dependency footprint belongs to the npm installation in dev/, so it shouldn't be mistaken for the whole editor's storage cost. The checkout already occupied 32.1 MB, and the guide says imported audio persists in browser storage. Save a .jizura.json project when a composition is worth keeping. A retained browser song is convenient across reloads, but an explicit project file gives you something you can move and keep alongside the source lyrics.
MP4 export depends on the browser's codecs
The Japanese README recommends Chrome or Edge for WebCodecs-based MP4 export. It says H.264 availability depends on browser and operating system, with preview and PNG sequences available when video encoding is unsupported. The English guide also describes a separate WAV soundtrack when the browser can't encode AAC. Check the deliverable your editor needs before committing the whole song: an MP4 accompanied by a WAV requires another assembly step if the recipient expects embedded audio.
Phone mode starts at 720p and caps output at 1080p unless you switch to Advanced mode. Those are documented settings, not resolution results from our 3-CPU sandbox. The developer run didn't measure video export speed or phone reliability. If you plan to finish on a handset, make a short export with your actual fonts and soundtrack first. A successful preview can leave a codec problem undiscovered until the final file is requested.
The After Effects handoff needs a visual check
Open issue 40 concerns the JIZURA_AE.jsx panel labeled v0.9.0, running in After Effects on macOS. Its author reports that generation finishes but emits warnings about a hidden fill-color property and an out-of-range tracking value. Those warnings concern the very output you'd hand to an editor: color and letter spacing. They aren't evidence that browser MP4 export fails. The report gives a concrete reason to inspect the imported composition before accepting it.
Our run skipped tests, and the scan found 0 CI workflows. The English guide separately says the panel's automated checks use a mock After Effects environment and that actual After Effects is needed to verify motion and export behavior. Some effects are approximated with standard effects and transforms in the Japanese documentation. Treat the JSON handoff as an editable starting point. If a client requires the browser preview reproduced exactly, check the troublesome cuts in the intended Adobe environment before quoting the job.
October activity supports trying it, with a small acceptance job
The last repository push was October 1, 2026. GitHub showed 1,816 stars and 25 open issues and PRs, with issue activity continuing into October. The latest-release endpoint returned no published release, which doesn't establish abandonment: the push and discussion dates show recent work. The English guide's v0.9.0 label also sits beside instructions marked v0.10, so pin the downloaded artifact instead of assuming every documented change belongs to a released package.
Choose JIZURA for a lyric video you can inspect and adjust yourself. Our 5-second install makes the developer entry inexpensive, but offers no shortcut around checking the finished media. Remotion suits a developer who wants animation defined in React and repeatable rendering logic. Shotcut suits someone who needs a general desktop video timeline. For JIZURA, the sensible first job is your hardest chorus: export it, listen for the soundtrack, then check every word before extending the arrangement to the whole song.