Plastic SCM features


  • Filter by:

  • 5.4

    5.4 – The “cutting-edge” version including all the latest improvements. You can find it under “labs” in our downloads section. It is stable and already in production in several major companies.

  • 5.0

    5.0 - The main stable realease. It still receives small features upgrades and tweaks.

  • 4.1

    4.1 – The oldest one still in maintenance, rarely releasing new versions.

Branching & Merging

Branching & Merging

Good branching and merging is key for “task driven development”, feature branches and good release management.

Using Plastic you’ll branch fast even with huge code bases.

You’ll handle merge cases that no other tool can deal with.

You’ll be able to diff and merge refactored code using Xdiff/Xmerge (included with Plastic) and our SemanticMerge, the only language-aware merge tool and the first step in our “semantic version control” initiative.

And since an image is worth 1000 words, you’ll visualize the merges using the Branch Explorer

New in 5.0 Item merge tracking helps understanding merges when running diffs, annotates and displaying the 2D version history of a file.

Distributed, multisite and centralized

One of the key reasons why teams move to Plastic is its ability to work in distributed mode. Distant offices can be seamlessly connected, developers can work from home and you’ll still be able to scale up to handle hundreds of developers working onsite. Find more details in the Distributed guide.

Fully distributed

Fully distributed

Using Plastic a developer can have a clone of the repository on his local machine and checkin, branch and merge without connection to the main server. This is what fully distributed is about.

The benefit is clear in terms of speed, enabling developers to work from home without suffering slow VPNs or being hit by a network issue. Developers can pull and push changes to any other Plastic server (depending on the permissions) anytime. In extreme distributed environments, developers wouldn’t even use a central server. However, in practice, a central place will be used as rendezvous point.

Fully distributed



It is very common to have teams working on different cities, sometimes even in different continents. They work on a shared codebase, so it is good to have a server at each site, and replicate changes between servers.

If the server is only at one of the sites then all the others will suffer from slow response, even if they use some sort of proxy server (which used to be the solution in the old days). Plastic applies the distributed tech to enable teams to get the best out of distributed (connect servers) + centralized (developers working at each site checkin locally) approaches.




Some teams need to benefit from the powerful branching and merging of DVCS but don’t want to have a clone of the repository (or repositories) on each machine.

Using Plastic you can do both distributed (checkin-push workflow) and centralized (just checkin to the central, old Subversion style). Some team members can work centralized while others use a distributed setup concurrently.


Graphical User Interface and Visualizations

Plastic is much more than a scalable core and a great merge engine. Everything we do has the end user in mind, and making things simple and visual is key for us.
  • GUI

    Plastic allows you to perform every version control operations from the GUI, which is pretty easy to learn. User experience is our most important goal.

  • Branch Explorer

    It is the core feature of the GUI. It is an interactive graphic that renders the evolution of the repository. From the Branch Explorer you can branch, merge, diff, push and pull and switch to different branches. If there is a single feature that makes Plastic worth, this is the Branch Explorer. Find more here.

  • Built-in Code review

    Plastic ships with an integrated code review system. You can create reviews from changesets and branches, add comments to lines and assign the review to a developer to check it. Reviews are replicated between repos with their branches. Find more in the GUI guide

  • Version tree 2D

    You can display the history of a file visually using a 2D version tree. Then you can follow how it was branched and merged, and run diffs from the diagram. Check the GUI guide for details.

  • Annotate/Blame

    This view shows who wrote every line of and file. Each line is annotated with the date, the changeset and the branch. Additionally the annotate displays the line age and it can summarize the file age and main contributors.

  • Built-in side by side diff

    Plastic includes a built-in diff tool, Xdiff, which can be invoked as a separate tool but it is also used inside the GUI to show side by side differences. It has the ability to track moved text (even when it has been modified). You can find this in Plastic, inside the pending changes view, diffing changesets or branches or running code reviews.

  • Built-in 3 way merge with refactor detection

    Plastic comes with its own 3-way merge tool called Xmerge. Besides being a regular merge tool, it has the ability to track and merge moved code fragments. Plastic also lets you plug any other 3-way merge tool like Araxis, BeyondCompare, our own SemanticMerge and many others.

  • Diff window - branch, changeset and label diff

    Each time you need to diff branches, changesets or labels you’ll use the Diff Window. It is a very complete interface that will show changed, added, deleted, moved and also files that have been merged in the changesets, labels or branches you’re diffing.

  • Image diff

    Plastic includes a image diff tool, able to compare two revisions of the same graphical file. The file can be in a variety of file formats (specially if you have ImageMagick installed). This tool can show images side by side, do an “onion skin” preview, calculate differences, do a “swipe” and also diff the image properties in text format.
    More details in the GUI guide.

  • Image preview in the workspace explorer

    When you browse the files in your workspace you can preview the image files and read the extended properties stored on it. Plastic can be configured to use ImageMagick to generate the previews of hundreds of different formats. You can even write your own custom previewer to support custom file formats (quite common in game development). It will also be used to diff image files.

