Premiere Pro: Thoughts on Using Productions

Posted on by Larry

Last week, my webinar presented a close look at the new Productions panel in Adobe Premiere Pro. (Adobe released it as part of their April, 2020, updates.) I’ve been thinking about this feature a lot since it’s release.

Productions were introduced by Adobe as a collaboration feature. But, even if you are a solo editor, there are significant benefits when using Productions.


A Productions folder is a special folder on your storage that holds projects, or sections of larger projects. This folder can be used by a single editor or a team of editors. Because of how it is designed, you can move and share media between projects without duplicating it.

Also, because of how it is designed, it allows you to work on very large projects in pieces – for example, acts or scenes – to minimize project file size and maximize the performance of your system.

Based on working with this feature for a week, I don’t see any downside to using Productions even as a single editor working with smaller projects. There is a lot to like here.


Create a folder on your storage to hold production folders. This initial folder isn’t required, but I like how it keeps me organized. In my example, my containing folder is called: “Premiere Productions.” You can call this folder anything you want.

Inside this containing folder, use Premiere to create as many production folders as you need. In my example, this is called “First Production” – again, you can call it whatever name you like. You can create as many production folders as you want, however, you can only have one production folder open at a time. There is no limit to the number of projects stored inside one production folder.

Inside a production folder you can only store projects. This is important! Media and other files must be stored outside the production folder. But, when you think about it, most of us are used to storing media in separate locations from our projects.

In the screen shot above, there are project files; lock files, which determine which editor has ownership of the file; a show folder, which contains projects related to a Netflix drama, and a Trash folder, where projects are moved when you decide you no longer need them.

NOTE: When you trash a file in a Production it is not erased, it is simply moved to this folder. Once moved here, you can decide what to do with it later.

The Production folder – First Production, in my example – is exactly reflected in the Production panel in Premiere.

If you are a solo editor, you can ignore all of these – you’ll have read-write access to everything anytime you need it. If you are part of a team, these prevent you from stepping on someone else’s work.

The reason I recommend solo editors look into Productions is illustrated in my Netflix Drama folder. Rather than create a single massive project, I created a project for each act, plus separate projects for graphics, music, and sound effects.

Rather than import all of these supporting elements into every act – making the project file unnecessarily big and unwieldy – whenever I need a graphic, I open the graphics project, select what I need and move it into the appropriate act.

NOTE: Here’s an article on how to move clips between Premiere projects.

If you are editing a series, with common graphics, you can create a single graphics (or music or sound effects) project and access it for as many different projects as necessary without duplicating your files or work.

Open the “master music project,” select what you need, then close it. No wasted effort or storage space. This is a big deal.


In the past, whenever we added a clip to a project, Premiere would create a master clip in the Project panel. Every clip in the timeline needed to link back to a master clip in the Project panel. As I moved clips from one project to another, these master clips were duplicated, taking up room and adding complexity.

With Productions, there’s now only one master clip stored in whichever project you first added the clip. As you move the clip, the Productions folder tracks the clip back to that single master clips. This reduces complexity and allows greater freedom to move clips around.

Adobe spends several pages in their Workflow Guide (see below) describing the advantages of this.

So, with my Netflix drama, I can create massive projects of just sound effects or music or graphics, but only open them when I need to pick something. This means that most of the time, I’m not tying up memory or project files with clips that I will never need.


The part I like best about Productions is that once you open a project and start editing, everything is exactly the same. You don’t need to keep the Productions panel open.

Productions simplifies organizing, storing, finding and accessing your projects. Once you have one or more projects open to edit, close the Productions panel to get it out of your way. Then edit as normal.


Productions are not designed for cloud services, such as Dropbox, Google Drive or VPNs. Projects and media need to be locally accessible.

Be sure both the shared storage and local workstations are synced for time. A good idea is to make sure both are using the same network time server.

Premiere preferences need to be changed to support Productions. The Workflow Guide explains what you need to know.

If you are working as a team, delegate one person to handle all ingest – from cards or tape. This simplifies assigning appropriate metadata during import.

You can convert any single, Shared or Team project to a Production, but you can’t convert a Production to a Team Project. You can also convert a production project to a standalone project by dragging it out of the Productions folder. A potential reason to do this is to share the project file with a remote editor.


