DeskShare Site Translator Reviews & Ratings

4.5/5

“Exclude Tags Easily, But UI Needs Some Polish”

Because I build multilingual sites with product codes, I used the exclude feature so “SKU123” doesn’t get translated. It works well but the dialog box to set those exclusions is awkward and needs too much manual precision.

Pros : Lets you exclude specific HTML/XML tags or words from translation

Cons : Exclude interface is clunky—requires manual input

Switched from : lokalise

Reason to switch : I moved over to retain fine-grained control over untranslated code.

4.5/5

“Command Line Support Is Great for Automation”

We run weekly content updates and Site Translator’s command-line option lets me script translations on a schedule—automagic! But I had to comb through the help files to figure out syntax—it’s not super intuitive.

Pros : Supports command-line execution—perfect for scheduled tasks

Cons : CLI usage isn’t fully documented—requires manual tweak

Switched from : Dubpro AI

Reason to switch : Moved from cloud-based CLI tools to a self-hosted script with full site control.

4.5/5

“Solid Offline Tool, But No Cloud Sync”

I like that everything happens on my local PC—no data stored in the cloud. But translating on two different computers requires manually copying the profile settings and files. It’s secure, but less convenient.

Pros : Fully offline—great for privacy and speed

Cons : No sync means translating across machines needs manual folder moves

Reason to switch : I switched to Crowdin for cloud-based team work, but miss the offline privacy of Site Translator.

4.5/5

“Preserves Internal Links Perfectly, But Slow for Big Sites”

I loved that after translation, all internal navigation still works—it updates every link reference seamlessly. But on large sites (500+ pages), the process drags, and you have to be patient.

Pros : Automatically updates internal links after translation

Cons : It can crawl slowly on sites with hundreds of pages

Switched from : WPML

Reason to switch : I moved from WPML so I could translate offline and keep full control over file handling.

4.5/5

“Can Handle .RESX Files—Perfect for Software Localisation””

I localize software, and exporting strings to RESX was tedious. Site Translator auto-translates the entire file, saving me tons of time. It took a bit to map keys correctly, but once done, it just works across languages.

Pros : Translates .NET RESX resource files effortlessly

Cons : RESX setup requires some attention to key/value pairing

Switched from : Visual Localize

Reason to switch : I switched from Visual Localize for faster .RESX automation and multi-language support.

4.3/5

“One-Year Dictionary Subscription Is Fair”

Out of the box, I get English and Spanish—handy for most clients. But after that I had to subscribe to extra language packs, which felt like upsells. Overall fair pricing, though.

Pros : Includes a year subscription to English & Spanish dictionaries

Cons : Additional languages need separate paid packs

Switched from : Vitra AI

Reason to switch : Chose Site Translator because the base packs covered my core needs affordably.

4.3/5

“Translation Memory Is Handy, But Needs Tuning”

When I translate common phrases like “Contact Us,” Site Translator remembers it and auto-applies across pages—it saves loads of time. But setting those personalized phrases initially means clicking through every instance manually, which is slow.

Pros : Remembers your customized translations

Cons : Initial build of the memory is manual and tedious

Switched from : Poedit

Reason to switch : I switched from Poedit to get a more automated whole-site translation where I can still manually refine common terms.

4.2/5

“Quick Site Translation But Techy Setup”

I use Site Translator to convert my static site into Spanish and French—it grabs all the text but leaves my HTML intact, which is super convenient. You point it at the folder and it works perfectly. The downside? You have to download and re-upload the files—no instant online editor like some cloud tools.

Pros : Translates full HTML/ASP/PHP/RESX files, preserves source code

Cons : Requires local file upload—not instant live translation

Switched from : Welglot

Reason to switch : I switched from Weglot because I prefer offline editing and full control over the HTML code.

4.2/5

“Supports Many Languages, But Interface Is Old School””

I appreciate the breadth of languages—from Croatian to Indonesian—which makes globalizing my site easy. But the user interface is barebones: classic Windows dialogs, lots of clicking. It works fine, but doesn’t feel modern.

Pros : Supports 19 languages (Catalan to Turkish)

Cons : UI feels dated—click-heavy and Windows-style menus

Switched from : lokalise

Reason to switch : I moved from Lokalise to get more language options while staying desktop-based.

4.2/5

“Great Trial Limits, But No Live Preview”

The 200-word trial allowed me to trial translation quality before buying. But I had to export files and view locally—not like cloud tools that show live previews. It’s fine, but slower for testing changes.

Pros : Trial lets you test 200 words for free

Cons : No live browser preview—need local build and view

Switched from : Doctranslate

Reason to switch : I moved to Site Translator for longer-term cost savings, even if workflow is slower.