Plastic Gluon - Version control for artists

Plastic Gluon is the version control designed and crafted for artists in game development. New in 5.4
Plastic Gluon screenshot

Performance & scalability

Checkin, update and merge as fast as possible. Handle hundreds of concurrent developers using the same server. Manage huge files. These are the things you can do with Plastic.
  • Scalability under heavy load

    Check how Plastic performs when 300 bots checkin at 2000 checkins per minute. Scaling up on centralized setups is key for many teams, and core to Plastic.

  • Improved blob storage New in 5.4

    Big blobs (configurable size) can be stored in the filesystem instead of the database for storage optimization and performance.

  • Single port operation & binary protocol

    All data transfer between the Plastic client and server uses an optimized binary protocol that compresses all metadata to speed up communications. All connections between clients and servers happen through a single TCP port (several can be configured if needed, but only one is needed by default) which makes the server very easy to configure and secure.

  • Proxy server

    Although Plastic is a full featured DVCS capable of replica, we also provide a proxy server (or cache server) to reduce data traffic to the central server. We don’t recommend this setup for multi-site but for high demand, heavy load scenarios where reducing data traffic on certain network segments can greatly improve overall network performance. Check this blogpost for more details.

  • Fast-update New in 5.4

    Standard Plastic update (download files to the workspace) walks the entire directory tree looking for changes. It is very efficient, but teams with really large codebases (>500k files) can end up experiencing slower IO and slower updates. That’s why fast-update just applies differences on disk, avoiding the full scan. Going from cset 3000 to 3014? It just calculates the differences and applies them on disk, reducing disk IO and improving speed.

  • Archiving – External storage

    You can extract revisions of large files from the database to be stored in secondary storage. Once archived the revisions can be accessed in two ways:

    1. Transparently for the users when the server is setup to find archived revisions on external storage.
    2. Prompting the user to insert the right media on his workstation (useful if your team uses an asset library in different media)
  • WAN optimized data transfer New in 5.4

    Teams with servers on different continents replicate branches through high bandwidth but high latency networks. The “WAN network channel” typically improves data transfer speed by 3 with 200ms latencies compared to regular TCP. This is very useful for companies replicating big files between different teams across the globe. Find more here.

  • Multi-thread checkin and update New in 5.4

    Checkin and update can be configured to use multiple threads. This way data compression and decompression will run in parallel with network and disk IO operations, greatly improving overall operation performance as you can you can find here.

  • Configurable database backends

    Plastic stores all data and metadata in standard database backends. The default installer uses SQLite on Windows, Linux and Mac. You can easily configure it to use SQL Server (including Express), MySQL (and MariaDB), PostgreSQL, Firebird (both embedded and server) or Oracle. This flexibility allows you to run a tiny and extremely Plastic server using SQLite on your laptop, or take advantage of a corporate server with SQL Server or MySQL.
    SysDBAs have the flexibility to setup clusters and apply optimizations since Plastic uses standard SQL structures. Backup is done with standard tools too. Blobs are stored in 4Mb chunks, compressed, and there’s an option to store them on the filesystem (or SQL Server FILESTREAM fields).

  • Configurable database backend table

    Full test suite - pass an entire unit + smoke test cycle - it means thousands of unit tests and hours of automated command line testing every release. Performance tested - ready for super fast single user access. Fast checkin/update cycle. Tested under heavy load - it means it has been tested and tuned to handle hundreds of concurrent users as described here. * SQL Server CE - perf - slower than sqlite

Component oriented development

