It really just comes down to personal preference and workflow how you do it.
First up, look in the browser inspector at the CORS errors listed in the console. It will tell you the site address that is trying to load the font and the url to the font file. These must be on the same sub domain (remember
.www is a subdomain). In the case above, the site was using
http://www but the resources links generated just
The problem people find when using resources happens if page links are not set to relative. When relative the link to the font file will just start with
/ and so will always reference a directory within the site
Personally I would never load up a RW project file with fonts. I prefer to manage fonts separately and manually ftp them to the server. You have two choices here -
either create a folder within your site root (
public_html or whatever it is on your host) and put the fonts in there. You can then just enter this url in FontPro and you will never have any CORS issues.
The other way to do it (and my preferred option) is to use a subdomain to store the fonts such as
This has the advantage that your fonts are totally separate from your site (should you wish to delete everything and republish then there is no danger of deleting the fonts by mistake) and also, multiple sites or subdomains of your site can all use the same font files.
In this case you just put the htaccess snippet from the link I posted above in the root directory of the subdomain on your server. If you want to specify just your domain, rather than the wildcard
* then, in your case you would ensure that no one else can use your fonts in there site.
I hope that makes sense and just remember that the browser inspector in Chrome or Firefox is your best friend here as that will tell you if the domains of the font and the requester are different, and what the urls are.