Hi Neil Allen

There is only a 32 bit version of Trados Studio at the moment.

A 64 bit release is on the backlog and is being considered but there is no timeline as of yet.

Seemingly still on the backlog 4 years later. Is this at all being considered at this point?

Fredrik Nylund 

As we say all the time, every release gets closer.  Moving to 64-bit is only going to be effective once we have completely replaced all the parts of the software that could be a bottleneck.  As so many "knowledgeable developers" in these forums tell us all the time it's simple to move to 64-bit.  And it is... but pointless if the software cannot take proper advantage of it.

So yes... of course it's being considered and if we thought it would really help we would have done it already.

Yes it is still a consideration and the pre-requisites are in progress. The Editor has been rewritten recently to use a more modern technology that is compatible with 64bit. That was a huge undertaking and a blocker to 64 bit support, which also made it support much bigger files.
We are currently porting to dotnet 6 which will make things easier.
Its more a case of replacing dependencies that will not work in 64bit and re-structuring. 
So all the work helps and eventually we will just be able to do the simple switch, that people keep referring to.

Looking forward to a 64 bit version and the refactored Editor. For me, a reason alone to purchase the upgrade to the next version.

I did not care too much about it until last week's project: a huge volume that would raise "Not enough memory" errors as soon as the files were loaded in the Review interface. This, just after a fresh reboot of a 32 Go laptop with only Studio and Antidote running. It is a nasty error as it lets you work in the Editor but will not save the file.

Strangely enough, the editor in Translation mode often works while it struggles in Review mode with high volume projects. Does the Review interface use notably less memory or is it caused by my window layout? I have experienced this many times, had sometimes to review content in Translation mode, then set the statuses in bulk before delivery. This is why the new Editor is good news.

Looking forward to a 64 bit version and the refactored Editor. For me, a reason alone to purchase the upgrade to the next version.

I did not care too much about it until last week's project: a huge volume that would raise "Not enough memory" errors as soon as the files were loaded in the Review interface. This, just after a fresh reboot of a 32 Go laptop with only Studio and Antidote running. It is a nasty error as it lets you work in the Editor but will not save the file.

Strangely enough, the editor in Translation mode often works while it struggles in Review mode with high volume projects. Does the Review interface use notably less memory or is it caused by my window layout? I have experienced this many times, had sometimes to review content in Translation mode, then set the statuses in bulk before delivery. This is why the new Editor is good news.