You can use and develop shared components in Plastic using Xlinks and submodules.
  • Xlinks

    Cross-links are the way to link together different repositories, potentially creating a hierarchy of components shared among different projects. An Xlink is a special directory entry that points to a given changeset on a different repository (potentially on a different server). The contents of the Xlink will be transparently downloaded to the user workspace. There are read-only Xlinks which are meant to handle dependencies that rarely change, and writable Xlinks to handle parallel development across a codebase made of several repositories. Branching and merging is handled by Plastic on writable Xlinks.

  • Submodules New in 5.4

    By default Plastic stores every repository on a different database (except for Oracle where a new “user” is created). Submodules allow admins to store several repositories inside the same physical database which is useful both for database administration and to create repository namespaces in organizations with hundreds of repositories. Submodule repository names look like “graphics/opengl” and “graphics/directx” instead of just the single name given to a repo.

Note: if you’re familiar with Git modules, then Xlinks are like merge-aware Git modules.


There is a number of features that help you on a daily basis when you’re working with Plastic:
  • Transparent SCM

    You can program using your favorite IDE/editor and Plastic will detect the changes you’ve done. You change a file and Plastic detects it. You move a file, a directory and Plastic also detects the move, perfectly tracking it even when the file was changed. This is what we call transparent scm and basically allows you to forget about the version control until you have to checkin and them Plastic will do its part, detecting even complex changes.
    Find out more

  • Client changelists New in 5.0

    This features helps you to organize the pending changes (to be checked-in) in your workspace with user defined categories. One of the goals is to make the Perforce users feel at home.
    Check the guide for more info.

  • Shelve (a.k.a. stash)

    You can “shelve” changes in Plastic and keep them saved in the server (not checkedin) until you apply them later on. You can shelve several files together and give them a description. They’ll be applied using merge, so it is a good way to apply changes to a different branch.
    Find more in the GUI guide.

  • Exclusive checkout (locking)

    There are files that can’t be easily merged or even merged at all, like images, animations, simulation data, 3D files and many more. Using Plastic you’ll be able to simply exclusive checkout (lock) these files to avoid them to be modified concurrently. This is key for many industries, like game development.

  • Attributes

    You can create your own metadata in the form of name/value pairs, attaching it to any object in the repository. This enables you to create sophisticated reports, using data retrieved by SQL queries. Check the Find guide. Later, you’ll be able to see the attributes in the GUI in places like the branches list, the Branch Explorer and more.

  • Transformable workspaces New in 5.4

    Sometimes you need to apply some transformations to your working copy that you don’t want to checkin. For instance you need the “/extlibs/includes” to show up inside “/includes/extlibs” in your local copy. All this, and a lot more, can be achieved with “transformable workspaces”.

  • Improved cloaked rules New in 5.0

    Cloaking rules (defining cloaked.conf) lets you avoid some paths (files or directories) to be updated or downloaded at all. Now with simpler rules you can define flexible rules to include or exclude certain paths.


Being able to set permissions to repositories, branches, labels, paths is not only good to secure the codebase but also to enforce policies and best practices like “don’t directly checkin to the release branch”.
  • Fine grained security with Access Control Lists (ACL)

    Using Plastic you can set permissions to branches, labels, repositories, paths and even the server itself. Objects inherit in a hierarchical way (repository inherits from server, branch from its repo) so it is possible to configure very fine grained and flexible security policies. There is a list of more than 30 version control specific permissions like add, change, move, checkin, mergefrom, applylabel and more. Learn more here.

  • Path based security New in 5.0

    You can set permissions (ACLs) to specific paths so that they’re always checked before performing certain operations. For instance, it is possible to deny the “ci” and “add” permissions at “/build/ scripts” for everyone except the “makefile masters” so that nobody messes with the build scripts. Path based permissions introduce a number of new possibilities together with the regular object ACLs.

  • Active Directory, LDAP and other authentication systems

    Companies can integrate Plastic with their Windows Active Directory or LDAP system so that users, groups and authentications are handled by the operating system and not by Plastic. This way there is no need to import users periodically and any change in group assignments will be immediately detected by Plastic. Built-in user/password is also available for groups that don’t use LDAP/AD or need to be independent from the IT department.

  • SSL

    Every Plastic server listens by default on a single TCP port, which makes it easy to configure and secure. It can be configured to listen on more ports including SSL, thus securing the communication between clients and servers or between different servers during replica.

  • Auditing and compliance

    Plastic keeps a configurable audit trail that register all important events happening in the system. Check this article to find how to comply with Sarbanes Oxley.

  • Encrypted servers New in 5.4

    This feature enables teams to use public servers because data will be stored in an encrypted way so even if the server is compromised the attacker won’t be able to access the original files. The mechanism is simple: you configure your team (or local) server to encrypt any file data being transferred to a given external server. It will also be decrypted while receiving from the encrypted server. The key will only be stored on your machine so unless it is compromised the data will be secured on external servers.


