A collaborator sends a Cubase project. You run Pro Tools. The usual answer is to ask for stems, wait, receive them misaligned, and rebuild the arrangement by hand. The alternative was AAF or OMF, which loses most of what made the session useful.
WG DAW Converter takes a different route: it reads the session file directly. No intermediate export format, and — the part that matters most — no need for the source DAW to be installed. You do not need a Cubase licence to open a Cubase project, because the converter parses the file itself and writes out whatever the destination application requires.
Supported applications include Pro Tools, Cubase, Nuendo, Logic Pro, Ableton Live, Studio One, FL Studio and REAPER, with conversion running between them rather than through a single hub format.
For studios receiving work from clients on unknown platforms, that removes the licence problem entirely.
Hurry and get discounts on all VST Plugins up to 90%
Original price was: €49.99.€29.99Current price is: €29.99.
Download instantly from PluginsBoutique
To pick up todayAccess your plugins immediately
Instant Digital Delivery
Your download link will be sent instantly to your email.
Free 2-Day returns if not work
Payment Methods:
Session interchange has been an unsolved problem for as long as there have been competing DAWs. Every studio has its own reason for choosing one, and none of those reasons help when a client sends a project file the studio cannot open.
Two workarounds have dominated. Stem exchange means bouncing every track to audio, sending a folder of files, and rebuilding the arrangement manually at the other end — losing automation, plugin settings, fades and clip structure along the way. AAF and OMF preserve rather more, but they were designed for video post-production rather than music, they handle a limited subset of session data, and both applications still need to support the format properly.
WG DAW Converter, announced in 2026 and covered by Production Expert at launch, works differently. It reads the session file itself and exports to the format the destination application needs. There is no intermediate hub format and no dependency on the originating software. Pro Tools, Studio One, Ableton Live, Cubase, Nuendo, FL Studio, REAPER and Logic Pro sessions can all be read directly.
Not requiring the source DAW is the design decision that changes the economics. Studios have historically maintained licences for software they never use, purely to be able to open incoming client sessions.
Removing the licence dependency is the strongest argument. Keeping a second or third DAW installed and authorised, purely as a translation step, costs money and disk space and adds an update burden for software nobody actually mixes in. Reading the file directly makes those licences unnecessary.
Direct parsing also avoids the losses that an intermediate format introduces. Every conversion through a common exchange format is bounded by what that format can express, and anything outside its specification is discarded regardless of whether both DAWs support it. Reading source and writing destination directly removes that ceiling.
Third, breadth of support matters more than depth for this kind of tool. A converter handling only two applications is useful occasionally; one covering the eight most widely used DAWs is useful whenever a project arrives. Mixing engineers, mastering engineers and post facilities receive work from all directions.
Fourth, it is a standalone utility rather than a plugin. It does not need to load inside a host, which is precisely the point when the problem is that you cannot open the file in the first place.
The purchase covers the WG DAW Converter application with support for the listed session formats in both directions where the destination format permits.
Because supported applications and versions expand over time, confirm current coverage on the developer’s own page before relying on a specific pairing for a deadline.
The audio file point is the one that catches people out. A session file is a description of an arrangement: which clips play, where, with what processing. If the recordings it points at are not present, the conversion will produce a correct arrangement referencing missing media. Always collect the full session folder, not just the project file.
Treat verification as a required step rather than an optional one. Session structures differ between applications in ways no converter can fully reconcile, and a five-minute check against the source arrangement is considerably cheaper than discovering a timing offset after a day of mixing.
Documented support covers Pro Tools, Studio One, Ableton Live, Cubase, Nuendo, FL Studio, REAPER and Logic Pro — effectively the applications that account for the overwhelming majority of professional and project studio work.
Set expectations correctly around plugin state. Third-party processing does not transfer between DAWs in any meaningful sense, because the destination application must have the same plugins installed and the session formats express plugin state differently. Expect arrangement, timeline and media to carry across, and plan to rebuild processing chains at the far end.
Anyone working entirely alone in one application will get nothing from this. It solves an interchange problem, and interchange only becomes a problem when other people are involved.
The clearest saving is in rebuild time. Reconstructing an arrangement from stems means importing dozens of files, verifying every start point, recreating fades and hoping nothing drifted. Converting the session directly delivers the arrangement already assembled, which turns a morning’s work into a few minutes.
Eliminating redundant licences has an ongoing effect as well. A studio no longer needs to buy, install, authorise and update software it does not mix in, simply to act as a translation layer. That is a recurring cost removed rather than a one-off saving.
Collaboration also stops being constrained by platform. When a session can move in either direction, the question of which DAW a collaborator uses becomes irrelevant to whether you can work with them — and that widens the pool of people a studio can take work from.
No. The converter reads the session file directly, which is the central feature of the product.
Pro Tools, Studio One, Ableton Live, Cubase, Nuendo, FL Studio, REAPER and Logic Pro.
No, it is a standalone application. A plugin would need a host, which defeats the purpose.
Those are intermediate exchange formats with a fixed and limited specification, originally designed for video post. This reads the native session file and writes the native destination format.
Do not count on it. Plugin state does not translate reliably between DAWs, and the destination system would need the same plugins installed. Plan to rebuild processing chains.
The session references audio files, so you must supply the complete session folder including the audio directory rather than the project file alone.
Support varies by format pairing. Verify the converted session against the original before starting paid work.
Conversion runs between supported applications rather than one way only, subject to what each destination format can express.
Save the converted output to a separate folder. Keeping the source untouched is standard practice regardless.
Yes — you need the application you intend to work in. What you do not need is the one the session came from.
Track count, clip positions, fades and overall timeline alignment against the source arrangement.
The documented support list covers music DAWs. Check with the developer for anything outside that list.
Supported formats expand over time. Confirm current coverage on the developer’s page.
WG, whose converter was announced in 2026 and covered by Production Expert at launch.
Most attempts at session interchange have tried to invent a common format everyone agrees to write. That approach keeps failing, because the format can only ever express the intersection of what all the applications support, and because it requires the sending application to cooperate.
Reading the native file directly sidesteps both problems, and removing the source DAW requirement turns a workflow tool into a licensing one. For any studio that has ever kept an application installed solely to open other people’s projects, that is the feature that justifies the purchase on its own.
Related production software is listed under DAWs, with processing tools under Mix & Master Plugins. The current supported format list is maintained by the developer at wg-apps.com.
In stock
No account yet?
Create an Account
Reviews
Clear filtersThere are no reviews yet.