bridge con't prreview the .psdt files like psd file ... please help
I've been lookiong for a solution to this for so long now, surely it's a fundamental part of file organisation... am I missing the answer somewhere or is it not that important to anyone else?!
A psdt file is a template file. As such there is no actual image in the file, it's a layout of a file. What a psdt file needs is a very descriptive NAME so that you can know by it's name what it's for and what it can do.
For example, if you have a template file for use with a given business and their employees, you could give it a name of "Acme Employees 2021." Since this template would only be used for employees of the Acme Company, you (as the creator) should know what it's for.
Think of a template as a code/instructions for PS as to how to present a photo. Remember that it opens up as an untitled document so it really has no content to display in Bridge or in Explorer or in Finder.
That's incorrect. The extension tells Photoshop to open the "Untitled" version of the file. The file itself *is* a standard Photoshop document. If you rename the file using just a PSD extension, the preview is there and the file opens as normal without any conversion; the same holds true for taking a PSD file—with a preview—and simply renaming it to PSDT. Upon doing so, the preview will disappear and Bridge will treat the file, which is identical to the PSD version, differently. The set of instructions you're referring to is, in fact, an actual Photoshop document.
The Bridge team just hasn't added previews for this extension for some reason. They also haven't implemented UI scaling for HiDPI monitors on Windows using less than 200% scaling. I think some things just aren't high on their priority list, which I guess is understandable (although mildly annoying in cases like this) for features which I assume are used by a relative minority of users and may not justify the development time to implement.
*Previews are also shown correctly in Photoshop on the Recent Files section.
As of October 2023 the problem still exist. Adobe Support, any suggestions?