Version control is a cornerstone tool in the software development process and as such many other tools extract data and interact with it.
  • IDEs

    Developers using Visual Studio can take advantage of the “VS Package” included in the Plastic installer. Inside the IDE you can checkin, checkout, branch, merge, show the Branch Explorer and basically do everything the GUI can do. We support all versions back from the SCC days till the newest Visual Studio 2013. The VS plugin includes unique features like "semantic history".

    Eclipse programmers will use the Repository Provider that implements the key version control capabilities integrated in the IDE. We recently added a Java based Branch Explorer too. We support up to Eclipse 4.4 Luna.
    Plastic is well-known to work great with PowerBuilder and other IDEs compatible with SCC including MatLab.
    Plastic also works with IDEs compatible with the newer VS Package system like Atmel Studio.
    Same holds true for Eclipse-based IDEs such as LPCXpresso and Eclipse RCP.
    IntelliJ and Android Studio developers also have a native Java plugin to perform the most common version control operations.

    Developers using any other IDE can take advantage of transparent scm which basically detects any changes in your workspace included files and directories being moved and renamed. It means you can simply work in your preferred editor and then switch to Plastic “pending changes” view, find the changes and checkin.

  • Issue tracking and project management tools

    Teams embracing agile will most likely be working with Rally, VersionOne or JIRA. They are fully supported and also Bugzilla, Mantis, Trac, OnTime and FogBugZ. Redmine, YouTrack and ALMs like Polarion are also supported. Adding a new one is not hard, so do not hesitate to contact us, even if it is a in-house one.

    Continuous Integration (CI) and DevOps

    You can integrate Plastic with a variety of tools inside your build and deploy ecosystem. Plastic can be integrated with Jenkins/Hudson, JetBrains TeamCity, Pulse, FinalBuilder, CruiseControl, Atlassian Bamboo. You can also integrate Maven using the Plastic SCM plugin.

    Code review systems

    Code reviews are key in “task oriented development” and as such you’ll be able to use Atlassian Crucible integrated with Plastic. Plastic includes its own integrated code review system too, which you can use from the GUI or the WebUI.

    Unity plugin

    If you develop with Unity you can use the Plastic integration with Unity. Find more here.

  • Microsoft Office (Word and Excel)

    You can use the Office plugin to checkin, checkout and view the history of files while working inside Word and Excel. Word diff and merge (invoking MSWord as diff and merge tool) is also available out of the box.

  • Windows Explorer integration

    If you ever used TortoiseSVN (or any other Tortoise*), chances are you miss performing checkouts, checkins and even merges from the Windows Explorer. The Plastic installer includes a Shell Extension (or Explorer integration) that basically is able to perform the same operations as the GUI but all available as a context menu on the Windows Explorer.

Sync with other version control systems

You’ll be able to keep Plastic repositories in sync with Git and Perforce and also import and export
using the fast-import/export de-facto standard.


GitSync New in 5.0

This is how we called the bi-directional synchronization between Plastic and Git. Basically Plastic can talk the Git network protocol and then push and pull packages to a remote Git server. From the Git side it is pretty transparent since Plastic totally adheres to the protocol, so the remote Git server *thinks* it is talking to a regular Git process. Using GitSync you can push merges from Plastic to Git (and viceversa) and they’ll be perfectly valid.

The great thing about it is that it is not a “migration solution” that only keeps a single branch in sync, you can basically do things like use the Plastic GUI as a Git client and interact cleanly with other team members using Git. Plastic internal structure is close enough to Git’s that it is totally possible to exchange all commits (changesets in Plastic jargon), branches and merges between them.

Git is a trademark of


P4Sync New in 5.4

P4Sync is a bidirectional synchronization with Perforce to help teams using P4 migrate to Plastic.

Since big migrations are complex and sometimes big organizations move team by team to Plastic, there’s a period when there are developers already in Plastic and developers still in P4. But development can’t stop, so we created a way to keep a P4 branch fully synced with a Plastic branch. This is P4Sync. P4 and Plastic are structurally different so only one branch can be kept in sync. This is clearly a solution designed only to help during the transition phase.

