Hand the tedious parts to the tool. Keep the final judgment in your hands.
Import a translation spreadsheet and let the workbench handle the layout churn: Photoshop replacement and read-back verification run under your supervision. At anything uncertain, it stops and shows you the evidence before continuing.
- Does not translate for you
- Every write is read back and verified
- Stops and asks when evidence is thin
图译工坊 is in a small invite-only beta. Users with real multilingual PSD projects who can report issues get priority.
Standard workflow
Add translations, review them, pick the design files, then batch-generate after confirmation.
- 01
Import translation tables
Batch import works best: one multilingual table, or several single-language tables selected together and merged automatically. Pasted text and OCR are also supported.
- 02
Review language by language
Each language card surfaces empty translations, duplicate source strings, and conflicting candidates in real time. Switch cards to confirm one language at a time.
- 03
Replace locally in Photoshop
On your own computer, Photoshop matches text layers strictly. All languages can run in one pass; extra table rows are listed in the report.
- 04
Confirm delivery
After sync, re-check anything that was flagged, then deliver once you are satisfied.
Design files stay on your computer
PSD / PSB source files and replaced images are processed only on your machine and are never uploaded. Layer text, table source strings and translations, and file paths are processed on our servers per the Privacy Policy; OCR and AI features additionally send necessary content to the corresponding services.
- PSD / PSB source files and replaced images are processed locally only
- Layer text, table strings, translations, and paths are handled per the Privacy Policy
- OCR / AI features send necessary content to the corresponding third-party services
- Replacement reports are generated only in your local output folder
Reviewable, not fully automatic
With multilingual design files the real risk is missed or wrong replacements that are hard to check — not translation quality. 图译工坊 does not promise 100% correctness: complex PSDs, rasterized text, and smart objects still need human review. Extra table rows and warnings are listed explicitly in the replacement report.
By submitting you acknowledge: this tool is still in beta validation, complex PSDs still require human review, and 100% automatic correctness is not promised.
Before batch-applying languages: check these 6 things
Short answer: the text must still be editable layers, the translation table must match this PSD, one object per row, review translations before writing, at most 12 target languages per batch, and review the layout language by language afterwards. Get these six right and batch language replacement will not need rework.
Prepared by the 图译工坊 team · Published 2026-10-17
Is the text still editable text layers?
If text has been flattened into the background image, Photoshop has no replaceable text content. Open a few representative pages first; special effects, complex fonts, or titles split across several layers deserve an extra look.
Does the translation table match this PSD?
Generate the table template from the PSD you are about to process, then fill in confirmed translations. Do not reuse a table from another design file: identical-looking source strings do not guarantee identical layers or positions. Spot-check a few rows before you start.
One design object per row?
Multi-line text in the same text layer belongs in a single cell; do not split it into several rows by the line breaks you see on screen. Splitting makes the layer-to-translation mapping ambiguous.
Review translations before writing?
Check for empty translations, duplicated source strings, and the same source string mapped to different translations. The product shows items needing confirmation before execution; ambiguous content should be decided by a person, never treated as a confirmed translation.
At most 12 target languages per batch?
The current per-batch limit is 12 target languages, processed language by language. For projects with more languages, split into batches and verify each batch uses the intended translation columns.
Check the layout language by language after writing?
Longer translations may take more space; line wrapping, fonts, and right-to-left scripts all affect the final layout. Read-back verification checks the text result but cannot judge semantics or aesthetics — open the output files in Photoshop and review text, wrapping, fonts, and the final visual for each language.
Source files and output files stay on your computer; layer text, translations, and design file paths are uploaded for quoting, execution, and billing — see the Privacy Policy and the list of subprocessors.
Frequently asked questions
The questions everyone asks first.
Is this an automatic image-translation tool?
No. It does not translate. It targets the delivery workflow of multilingual design files: batch-writing translations you already have into PSD text layers. Translation quality remains the responsibility of your translation source.
Do I have to upload my design files?
PSD / PSB source files and replaced images are not uploaded; both are processed on your computer. However, layer text, table source strings and translations, and path data are transmitted and processed per the Privacy Policy. When you use OCR or AI features, necessary content is also sent to the corresponding services. See the Privacy Policy and the list of subprocessors for details.
Can it guarantee fully automatic, correct results?
No. Rasterized text, smart objects, and other complex cases cannot be replaced automatically; they are listed in the report for you to handle. The product promise is "reviewable", not "fully automatic".
Why do some positions need my decision?
One source string with multiple translations, a read-back that does not match what was written, or a translation that may overflow the layer — the tool lacks evidence at these positions, and writing blindly is risky. Stopping to ask you is the safer choice.
What is the difference between "needs review" and "needs your decision"?
"Needs review" is a suggestion for a human to double-check (the write already happened or was skipped, and a reviewer can take over). "Needs your decision" must be resolved by you; the tool will not write on your behalf.
How do I get access?
Submit a beta request and the author will contact you by email. Users with real multilingual design projects who are willing to report issues get priority.
Request beta access
Describe your use case so we can judge whether this beta round fits.
Email is used to send the invitation and follow up on trials. No advertising.
Request beta access