The author names the tools behind the distressed result
In the original Mud author note, van der Woerd calls it a destroyed font and explains that it was altered using OPENRNDR, then vectorised and turned into a font with Fontself. This is a concrete production account: a procedural alteration became a reusable alphabet. It does not establish a release history beyond the source or prove that every Mud-named file was produced in the same way.
Check repeated letters before adding another layer of damage
Set a short invented event name containing a repeated letter in the actual Mud specimen. Look for the rhythm created when the same damaged shape recurs. Compare the original rendering with any extra texture you plan to add; keep the untreated version so you can tell whether another effect helps. At thumbnail size, inspect spaces inside letters and the gaps between them before approving a dense or photographic background.
Keep the title editable while preparing the final image
Retain an editable text version and a separate export for sharing, so a date or spelling correction does not require rebuilding the graphic. Confirm the required characters and the terms accompanying the original resource. Special Elite and Creepster here are independent comparisons, not Mud previews. Our Unicode text effect converter changes characters for copied text; it cannot reproduce the OPENRNDR-derived outlines, vectorise artwork or install van der Woerd’s font.
The Broken guide examines a different designed-damage approach with alternate capitals, rather than Mud’s documented procedural construction.
Your questions, answered.
How did the creator make Mud?
His original note names OPENRNDR for alteration, followed by vectorisation and Fontself to create the font.
Can a copied Unicode caption reproduce the damaged outlines?
No. Those outlines belong to the actual font resource rather than a transferable Unicode style.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.