The Persistence of Vision Raytracer:
Switch branches/tags
v3.8.0-x.tokenizer.9844488 v3.8.0-x.tokenizer.9841908 v3.8.0-x.tokenizer.9686180 v3.8.0-x.tokenizer.9684878 v3.8.0-x.tokenizer.9675110 v3.8.0-x.tokenizer.9673626 v3.8.0-x.tokenizer.9999 v3.8.0-alpha.9844500 v3.8.0-alpha.9841009 v3.8.0-alpha.9811560 v3.8.0-alpha.9606898 v3.8.0-alpha.9475849 v3.8.0-alpha.9436902 v3.8.0-alpha.9387404 v3.8.0-alpha.9322209 v3.8.0-alpha.9309453 v3.7.1-x.knockout.8881807 v3.7.1-x.diffuse.8587945 v3.7.1-x.dictionary.8884712 v3.7.1-x.dictionary.8877243 v3.7.1-x.dictionary.8791118 v3.7.1-x.dictionary.8790989 v3.7.1-x.dictionary.8790760 v3.7.1-x.colour.8747742 v3.7.1-rc.1 v3.7.1-beta.9 v3.7.1-beta.8 v3.7.1-beta.7 v3.7.1-beta.6 v3.7.1-beta.5 v3.7.1-beta.4 v3.7.1-beta.3 v3.7.1-beta.2 v3.7.1-beta.1 v3.7.1-alpha.8927145 v3.7.1-alpha.8917471 v3.7.1-alpha.8913469 v3.7.1-alpha.8901709 v3.7.1-alpha.8889454 v3.7.1-alpha.8826150 v3.7.1-alpha.8820458 v3.7.1-alpha.8809617 v3.7.1-alpha.8789352 v3.7.1-alpha.8776412 v3.7.1-alpha.8772883 v3.7.1-alpha.8764097 v3.7.1-alpha.8737777 v3.7.1-alpha.8730959 v3.7.1-alpha.8704732 v3.7.1-alpha.8697421 v3.7.1-alpha.8696519 v3.7.1-alpha.8615129 v3.7.1-alpha.8600570 v3.7.1-alpha.8586521 v3.7.1-alpha.8558038+av124 v3.7.1-alpha.8555867+av123 v3.7.1-alpha.8545805+av122 v3.7.1-alpha.8514084+av121 v3.7.1-alpha.8514084+av120 v3.7.1-alpha.8509766+av119 v3.7.1-alpha.8503825+av116 v3.7.1-alpha.8499454+av113 v3.7.1-alpha.8498421+av112 v3.7.1-alpha.8498353+av111 v3.7.1-alpha.8497793+av110 v3.7.1-alpha.8492620+av109 v3.7.1-alpha.8463913+av108 v3.7.1-alpha.8463913+av107 v3.7.1-alpha.8451792+av100 v3.7.1-alpha.8141620 v3.7.1-alpha.8004333 v3.7.1-alpha.7981337 v3.7.1-alpha.7930357 v3.7.1-alpha.7918791 v3.7.0.20140613 v3.7.0.20131220 v3.7.0.8 v3.7.0.7 v3.7.0.6 v3.7.0.5 v3.7.0.4 v3.7.0.3 v3.7.0.2 v3.7.0.1 v3.7.0.0
Nothing to show
Clone or download
c-lipka [parser] Change defaults to no longer be determined by very first `#v…
…ersion` statement.

