Fonts in the Cloud

1. Which fonts do you support?

A list of default compatible fonts can be found here.

2. If I upload a file that uses unsupported fonts, will the file be processed with a substitution font? Or will it not get processed at all?

The file will be processed even though fonts are missing. Vectorworks Cloud Services will substitute the missing fonts the same way your local Vectorworks application does, and the file will be rendered. Since the appearance of the PDF might not be exactly correct, an email will be issued telling you which file was affected, and which font was missing when the file was rendered.

3. What do I do if I get a "missing font" email from Vectorworks Cloud Services?

Simply put a copy of the missing font file anywhere in your Vectorworks Cloud Services folder. It does not need to be in a folder dedicated for font uploads, but you can do that if you would like. Then, use the "Synchronize now" command to upload the font file to your cloud account. The next time any Vectorworks file that uses this font is submitted for processing, the correct font will be used, and you will not receive a missing font email.

4. What types of fonts can I upload to the cloud?

We support Open Type fonts (.otf) and Windows True Type fonts (.ttf).

  • .otf fonts: Since .otf fonts are cross-platform font files, they can be uploaded to the cloud without modification whether you are a Macintosh or Windows user.

  • .ttf fonts: There are two versions of True Type fonts—Macintosh and Windows. Windows TrueType fonts work on both Windows and Macintosh OS X, but Macintosh TrueType fonts only work on the Macintosh. Therefore, your Macintosh TrueType fonts will need to be converted to the Windows version in order for them to work on the cloud.

    Various free online conversion tools are available. We recommend this one: Online font converter

    If you are converting a Macintosh TrueType font, we recommend that you convert it to .otf format. The font converter recommended above will return a .tar.gz file that contains a compressed version of the .otf file. Extract the font file from the compressed file, and then place the .otf file in your Vectorworks Cloud Services folder. We recommend 7-Zip file extraction software (http://www.7-zip.org/). Compressed files cannot be used by Vectorworks Cloud Services.

5. How does my local Vectorworks font mapping affect my cloud file processing?

How local Vectorworks font mapping works:

In Vectorworks, when you open a file that contains fonts that are not available on your system, the Font Mapping dialog box opens. You can map fonts from the original file to a font available on your system, or automatically map fonts to the default replacement fonts. Mapped fonts are stored as a Vectorworks preference when you quit the program. If your Vectorworks preferences are deleted, the Font Mapping dialog box will display again for a file that may have previously had the fonts mapped.

How cloud font mapping works:

Every time your desktop client uploads Vectorworks files for processing, it also uploads your local Vectorworks font mappings. If you use Vectorworks Cloud Services on more than one workstation, the font mappings might be different on each workstation. The desktop client replaces any existing font mappings that may be stored in your cloud profile with the font mappings on the workstation that you are currently synching from.

You can check the currently available system fonts and font mappings in your cloud profile by visiting https://cloud.vectorworks.net/portal/fonts .

In some situations, you might need to delete your local Vectorworks font mappings to ensure that the proper fonts are used for cloud processing. Prior to uploading files with the desktop client, access the Vectorworks preferences; on the Display tab, click the Edit Font Mappings button, and delete the mappings as needed. Quit the Vectorworks program to save the font mapping preferences.

Generally, Vectorworks Cloud Services uses fonts and font mappings in the following order of priority:

  1. Available system fonts are used
  2. Your local font mappings are used
  3. Custom fonts from your cloud processing folder are used
  4. If the first three steps fail, Arial is used

The cases below illustrate how these priorities work, depending on the platforms you and your collaborators are working on.

  • Mapping a default Mac system font to a default Windows system font or vice versa

    You are a Windows user and you have received a .vwx file from a Mac user. The Mac user has created this file using Mac system fonts that are not available on a Windows platform. When you open this file in Vectorworks, you choose to map this font to a default font that is available on the Windows platform. Since the cloud server already has all default Windows and Mac system fonts, when you send this file for processing, it will be processed by using the original font in the file, not by using your local font mapping. This means the file will maintain its original appearance from the Mac user.

  • Mapping a custom font to a default Windows or Mac system font

    You are a Windows user and you have received a .vwx file from a Mac user. The Mac user has created this file using a custom font that is not available as a default system font on either Windows or Mac platforms.

    1. The Mac user does not provide the font file, and you have a local font mapping set to a default font of your choice:

      When you send the .vwx file for processing you will only have the font mapping that maps this font to a default system font. In this situation, Vectorworks Cloud Services will use the font mapping of your choice while processing the file.

    2. The Mac user does not provide the font file, and you do not have a local font mapping to a default font of your choice:

      When you send the .vwx file for processing, Vectorworks Cloud Services will automatically map the missing font to Arial.

    3. The Mac user provides the font file, but you do not install it on your computer. Instead, you create a local font mapping to a default font of your choice, and only upload the Mac font file for use by the cloud:

      When you send the .vwx file for processing, you will have the original font file in your cloud processing folder as well as a font mapping that maps this font to a default system font in your cloud profile. Vectorworks Cloud Services will use your font mapping while processing the file. To use the original font, delete your local font mapping before you upload the file, as described earlier in this article.

  • Mapping a custom font to another custom font

    You are a Windows user and you have received a .vwx file from a Mac user. The Mac user has created this file using a custom font that is not available as a default system font on either Windows or Mac platforms.

    1. The Mac user provides the font file, but you do not install it on your computer. Instead, you create a local font mapping to a custom font of your choice, and only upload the Mac font file for use by the cloud:

      When you send the .vwx file for processing, you will have the original font file in your cloud processing folder as well as a font mapping that maps this font to a custom font of your choice in your cloud profile. If you have not uploaded your custom font, Vectorworks Cloud Services will use Arial as a replacement font. If you have uploaded your custom font, the cloud server will use your font mapping; the original font will be ignored and your custom font will be used.

    2. The Mac user does not provide the font file, and you have a local font mapping to a custom font of your choice:

      When you send the .vwx file for processing, you will only have the font mapping that maps this font to a custom font of your choice in your cloud profile. If you have uploaded your custom font, Vectorworks Cloud Services will use it while processing the file.

Your browser's JavaScript is disabled. Enable it to use the site.