Support & Help

Find answers to most common Axure RP questions

Re-Install icon fonts

All the libraries use embedded icon fonts. In case you don’t see the icons in your wireframes, this just means, you still need to install or re-install the correct icon fonts locally or on a server online. This is easy and there is a good tutorial on Axure’s Forum (link or link) on how to install custom fonts. Just as a note; In case you want to install other fonts from Google or Apple, you need to go through a process called Font Mapping. See topic below.

Understand Axure's font mapping

In case you want to install custom fonts in Axure RP, you need to do a font mapping for each font/cut (regular, bold, italic, etc.). Please follow these instructions on the Axure Forum (link). Here is another good online resource that explains the process. I am not affiliated with Axure, so things might change within their software, this is the reason I refer to their website.

How to set up a new document

Two things you want to look for, when starting a new “Axure.rp” file: Firstly you need to go through the font mapping process again, if you want to use custom fonts and an icon font. Secondly, you need to set up the View Port in the menu “Publish – Generate HTML file – Mobile/Device …”.


For mobile prototypes go with (adjust width to fit your device):


Settings for Mobile Device Testing Axure RP

Font Awesome Icons Fix & Installation

Working with Font Awesome 5 in Axure RP 8 works great except none of the icons will display when published to There is a little bit of a problem with Axure naming fonts in the exported HTML (they are not compatible with FA5 css).
To solve your issue, you can change font mapping in the “Generate HTML” options or try my slightly modified CDN:

More in regards to this issue here:

Help with responsive designs

When it comes to responsive or adaptive UX design, I often just go with two versions – and this is years of Axure prototyping and wireframing experience.


Tablet/Desktop with a setting of 1024px width min. and a 960px grid. The Web UI Kit widget library works perfect for this. All the elements have a perfect size-ration and beautiful proportions.


Smartphone with a setting of 360px or 375px width and a grid that is based on iOS Google’s Material Design Guidelines.


With those two screen sizes you can cover 90% of all the edge cases in your responsive or adaptive (web) design and you become fast, since you only need to update and iterate on two prototypes.

Editing dynamic layers

Some of the modules and components included in the widget libraries are fairly complex and have multiple layers merged into one dynamic layer. This is often required when you want to work with full-screen background images, sticky drawers, footers and headers, and especially when you have interactive components. Years of prototyping experience has taught me, to keep designs editable and simple, so you can change things fast. Nonetheless – you want to build a product that comes as close as possible to the finished version, otherwise you risk testing something that is far away for the end-product, which in return diminishes your user testing results. So; Build fast and always stay close to final product.

Customise repeaters

Repeaters are a great widget in Axure, but I noticed that it slows you down in the design process, since editing repeaters is a bit painful (many clicks). It’s great if you need to demonstrate and work with some real data, but this is often not required if you work with real copy (always work with real copy!!!).


The other disadvantage is, that repeaters make your page load extremely slow. This is often the case when you go beyond 40 or 50 rows of data input. So keep it light. Again, you are simulating MVP’s and prototypes, not life pages.

Still have a question?