gofpdf alternatives and similar packages
Based on the "Template Engines" category.
Alternatively, view gofpdf alternatives based on common mentions on social networks and blogs.
sprig8.8 2.6 gofpdf VS sprigUseful template functions for Go templates.
pongo28.5 5.9 gofpdf VS pongo2Django-syntax like template-engine for Go
quicktemplate8.5 0.0 gofpdf VS quicktemplateFast, powerful, yet easy to use template engine for Go. Optimized for speed, zero memory allocations in hot paths. Up to 20x faster than html/template
hero7.9 0.0 gofpdf VS heroA handy, fast and powerful go template engine.
mustache7.7 0.0 gofpdf VS mustacheThe mustache template language in Go
Jet Template Engine for GOJet template engine
maroto7.5 3.2 gofpdf VS marotoA maroto way to create PDFs. Maroto is inspired in Bootstrap and uses gofpdf. Fast and simple.
Razor7.3 0.0 gofpdf VS RazorRazor view engine for go
amber7.3 0.0 gofpdf VS amberAmber is an elegant templating engine for Go Programming Language, inspired from HAML and Jade
ace7.2 0.0 gofpdf VS aceHTML template engine for Go
Plush7.1 1.7 gofpdf VS PlushThe powerful template system that Go needs
fasttemplate7.0 3.3 gofpdf VS fasttemplateSimple and fast template engine for Go
raymond6.7 0.0 gofpdf VS raymondHandlebars for golang
ego6.7 0.0 gofpdf VS egoAn ERB-style templating language for Go.
goview6.0 0.0 gofpdf VS goviewGoview is a lightweight, minimalist and idiomatic template library based on golang html/template for building Go web application.
Jade6.0 0.0 gofpdf VS JadeJade.go - pug template engine for Go (golang)
liquid5.5 0.0 gofpdf VS liquidA Liquid template engine in Go
Soy5.4 1.7 gofpdf VS SoyGo implementation for Soy templates (Google Closure templates)
grender4.0 0.0 gofpdf VS grenderGo package for easily rendering JSON/XML data and HTML templates
velvet3.9 0.0 gofpdf VS velvetA sweet velvety templating package
extemplate3.7 2.5 gofpdf VS extemplateWrapper package for Go's template/html to allow for easy file-based template inheritance.
kasia.go3.7 0.0 gofpdf VS kasia.goTemplating system for HTML and other text documents - go implementation
gospin3.0 0.0 gofpdf VS gospinArticle spinning and spintax/spinning syntax engine written in Go, useful for A/B, testing pieces of text/articles and creating more natural conversations
damsel2.5 0.0 gofpdf VS damselPackage damsel provides html outlining via css-selectors and common template functionality.
tbd1.8 1.5 gofpdf VS tbd"to be defined" - a really simple way to create text templates with placeholders
GoT1.1 0.0 gofpdf VS GoTGoT is a template engine that turns templates into Go code to compile into your app.
Access the most powerful time series database as a service
Do you think we are missing an alternative of gofpdf or a related project?
GoFPDF document generator
Package gofpdf implements a PDF document generator with high level support for text, drawing and images.
- UTF-8 support
- Choice of measurement unit, page format and margins
- Page header and footer management
- Automatic page breaks, line breaks, and text justification
- Inclusion of JPEG, PNG, GIF, TIFF and basic path-only SVG images
- Colors, gradients and alpha channel transparency
- Outline bookmarks
- Internal and external links
- TrueType, Type1 and encoding support
- Page compression
- Lines, Bézier curves, arcs, and ellipses
- Rotation, scaling, skewing, translation, and mirroring
- Document protection
- Charting facility
- Import PDFs as templates
gofpdf has no dependencies other than the Go standard library. All tests pass on Linux, Mac and Windows platforms.
gofpdf supports UTF-8 TrueType fonts and “right-to-left” languages. Note that Chinese, Japanese, and Korean characters may not be included in many general purpose fonts. For these languages, a specialized font (for example, NotoSansSC for simplified Chinese) can be used.
Also, support is provided to automatically translate UTF-8 runes to code page encodings for languages that have fewer than 256 glyphs.
We Are Closed
This repository will not be maintained, at least for some unknown duration. But it is hoped that gofpdf has a bright future in the open source world. Due to Go’s promise of compatibility, gofpdf should continue to function without modification for a longer time than would be the case with many other languages.
Forks should be based on the last viable commit. Tools such as active-forks can be used to select a fork that looks promising for your needs. If a particular fork looks like it has taken the lead in attracting followers, this README will be updated to point people in that direction.
The efforts of all contributors to this project have been deeply appreciated. Best wishes to all of you.
To install the package on your system, run
go get github.com/jung-kurt/gofpdf
Later, to receive updates, run
go get -u -v github.com/jung-kurt/gofpdf/...
The following Go code generates a simple PDF file.
pdf := gofpdf.New("P", "mm", "A4", "") pdf.AddPage() pdf.SetFont("Arial", "B", 16) pdf.Cell(40, 10, "Hello, world") err := pdf.OutputFileAndClose("hello.pdf")
See the functions in the fpdf_test.go file (shown as examples in this documentation) for more advanced PDF examples.
If an error occurs in an Fpdf method, an internal error field is set.
After this occurs, Fpdf method calls typically return without performing
any operations and the error state is retained. This error management
scheme facilitates PDF generation since individual method calls do not
need to be examined for failure; it is generally sufficient to wait
Output() is called. For the same reason, if an error
occurs in the calling application during PDF generation, it may be
desirable for the application to transfer the error to the Fpdf instance
by calling the
SetError() method or the
SetErrorf() method. At any
time during the life cycle of the Fpdf instance, the error state can be
determined with a call to
Err(). The error itself can be
retrieved with a call to
This package is a relatively straightforward translation from the
original FPDF library written in PHP (despite
the caveat in the introduction to Effective
Go). The API names have been
retained even though the Go idiom would suggest otherwise (for example,
pdf.GetX() is used rather than simply
pdf.X()). The similarity of
the two libraries makes the original FPDF website a good source of
information. It includes a forum and FAQ.
However, some internal changes have been made. Page content is built up using buffers (of type bytes.Buffer) rather than repeated string concatenation. Errors are handled as explained above rather than panicking. Output is generated through an interface of type io.Writer or io.WriteCloser. A number of the original PHP methods behave differently based on the type of the arguments that are passed to them; in these cases additional methods have been exported to provide similar functionality. Font definition files are produced in JSON rather than PHP.
A side effect of running
go test ./... is the production of a number
of example PDFs. These can be found in the gofpdf/pdf directory after
the tests complete.
Please note that these examples run in the context of a test. In order
run an example as a standalone application, you’ll need to examine
for some helper routines, for example
Example PDFs can be compared with reference copies in order to verify
that they have been generated as expected. This comparison will be
performed if a PDF with the same name as the example PDF is placed in
the gofpdf/pdf/reference directory and if the third argument to
ComparePDFFiles() in internal/example/example.go is true. (By default
it is false.) The routine that summarizes an example will look for this
file and, if found, will call
ComparePDFFiles() to check the example
PDF for equality with its reference PDF. If differences exist between
the two files they will be printed to standard output and the test will
fail. If the reference file is missing, the comparison is considered to
succeed. In order to successfully compare two PDFs, the placement of
internal resources must be consistent and the internal creation
timestamps must be the same. To do this, the methods
SetCreationDate() need to be called for both files. This is done
automatically for all examples.
Nothing special is required to use the standard PDF fonts (courier,
helvetica, times, zapfdingbats) in your documents other than calling
You should use
AddUTF8FontFromBytes() to add a
TrueType UTF-8 encoded font. Use
LTR() methods switch
between “right-to-left” and “left-to-right” mode.
In order to use a different non-UTF-8 TrueType or Type1 font, you will need to generate a font definition file and, if the font will be embedded into PDFs, a compressed version of the font file. This is done by calling the MakeFont function or using the included makefont command line utility. To create the utility, cd into the makefont subdirectory and run “go build”. This will produce a standalone executable named makefont. Select the appropriate encoding file from the font subdirectory and run the command as in the following example.
./makefont --embed --enc=../font/cp1252.map --dst=../font ../font/calligra.ttf
In your PDF generation code, call
AddFont() to load the font and, as
with the standard fonts, SetFont() to begin using it. Most examples,
including the package example, demonstrate this method. Good sources of
free, open-source fonts include Google
Fonts and DejaVu
The draw2d package is a two dimensional vector graphics library that can generate output in different forms. It uses gofpdf for its document production mode.
gofpdf is a global community effort and you are invited to make it even
better. If you have implemented a new feature or corrected a problem,
please consider contributing your change to the project. A contribution
that does not directly pertain to the core functionality of gofpdf
should be placed in its own directory directly beneath the
Here are guidelines for making submissions. Your change should
- be compatible with the MIT License
- be properly documented
- be formatted with
- include an example in fpdf_test.go if appropriate
- conform to the standards of golint
and go vet, that is,
go vet .should not generate any warnings
- not diminish test coverage
Pull requests are the preferred means of accepting your changes.
gofpdf is released under the MIT License. It is copyrighted by Kurt Jung and the contributors acknowledged below.
- Remove all legacy code page font support; use UTF-8 exclusively
- Improve test coverage as reported by the coverage tool.
*Note that all licence references and agreements mentioned in the gofpdf README section above are relevant to that project's source code only.