Instead, subsequent `#version` statements may switch defaults back and forth until the first `default` statement.
Latest commit b5b17ea Sep 19, 2018
Failed to load latest commit information.
.github Update Oct 12, 2017
distribution Fix bug in `f_enneper` inbuilt isosurface function detected by static… Sep 12, 2018
doc/html Update docs. Sep 10, 2017
libraries [ci skip] Some source documentation work. May 1, 2018
platform Get rid of C-style `NULL` throughout the code in favour of the less a… Sep 12, 2018
source-doc Minor update to `source/base/build.h` and related docs. Sep 11, 2018
source [parser] Change defaults to no longer be determined by very first `#v… Sep 19, 2018
tests/source [ci skip] Some source documentation work. May 1, 2018
tools Update git pre-commit hook. Please copy `tools/git/hooks/pre-commit` … Sep 9, 2018
unix Get rid of C-style `NULL` throughout the code in favour of the less a… Sep 12, 2018
vfe [windows] Fix error in recent commit 917a876 that broke the build. Sep 12, 2018
windows Update various comments and a few text strings. Sep 12, 2018
.gitattributes Update to `.gitattribute`; most notably, prevent auto-merging of `sou… Sep 11, 2018
.gitignore [ci skip] Adding /unix/config/ar-lib to .gitignore. (#337) Nov 18, 2017
.travis.yml Change `unix/` to allow running it from the main directory. Jan 5, 2018
LICENSE Initial import Nov 6, 2013 Update maintenance status in May 22, 2018
appveyor.yml Update various comments and a few text strings. Sep 12, 2018
changes.txt [parser] Change defaults to no longer be determined by very first `#v… Sep 19, 2018
revision.txt Update change log. Sep 12, 2018

POV-Ray - The Persistence of Vision Raytracer

Semaphore Build Status AppVeyor Build status Travis CI Build Status Coverity Code Analysis Maintenance Status


As of version v3.7, the source for POV-Ray is licensed under the AGPL3. The documentation is under the Creative Commons Attribution-Noncommercial-ShareAlike 2.5 license, and support files such as SDL includes, macros, sample scenes and so forth are under the Creative Commons Attribution-ShareAlike 3.0 Unported License (see each file header for the specific one).


Discussion regarding POV-Ray is traditionally done via our forums at These are also available via NNTP at news:// for those preferring that.

Please note that the POV-Ray developers do not monitor all forums regularly. The ones we tend to check most frequently are povray.general, and povray.unix.

Bug Reports

It's generally a good idea to mention a bug in the forums prior to lodging a formal report; this can save you some time if it's a non-bug or a solution is known. You should also first check the known issues to see if it has been reported already.

If you're sure something is a bug then please do lodge a bug report on the GitHub issues tracker.

Official Binaries

At this point in time, the only platform for which the project distributes pre-built 'official' (i.e. supported) binaries is Microsoft Windows. These may be obtained via We do intend to provide Mac OS X binaries shortly, but these will be console-mode only (based on the unix build).

Official Windows binaries of selected development versions are made availabe at on a semi-irregular basis.

Building POV-Ray

At this point in time we generally recommend building from the latest version of the latest-stable branch. Alternatively, you may want to opt for a recent tagged version to test-drive features that have been added since the latest stable release.

Please do not build directly from the master branch (or any other non-stable branch for that matter), as versions from that branch may report ambiguous version numbers, making it difficult to obtain version-specific support or report bugs in a useful manner.

POV-Ray should compile on any POSIX-compliant system with the required tools (please see unix/ for build instructions), on Microsoft Windows systems that have Visual Studio 2015 Update 1 or later installed (targeting XP or later, both 32 and 64-bit - be sure to see windows/, otherwise your build will not work), and also on Mac systems (console mode only, using an appropriately-modified version of the unix build - not currently provided by us).

If you are using an operating system with a package or ports system such as Ubuntu or FreeBSD, you may like to check whether or not POV-Ray is available via that route.

IDE versions

Currently the only version of POV-Ray with an IDE as such is the Windows build. We do want to change that, though. With the release of POV-Ray v3.7 we have added a clear split between the backend (renderer) and frontend (UI or console), along with a C++ layer which abstracts this into a fairly easily-understood set of classes (VFE, aka 'Virtual Front End').

We will offer support to those wishing to use this interface layer to integrate POV-Ray into an open-source cross-platform IDE. We would also be interested in hearing suggestions as to what we could base such an IDE on, should we go ahead to integrate it ourselves.

Putting it another way: we consider getting a cross-platform IDE a high priority.

3D Modeller

POV-Ray does not currently have its own 3d modelling application (at least, not one in a usable state). We do own the rights to the Moray modeller, which was formerly commercial, but it needs a little work to get it working with v3.7 or later. It is also Windows only (due to its use of MFC). Nevertheless we will be adding the source to the repository at a future date.

Authors of open-source modellers with a compatible licence wishing to directly integrate POV-Ray are welcome to contact us for support in doing so.


When built and installed via the means provided in the source tree, all versions of POV-Ray come with documentation. For the Unix build, this is in the form of a manpage giving basic usage, and full HTML-based documentation. For the Windows version, there is a HtmlHelp (.CHM) file provided.

The official location for the online documentation is Further information, as well as online documentation for the current development version, can be found at

Contacting Us

We prefer that you contact us via the forums mentioned at the head of this document. If the matter is one that requires direct email contact (and this generally will NOT include tech support requests, though exceptions are made for package maintainers) you may use the address listed at the bottom of