Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I have been trying to use Helvetica font while creating the pdf but the font is not reflected back in pdf.

I did some google and found some solutions but none are workable.

Tried Solution 1

I found similar thing here : Font issue

Tried the last solution mentioned over there

workaround is to define @font-face in your css and have src link to external host that is accessible by wkhtmltopdf

But the solution is not working.

Tried Solution 2 I also tried to use google font api, but result is still not workable. helvetica font

here is an example Example of custom font

Tried Solution 3 I tried doing it using css property @page. But that also is not working.

What is the approach for a workable solution.

The easiest way to fix wkhtmltopdf 's font problems is to Base64 encode the font ( you can use this tool ) and include it in your CSS:

@font-face {
    font-family: 'Helvetica';
    src: url(data:font/truetype;charset=utf-8;base64,AAEAAAATAQA...
This works with all fonts (including Google Fonts), and guarantees cross-platform compatibility across different machines and operating systems.
                yes i think its the same solution as given in here.stackoverflow.com/questions/6721295/…. How ever the generated dosent seem to show helvetica font
– Padmalochan
                Aug 5, 2013 at 9:37
                @JaredEitnier, the old link has gone offline. Try this website instead, it does the same thing.
– Arman H
                Sep 4, 2014 at 18:22
                Thanks mate!, if anyone is interested I used this base64: github.com/alixaxel/typhon/blob/master/typeface/sans-serif/…
– Benjamin Vison
                Aug 23, 2017 at 16:31
                You can use this tool to generate all the base64 encoded font file from google fonts stylesheets url. amio.github.io/embedded-google-fonts
– anil90
                Sep 22, 2020 at 11:53
For me loading fonts from Google Fonts didn't work. And putting base64ed binary into a CSS file seems a little to much for me(Korean types are several megabytes). I'd recommend to install the fonts you need to use on the machine. For Ubuntu you can simply download fonts files from Google Fonts and copy the files in to $HOME/.fonts directory and run fc-cache command in command line to rebuild the fonts list.
$ mkdir ~/.fonts
$ copy your-font-file.ttf ~/.fonts/
$ fc-cache -fv
For a Rails application you can symlink
$ ln -s /your/app/root/assets/fonts ~/.fonts
Then you will be able to list all available fonts.
$ fc-list
Nimbus Sans L:style=Regular Italic
URW Palladio L:style=Roman
Century Schoolbook L:style=Bold Italic
Nimbus Sans L:style=Bold
URW Chancery L:style=Medium Italic
Nimbus Roman No9 L:style=Regular
Century Schoolbook L:style=Bold
Century Schoolbook L:style=Italic
Nimbus Sans L:style=Regular
                We use a similar method using wkhtmltopdf for production workloads.  Fonts installed on our servers works well for us.
– theandywaite
                Jun 14, 2016 at 10:06
                thanks for suggesting fc-list. It was enough to find the available fonts in my server :)
– igorsantos07
                Oct 6, 2016 at 20:37
                This should be the accepted solutions, base64-ing of fonts is a bit of a hack. It should also be understood wkhtmltopdf is using fonts that are on the server, so like you would add a font you're missing in Word to your PC or Mac, you add the font to the server. If you're looking to install MS fonts system wide, see this: unix.stackexchange.com/questions/217365/…
– kasimir
                Aug 30, 2017 at 15:59
                This solution is worked also for me (CentOs 7 linux), but with one modification :  it seems that the "Family Name" property inside the TTF file is the problem maker. becuase linux matched the Family Name so if all the fonts have the same family name (Heebo). So I edited the TTF files and changed the family name to "Hebbo-Light" (using the "Font-Forge" software , in "Element" menu > "Font-Info" screen - I edited the "Family" propery" to be with dash , exactly like in the css)   and then re-installed the fonts on the linux - and it works!
– user1598814
                Sep 12, 2018 at 6:45
To add to the fray, using wkhtmltopdf 0.12.1 (with patched qt) on linux this worked for me:
@font-face {
    font-family: dejaSansMono;
    src: url('file:///usr/share/fonts/dejavu/DejaVuSansMono.ttf');
I.e., specifying the path to the .ttf.  Simply naming a font-family, any font-family, did not work even if it did in the browser.
expanding baxangs answer for linux (x64) users: you install the ttf font file in /usr/share/fonts/font-folder/font-name
and then in your css file use the fontname which is listed in fc-list, you don't need to use @font-face, just use the fontname in your css
example Verdana.ttf======
copy from local machine to server into /usr/share/fonts/Verdana/Verdana.ttf
fc-list to get the fontname (most likely it'll be Verdana)
Then use in your css P{ font-family: 'Verdana'}
and that's it! took me a while to get it fixed.
I had the same problem with PT Sans from google. What worked for me was the following process:
Download PT Sans from google and runt it through fontsquirrel
generator 
Place the @font-face (I only used the ttf) in the css (in my case was in html
head of a php file)
Note that I did not use base64 and it worked as expected.
Hope it helps
To convert HTML to PDF by wkhtmltopdf try to avoid woff font face. Use trutype format of the Google Web Fonts with base64 encode.
Recently I tried to use a google web font from Google Web Fonts. But in browser it shows correctly but it doesn't show after converting HTML to PDF.
Then after searching lots of from web at last I found tools to encode fonts to base64 encoded format and also got CSS for @font-face.
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.