EffectCraft export routes solve different jobs
The maintainer README documents a render queue, ProRes MOV with alpha-capable profiles, image sequences and Lottie output. These are routes to test in the selected build, rather than a promise that every composition works in every format.
| Required result | Route to investigate | Receiving check |
|---|---|---|
| A flat video for review | A documented video output such as H.264 MP4 | Playback, crop, timing and text |
| An overlay above other footage | An alpha-capable ProRes profile or suitable image sequence | Transparent background and soft edges |
| An animation in a web or app player | Lottie JSON or .lottie export | Supported features and target runtime |
| A future editable revision | The .ecproj working project and assets | Assets, fonts and a reference render |
Check transparency in the actual compositor
A transparent overlay needs both suitable output settings and a receiving application that uses that transparency. A black or white background in one player is not enough to decide whether the exported file contains useful alpha.
Render a short section with empty areas and a soft edge. Place it over a light background and a dark background in the receiving editor. Look for a fixed rectangle, an unwanted fringe or a change in the intended opacity. Retain the working project while adjusting the export. The profile and result matter more than the filename alone.
Review Lottie export warnings and runtime behavior
The repository describes Lottie export through File → Export → Lottie JSON and says it lists features that Lottie cannot express. Treat that report as part of the handoff. An exported JSON file is not proof that the animation matches the composition.
Inspect the beginning, middle and end in the actual web or app player, at the intended display size. Check fonts or outlined text, masks, layer order and timing where they matter to your design. If a required visual cannot be represented, agree on a simplified animation or another delivery format rather than hiding the mismatch.
Make a short export test before the full render
Use the same destination and settings intended for the final delivery. A tiny test can reveal a mismatch before you spend time exporting the entire composition.
- Record the required dimensions, duration, timing and whether transparency is needed.
- Select a representative section containing text and the important effect or edge.
- Export that section through the chosen documented route.
- Open the output in the receiving player, editor or Lottie runtime.
- Compare the start, middle and end against the composition preview.
- Confirm the result before rendering the full output, and keep the working project separately.
Keep the editable source and deliver the checked output
The maintainer identifies .ecproj as the working project format. A video or Lottie deliverable serves a different purpose from that editable source. Retain needed assets and note the build used for the output so a later revision has a clear starting point.
For an EffectCraft export, choose the destination first and approve a short sample there. This guide is based on current project documentation and editorial checks; we have not rendered an EffectCraft project or measured its output quality.
Questions, answered
Which EffectCraft format should I use for a review?
Investigate a documented video output that the recipient can play, then check timing and appearance in that player.
Does an alpha-capable format guarantee a transparent overlay?
No. Check the chosen profile, export settings and actual result over another background in the receiving editor.
Does every EffectCraft effect export to Lottie?
Do not assume that. The maintainer says the exporter lists features Lottie cannot express; inspect that report and the target runtime.
Sources & checks
Product claims come from provider documentation. Steps and handoff checks are editorial guidance; we have not tested your file in these applications.