Apophysis (software)
open source fractal flame editor and renderer

Apophysis is an open source fractal flame editor and renderer for Microsoft Windows and Macintosh.
Apophysis has many features for creating and editing fractal flames, including an editor that allows one to directly edit the transforms by manipulating triangles, a mutations window, which applies random edits to the triangles, an adjust window, which allows the adjustment of coloring and location of the image. It also provides a scripting language with direct access to most of the components of the fractal, which allows for effects such as the animations seen in Electric Sheep, which are also fractal flames. Users can export fractal flames to other fractal flame rendering programs, such as FLAM3.
There is a separate version of Apophysis that supports 3D. There are numerous clones, ports, and forks of it.
History
Scott Draves invented Fractal Flames and published an open source implementation written in C in the early 90s. In 2001, Ronald Hordijk translated his code into the Delphi programming language (Delphi 6) and created a non-animated screensaver. And in 2003 or 2004 Mark Townsend took Ronald's code and added a graphical user interface to create Apophysis. It has since been improved and updated by Peter Sdobnov, Piotr Borys, and Ronald Hordijk.
Since 2009, there is a version of Apophysis called Apophysis 7X. Originally, it was targeting to provide support for modern Microsoft Windows operating systems like Windows Vista and 7.
“Apophysis (software)” enters the record as open source fractal flame editor and renderer. Crown Archives preserves that source wording while asking what Apophysis, software and source can confirm, complicate or overturn.
Why this record matters
“Apophysis (software)” is worth following because a concise public description often conceals a longer documentary argument. Here, Apophysis, software and source provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jan 6, 2026. The linked authority identifier is Q4034218. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2001, 2003, 2004 and 2009.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Apophysis (software)”, its source revision and the description used here.
- Expand the search: follow Apophysis (software) primary sources, Apophysis (software) archive and Apophysis research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Apophysis (software)”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Apophysis (software)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.