Blazonry Server

Enter your blazon:

Format:

  • PNG
  • SVG


Blazonry Supported

The Blazonry server uses the pyBlazon program, which converts mediæval blazonry into SVG format, and then (by default) converts the SVG into PNG graphics using rsvg (since pretty much no web browsers handle the generated SVG properly).

See the pyBlazon Home Page

Don't Know Enough Blazonry to Understand What To Do? See the Blazonry Intro at the pyBlazon Googlecode Wiki

Blazonry's structure is already pretty rigid, so most normal blazons should work without much trouble. Follow the usual conventions: background first, then charges, using the usual terminology. But note also that the line between Blazonry and ordinary English is not a sharp one, and this program can in no way follow it very far in that direction. See the pyBlazon page for some idea of the limitations of the grammar.

Not many “fancy” charges (animals, plants, common objects, etc.) are supported, but we have some: a few various crosses, lions rampant and passant.... But you can use any image on the web as a charge; just give its URL between <>-signs (but if you do that, remember that unless it has a transparent background, in PNG or GIF for example, the background will be included as part of the charge too). Or concentrate instead on experimenting with what patterns and arrangement you can make with the charges at hand.

I repeat: the cool charge you're looking for is probably not there. If your Or a horse-head cabossed sable didn't work, it probably isn't going to work for Or a horse-head sable or anything like that. Hardly any charges are supported by default, beyond geometric ones. The cool part is seeing how they are handled.

Examples:

You might also try taking a look at this site of old rolls of arms for some authentic examples. Try some of them out on the server. By no means will all of them work, but some will.

Some of the terms the server understands:


News

1 May 2008
After a long hiatus, uploaded the new version here. This uses a different type of lexer, making it more flexible in accepting complicated charge-names, against a time when I'll have a table of charges that can use it. In the meantime, though, I've added a question-mark shaped charge that is used for anything not recognized, which is a lot better than an error message when you use a charge that isn't one of the few pyBlazon knows. Also see the pyBlazon home page for new information about the availability of the software.