Webfont Previewer

This extension allows you to test webfonts out on any website and target which elements the fonts should be applied to.

Webfont Previewer - Test and Apply Webfonts On Any Website

"Webfont Previewer" is a Chrome extension designed to help website developers efficiently alter and preview webfonts on any site. It allows users to choose a font, target specific page elements using CSS selectors, and apply the chosen font to the selected content. Come with a special feature to star favorite fonts for quick use, along with an option to copy the final font code for site integration. Note: Refresh any opened tabs post-installation for smooth function.

Download

Extension stats

By: JustinTheClouds

Users: 595

Rating: 3.29

(7)

Version: 1.2 (Last updated: 2013-09-26)

Creation date: 2013-09-25

Risk impact: High risk impact

Risk likelihood:

Low risk likelihood

Manifest version: 2

Permissions:

tabs
storage
http://fonts.googleapis.com/*
https://googlefontdirectory.googlecode.com/hg/ofl/*

Size: 621.57K

Ranking

# 37,006 ▲ 894

Other rankings

#3762 in Developer Tools ▲ 19

Other platforms

Not available on Android

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

Quickly test and preview out different web fonts while developing your websites.

Select a webfont from the list of fonts. Then choose the page's targets using CSS selectors. Then apply to see the webfont applied to current page's content.

Star your favorite webfonts to make them appear at the top of the list of fonts for quick use. Once you have the font you like, press the code "</>" button to copy the code to paste into your site's HTML for use.

Once installed, any previously opened tabs must be refreshed to work properly

User reviews

Does not work. Console error: Refused to load the stylesheet 'https://fonts.googleapis.com/css?family=ABeeZee' because it violates the following Content Security Policy directive: "style-src 'unsafe-inline'". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.