Shipper Templates for ProBoards: The Ultimate Free Collection
If you run a roleplay forum on ProBoards, you already know that the way you present relationships matters as much as the writing itself. A shipper template is the pre-built layout that players use to display everything about a pairing — the two characters, their status, their history, the threads they share, and the little details that make the ship feel alive. Instead of scribbling that information into a plain post, members drop it into a structured format that looks intentional and reads cleanly on both desktop and mobile screens.
Searching for shipper templates for ProBoards can be frustrating because the term means different things depending on who you ask. For some communities it is a simple profile block with two portraits and a status tag. For others it is an elaborate multi-section layout with tabbed navigation, quote boxes, playlists, and a full thread tracker. This guide walks through what these templates typically contain, how to build one that actually works inside ProBoards' posting system, and how to share or credit them responsibly.
What a Shipper Template Actually Does
At its core, a shipper template is a reusable layout document. It defines where images go, where text goes, and how the whole thing is styled, so that every member filling it out produces a page with a consistent look. On ProBoards, that typically means a combination of BBCode tags and, where permissions allow it, a small amount of HTML and inline styling. The template becomes a container: the structure stays fixed while the content inside changes from ship to ship.
That structure solves a very real problem. Without it, relationship pages sprawl. One member posts a wall of text, another posts a single line, a third forgets to link their threads, and the board's ship index turns into an unreadable pile. A template enforces minimum information and visual rhythm, which makes browsing a large roleplay community far less exhausting.
Why Roleplay Communities Depend on Ship Layouts
Discoverability is the biggest reason. New applicants usually browse a board's relationship directory before they write a single post, and they are looking for open dynamics, taken pairings, and characters who need connections. A well-designed template lets them scan ten ships in a minute instead of reading ten essays. Status labels, character names, and face claims need to be visible at a glance.
Continuity is the second reason. Long-running boards accumulate dozens of threads per pairing, and players lose track of what happened three months ago. A template with a dedicated thread tracker section keeps that history attached to the ship page, so returning after a hiatus takes minutes rather than hours of forum archaeology.
Standard Blocks You Will Find in Most Ship Pages
While every community puts its own spin on things, most shipper templates share a common skeleton. Knowing these blocks helps you decide what to keep and what to cut for your own board's culture.
- Header banner with the ship name, often a portmanteau of the two characters' names, plus a colored accent or divider.
- Character profiles with portraits, face claims, ages, and short personality blurbs.
- Status tags such as canon, alternate universe, crack ship, endgame, slow burn, or complicated.
- Dynamic description explaining the emotional and narrative relationship between the two characters.
- Thread tracker with linked titles, dates, and current progress.
- Extras like playlists, mood boards, quote blocks, wanted ads, and plotting notes.
The variation usually comes down to form factor rather than content. A minimal template might be a single column under 500 pixels wide with two portraits side by side. A maximalist one might stack six sections vertically and rely on color blocking to separate them. Both work, as long as the text remains legible and the images are not so large that the page takes ten seconds to load.
Building a Shipper Template That Survives ProBoards
Before you touch a single tag, decide what the template is for. A ship page meant for quick reference needs different priorities than one meant to be read like a story. Write out the sections on paper first, then map each section to a visual block. Skipping this step is why so many templates end up with gorgeous headers and cramped, unreadable body text.
Once the plan is set, build a master version and keep it in a staff-only thread or a hidden board. Every time a member asks for a tweak, you can pull from that master instead of reconstructing the layout from memory. Version your templates with dates in the title so you can tell at a glance which one is current.
Working Within BBCode, HTML, and Board Limits
ProBoards runs primarily on BBCode in the post editor, and that is what most templates rely on. Tags for centering, images, tables, font colors, and styled divs cover the vast majority of what a ship page needs. Whether raw HTML renders inside a post depends entirely on how your administrator configured posting permissions, so never assume it will work for your entire membership.
Two constraints deserve attention early. First, every post has a character ceiling, which is generous but not unlimited, and image-heavy templates eat into it fast. Second, script-based effects such as hover tabs or accordions are generally not viable inside posts, because scripting is filtered for security reasons. If you want those features, they belong on a custom page or in the theme's layout templates, not in a member's ship post.
Design Choices That Keep Pages Readable
Contrast and size do more for readability than any decorative flourish. Body text should sit comfortably against its background, and font sizes should never drop below what a phone screen can render without zooming. Portrait images work best when kept to roughly 300 to 500 pixels wide, compressed before uploading, and hosted somewhere reliable rather than on a free host that might vanish in six months.
Color should guide the eye, not fight it. Pick two or three tones per ship and use them for borders, headings, and dividers. Resist the urge to use a different palette for every section, because that turns the page into a patchwork. If a template looks clean in grayscale, it will almost certainly look clean in color too.
Organizing, Sharing, and Crediting Templates
A board with fifty shipper templates needs a home for them. The standard approach is a dedicated resource board with sub-boards for templates, graphics, and code snippets, each with clear posting rules. Keeping the resource area separate from the in-character boards prevents clutter and makes it easy for new members to find what they need during the application process.
Sharing outward is where things get delicate. Many designers are happy to let other forums use their work, but almost all of them expect credit and a link back. Building a reputation as a community that respects those terms makes it easier to collaborate with graphic makers and coders later, and it keeps the creative pipeline flowing in both directions.
Where to Find Pre-Made Templates
The ProBoards support community is a genuinely useful starting point, since its template and graphics sections are full of member-made layouts that have already been tested on the platform. Roleplay resource directories, affiliate boards, and dedicated coding blogs frequently publish free-for-use ship layouts as well. Pinterest and Tumblr still surface a steady stream of designs, though you will need to trace them back to their original source before using them.
Vet anything you download before you upload it. Check that the image hosts are still active, that the layout does not rely on a code tag your board has disabled, and that the designer's terms permit use on your forum. A template that looks stunning but breaks on mobile is not a bargain, it is a support ticket waiting to happen.
Credits, Permissions, and Community Etiquette
Removing a credit line is the fastest way to sour a relationship with a designer, and word travels quickly across roleplay circles. If a template says "do not edit the credit," do not edit the credit. If you want a variation, message the creator and ask. Most will either say yes or point you toward someone who can help.
There is also a pay-it-forward side to this. If you build a solid shipper template for your own board, consider publishing it free to use with a simple credit requirement. It strengthens the wider community, brings traffic back to your forum through the credit link, and gives newer designers something to learn from.
Whether you are polishing your first relationship directory or overhauling a board that has been running for years, the goal stays the same: make it easy for players to find each other and start writing. Start with one template, test it on a phone, get feedback from your members, and iterate. The layouts that last are rarely the flashiest ones; they are the ones that someone actually enjoys filling out at two in the morning when a new plot idea hits.