Under Community Review

64-bit version of Studio

Please create a 64-bit version of Studio. At present only a 32-bit version is available, and therefore it can theoretically only access 2-3GB of system memory, meaning that upgrading your machine with more memory then this does not have any beneficial impact on Studio performance.

When handling large files & projects, allowing Studio access to all of your system's memory would make a huge difference in time and performance, and for this the app needs to be 64-bit.

Are there any plans to release a 64-bit version in future?

Jay Young
  • in reply to Giovanna COMOLLO

    For what it's worth, I have completely given up on this issue being resolved within my working lifetime (I'm retiring in 2026). My solution is to retain the use of Trados Studio for compatibility with the workflow of clients who use it, but to import the sdlxliff (the segmented one in the directory \projects\project name\language-variant) into MemoQ, together with the memories. This is a quick operation that means that I work in an environment that does not crash, is fast and has much better "intelligent" search and replace for faster post-editing.

    When the translation is done, just export to the same directory, open it in Trados, and deliver to your client. All QA and all other processing is done in MemoQ and XBench.

    I am currently doing a project with around 450,000 repeated segments and I dread to think of the problems it would cause in Studio.

  • in reply to Giovanna COMOLLO

    Glad to read 32 bits are enough and work fine for you, but it is not sufficient for many of us. 

    It seems you never see studio suddenly stop working and disappear from your screen in the middle of a doc, with unsaved segments, or do not undergo unavailability times when the autosave functiom runs (which should be a background transparent process, like in, e.g. Word), or have to wait long minutes when performing certain processings on large files or series of files or when accessing to large memories. Most of those issues relate to available RAM, or to its use, which is directly linked to the 32-bits vs 64-bits issue.

    With a limited RAM, Studio (like any other RAM intensive software) has to continuously swap data between that limited RAM and your far larger HDs or SSDs, instead of keeping all needed data in its instantly accessible RAM, which, at the end of the day, is a waste of time and can produce errors.

    I dream of an update of Studio without any new marginal feature, but with a focus on evolving to 64-bits and fixing some bugs that are still in the landscape after years, such as the index issues when merging 2 segments or hexadecimal characters in a comment that can prevent to reopen a file, which should never occur.

    And since we are at the AI era, it could be great to use it for tracking and solving those bugs, rather than dedicate it only to automatic translation.

  • in reply to Giovanna COMOLLO

    That is EXACTLY what I work on. Multiple large files, often into the hundreds of megabytes, which grows exponentially in Trados' use of memory capacity. Without a 64-bit version Trados crashes daily, frequently losing TM entries (fortunately not whole TMs, because I use GroupShare TMs). This is becoming unbearable...

  • I use it on a 64-bit PC and it works allright. I often encounter small issues, but they can generally be solved fairly quickly. There are many other issues that make Trados slow and hard to use with confidence. Not 64-bit PCs. Unless you work on very very large projects.

  • in reply to Renato Colonna Rosman

    This is incredible - this post has been out there for 6 years. There have been several new Trados Studio versions since then and STILL no 64-bit support. MOST of the projects I work with are made up of dozens or even hundreds of XML files, with incredible amounts of cross-file repetitions and I always work on them by opening them all at once. This usually crashes Studio. This happens every single day. No amount of developers sayin there's a workaround or that they are investigating this idea will change the fact that this system has become so unstable due to the RAM restrictions that I am actually really considering stopping buying any future releases - the 2022 version for both myself and my linguists + a GS 2017 will have to suffice.

    The ONLY feature I am looking forward to is the 64-bit support. No bells and whistles, just the thing that you've been contemplating for the past decade. Just do it, for Pete's sake. As evidenced from other users' replies, the 64-bit version is THE priority for the majority of Trados users, and yet you decide to tackle anything and everything else before you get to this. Is the source of the Trados Studio SO unstable that moving to a 64-bit is just impossible? Is that it? Because this seems to be the only reason I could think of - and I have a lot of experience in product development, so I really think this might be the case. But if that is so, just say you'll never prepare a 64-bit version of your software and be done with it.