Productions are a nicely implemented feature that benefit just about all Premiere editors. It helps us better organize our projects, reduce project size, reduce project complexity and, for those that need it, supports improved collaboration.

I had fun working with it so far and look forward to making it a regular part of my Premiere editing routine.


Bookmark the permalink.

8 Responses to Premiere Pro: Thoughts on Using Productions

  1. Andy says:

    Hi Larry

    Having just had a look at Productions for the first time myself (converting a short documentary project into a Production and testing with that), I’ve run into a few drawbacks that would affect my own workflows. Given that you note above that you’re not yet seeing any downside to using Productions, even as a single user, I thought the following caveats might be useful to some readers.

    1) Search Bins will only work at a project level, not a production level. If you edit projects containing vast numbers of clips, and if in your workflows you use metatdata to log/tag and organise that media (through Search Bin functionality), then be aware that all of your production’s media (or all that you need to be able to search) will need to live within a single project… so, for example, don’t break it down into ‘dailies’ sub-projects if you want to be able to search across multiple days.

    2) Splitting sequences into different projects prevents the ‘Reverse Match Frame’ function from working. ie A match framed clip from a sequence in one project cannot be reverse match framed into a sequnce in a different propject. Hopefully it’s something that can be fixed, but if it’s a function you need now, you need to keep all sequences that need to interact in that manner within the same project.

    3) Clip usage figures are calculated ‘per project’, not ‘per production’. If you tend to use Video Usage and/or Audio Usage metadata to track and guide media usage in your edits, you’ll need to keep the edit(s) you’re tracking in the same project as the media.

    Hope this helps.


    • Larry says:


      These are really helpful comments. I did not think to test/look at search functions in Productions when I was writing this article.



  2. Loren Miller says:

    While Productions feels like it has some utility, many of us storyline editors are already organizing projects in a Premiere Projects folder, so the advantage is?

    More important, many folks I’ve heard from on the community forums are unhappy with the upgrade to 14.1. I myself had to downgrade to keep my 4K functions alive. 14.1 completely cut out my dual D500 GPU support, which makes a couple streams of 4K possible on my system. I would also experience “Error exception” messages including one regarding :”(Advanced Render 2)”

    All very cryptic and unfriendly. So 14.1’s Productions might be an advance for soime, but a disaster for others. Adobe is to be applauded for making a backstop to 14 .04 very easy, but it’s no excuse for less than thorough platform testing.

    Maybe because I’m using High Sierra and not Mojave or Cataline? Maybe, but I’m not going there just yet. And the installer is smart enough to know when you’re trying to install on an earlier OSX.

    Best, as always,

  3. Rob McGreevy says:

    My situation was similar to Loren’s, but in Windows 10. When I upgraded to 14.1 it broke the NVIDIA GPU support for everything Adobe. This is a known bug acknowledged by Adobe. My only options were to shift to software only rendering which exponentially increased my render times or downgrade PP, AE and ME back to the previous versions which is what I chose to do. Productions looks very interesting to me, as I can see advantages to using it in my situation, but until they get the bugs worked out, I’m sticking to the previous version.


    • Larry says:


      Thanks for the update – I’m sorry for all the hassles. Adobe does a great job of creating new features, but they still need to do better on fixing bugs.


  4. Searching within the production is my biggest problem. I’m making a storyboard sequence and want to know if I have imported an asset into the production already. Or where is that sequence I need? The only way I see to search is to open each project separately. I guess I need to create a dynamic catalog or index for reference. I see this discussion is 1.5 years old. Is there a known solution?

    • Larry says:

      Caroling Geary:

      This is a great question, and I’m not sure of the answer. I haven’t looked at productions for a long while. My suggestion is to contact Adobe Support, then let us know what you find out. I know this question of searching productions comes up frequently.


Leave a Reply

Your email address will not be published. Required fields are marked *

Larry Recommends:

FCPX Complete

NEW & Updated!

Edit smarter with Larry’s latest training, all available in our store.

Access over 1,900 on-demand video editing courses. Become a member of our Video Training Library today!


Subscribe to Larry's FREE weekly newsletter and save 10%
on your first purchase.