Perforce is a trademark of Perforce Software, Inc


TFSSync New in 5.4

TFSSync is a bidirectional synchronization with Team Foundation Server to help teams moving away from TFS during the transition phase.

Like P4Sync it can only keep a single branch in sync between the two systems and it is specifically designed to help during migrations.

TFS (Team Foundation Server) is a trademark of Microsoft Corporation



Plastic is able to import any version control history using the fast-import format, which is the de-facto standard created by Git. Anything that can be imported to Git can hence be imported to Plastic.

We have helped customers to migrate from Hg, Subversion, CVS and others using this method.

Plastic is also capable of exporting to fast-export format (besides GitSync!) which basically means that if you ever need to move away from Plastic you’re free to go.

Learn more about the fast-import/export operations.

If you need to use TFSSync or P4Sync, please contact our support team


Plastic SCM is a multiplatform version control system. You can run client and servers on Windows, Linux and Mac OS X, and there are also solutions for other Unix platforms.



All Windows versions are supported, including Windows 7, 8 and all server variants. In fact, we preserve an ancient W2K server to run GUI and CLI tests on a daily basis. You can find all the available installers and bundles in our downloads page.

Windows is a trademark of Microsoft Corporation



You can install Plastic servers and clients (including GUI) on different Linux flavors. We have packages for the most common distros.


Mac OS X

Mac OS X

Mac OS 10.7 and higher are fully supported to run both clients (including GUI) and servers. View more

We discontinued support for PPC based processors long ago.

Mac OS X
Mac OS X is a trademark of Apple Inc.



While we don’t provide official packages for OpenBSD or FreeBSD we have tested Plastic on both OSs. You can install it taking advantage of the ZIP packages that include the binaries in a platform agnostic way.

  • 64bits and multi-core support

    Clients and servers are optimized for 64bits hardware so you can take advantage of installations with large memory configurations. The Plastic server is multi-threaded to take advantage of multiple cores and processors.

    New in 5.4 The client also takes advantage of multicore to upload and download data in parallel.

  • JavaCLI New in 5.4

    It is a Java based Command Line Client (CLI) that is cross-compiled from our regular CLI source code. Teams that need to deploy to HP-UX, Solaris or other Unix flavors use JavaCLI to automate commands on those platforms.

  • Fully compatible client and servers on different operating systems

    As expected it is straightforward to connect clients and servers running on different operating systems and even using different authentication methods – like a Linux client connected to a Windows Plastic server using Active Directory. The data transfer works between hardware with different endianess.

One of the key features in Plastic SCM is performance, and the 3 main platforms: Windows, Linux and Mac, perform great even under heavy load

Semantic version control

We believe that version control is in a unique position to offer developers many more tools for the job. It stores a lot of history that correctly organized can really help in daily operations. That’s why we created SemanticMerge first and then we applied this technology to the version control itself... This is just the beginning of what is to come.
  • Semantic History New in 5.0

    90% of the times you go through the history of a file you are actually looking for the history of a given method or function. Semantic History (available for C# and Java right now) lets you select a method and find how it was modified through the history of the file. It parses the code and it is able to find the method even when it has been moved, renamed or heavily modified through history.

    You need the .NET 4 release (available in the downloads area) to use this feature both from the GUI and the Visual Studio Package. It can track methods, properties, constructors, members and more.

  • Next steps

    It all started with Xdiff/Xmerge, able to track moved text (language independent) and then continued with SemanticMerge. Our next goals are:

    • Semantic Repo History: to track methods moved across files.
    • Multifile SemanticMerge: the *real* Semantic that will be able to merge methods that were refactored across files too.
    • Semantic blame/annotate: to give the programmer extended info of each line of code and method while he types on Visual Studio, warning him about code that has a long and complex history behind, bugs and more.

Release early, release often

We create new Plastic SCM releases on a daily basis and we normally publish them once a week.
Every new release includes new features and fixes. We try to move as fast as our customers do.

    Currently we have 3 major versions in production:

  • 5.4 – The main stable release under active development. 5.4 has been around for quite a long time and it is the default version to download.
  • 5.0 – no longer the main version, it rarely receives fixes.
  • 4.1 – the oldest one still in maintenance, rarely releasing new versions.

Get the latest news