A Baltimore-themed shirt design can be technically ready to print and still not be ready for production. The file may be sharp, properly sized, and visually complete, but if the source of the artwork or the basis for using it is unclear, there is another question to resolve before technical print preparation begins.
For Baltimore-themed DTF merch, the first preflight question should not be only, “Will this file print well?” It should also be: “Where did this artwork come from, and what is the basis for using it for this particular product?”
That starts with separating four categories that are easy to blur together: the official Baltimore City Seal, the City logo, independently created Baltimore-themed artwork, and customer-supplied or third-party licensed artwork. They should not all move through production under the same assumptions.
If you are evaluating the broader commercial side of this market, our guide to DTF transfer business opportunities in Baltimore covers that wider decision. This guide has a narrower job: establishing the source and rights status of artwork before it becomes a production file.
Start by Identifying What Kind of Artwork You Actually Have
Do not classify a design only by what it looks like. Start with where it came from. Two graphics that both reference Baltimore can have completely different source and usage situations.
A practical first-pass classification is:
- Official City asset: Is it an asset identified by Baltimore City, such as the Baltimore City Seal or official City logo?
- Original artwork: Was the design created from scratch by your business or by a designer working on your project?
- Customer-supplied artwork: Did the customer provide the finished graphic?
- Third-party or licensed asset: Did it come from an artist, photographer, stock library, marketplace, or another outside source?
This classification does not decide the legal status of a design. It gives you a production checkpoint so that an official symbol, an original illustration, and a downloaded asset are not treated as interchangeable files.
If You See the Baltimore City Seal, Do Not Treat It Like Ordinary Artwork
The Baltimore City Seal has a specific local rule attached to it. Baltimore City Code Article 1, Subtitle 35 §35-3 prohibits using a copy or facsimile of the Seal of the Mayor and City Council of Baltimore for advertising purposes and also restricts the use of copies or facsimiles of the Seal on documents outside specified official City uses.
That makes the Seal materially different from a generic Baltimore-themed illustration. If a submitted design appears to contain the official Seal, or something presented as the Seal, it deserves a separate source check before production is released.
Useful preflight questions include:
- Is this actually the official Baltimore City Seal?
- Where did the asset file come from?
- What exactly is the proposed apparel or merchandise use?
- Has the current City Code and any applicable official guidance been checked for that use?
A print seller does not need to turn this checkpoint into a legal opinion about whether a particular shirt or merchandise use definitively falls into a particular statutory category. Operationally, the safer response to an identified City Seal is to pause the release and verify the applicable official rule rather than assuming it can be handled like ordinary commercial artwork.
Just as important, this rule does not mean that every image associated with Baltimore has the same status as the City Seal. An independently created Baltimore illustration, typography treatment, neighborhood-inspired graphic, or other local-themed artwork has to be evaluated according to its own source and rights situation.
Do Not Confuse the City Logo With the City Seal
Baltimore City's official brand guidelines distinguish the City logo from the City Seal. The guidelines identify the Seal as the City's official government emblem and state that its use is regulated by Subtitle 35 of Article 1 of the City Code. The same guidelines treat the City logo as a separate element of City Hall's visual identity.
That distinction matters during artwork preflight. A City logo should not automatically be classified as the Seal simply because both are official Baltimore assets.
But the opposite shortcut is not appropriate either. The fact that the brand guidelines distinguish the logo from the legally regulated Seal should not be treated, by itself, as a blanket permission for an independent apparel seller to put the City logo on commercial merchandise.
The guidelines describe Baltimore City Hall's visual identity and include rules for how the logo should appear. They should not be stretched into a third-party merchandise license that they do not expressly provide.
For production purposes, keep the decision paths separate:
City Seal: identify it as the official government emblem and check the applicable City Code provision before release.
City logo: identify it as a separate official asset, verify its source, and confirm the appropriate guidance or permission basis for the proposed third-party or commercial use rather than inferring permission from the Seal/logo distinction.
“Baltimore-Themed” Does Not Automatically Mean “Official City Asset”
A design can be unmistakably about Baltimore without incorporating an official government asset. A designer might create original typography, illustrations, abstract city references, neighborhood-inspired graphics, or other visual concepts from scratch.
At that point, the preflight question changes. You are no longer asking only whether the City Seal rule applies. You are asking who created the artwork and what basis supports the planned use.
For example, an original Baltimore-themed shirt graphic and a direct reproduction of the City Seal should not enter the same branch of the decision process merely because both refer to Baltimore.
The same caution applies to locally inspired imagery. Do not assume that something is unrestricted simply because it depicts a skyline, landmark, local phrase, or other Baltimore reference. Identify the actual artwork you have, where it came from, and whether another creator or rightsholder is involved.
A Customer Sending the File Does Not Answer the Rights Question
Customer-supplied artwork is normal in a DTF transfer workflow. But possession of a PNG, PDF, or vector file does not by itself explain who created the artwork or what rights came with it.
A customer could have created the design, commissioned it, licensed it, received it from another organization, purchased an asset, or simply downloaded something from the internet. Those situations should not automatically receive the same production status.
Before release, useful source questions include:
- Who created the artwork?
- Is it the customer's original asset?
- If another designer or rightsholder is involved, what permission or license supports this use?
- Does the file contain artwork associated with another brand, organization, artist, or creator?
- If the design will be reproduced on merchandise for sale, does the identified permission or license address that intended use?
This is not about the print provider acting as the customer's attorney. It is about avoiding an operational rule that says, “The customer uploaded it, so the rights question is automatically settled.”
For Stock or Licensed Artwork, Check What the License Actually Covers
Paying for or downloading an asset does not necessarily answer every usage question. Stock libraries, design marketplaces, photographers, artists, and other creators can offer different license terms for different uses.
If a license is involved, record more than the fact that an asset was “purchased.” Check whether the identified terms address the way the artwork will actually be used, especially when the design will be reproduced on physical merchandise or products offered for sale.
The U.S. Copyright Office's guidance on obtaining permission provides a useful framework for this kind of source check. It explains that when using a work you did not create, you may need to determine its copyright status and identify the current owner of the exact material. When permission is sought, the intended use and the specific material involved are among the details that may matter.
The Copyright Office also notes that the absence of a copyright notice does not necessarily mean a work can be freely used.
That is why statements such as “I found it online,” “there was no watermark,” “the customer said they bought it,” or “it came from a marketplace” are not substitutes for understanding the source and the applicable terms.
Keep a Source and Rights Record for Original or Commissioned Artwork Too
When artwork was created specifically for your business, source verification may be more straightforward. Even then, “a designer made this for us” should not automatically be used as a complete answer to every ownership or usage question.
A short origin and rights record associated with the production file can include:
- Artwork creator
- Artwork source
- Customer or internal project reference
- For commissioned work, the agreement or permission reference supporting the intended use
- Any applicable license or other rights documentation
- The final artwork version released to production
This is an operational record, not a claim that every item on the list is an official legal-document requirement. Its purpose is to make the production history understandable later.
If the same design comes back months from now for another order, your team should not have to rely entirely on someone remembering where the artwork came from or why that version was cleared.
Version control still does not replace rights verification. First establish the source and usage basis. Then connect that cleared status to the specific final file that enters production.
Do Not Let Proof Approval Substitute for Rights and Source Clearance
A visual proof can confirm what a design looks like, where it will be placed, and which version the customer expects. It does not independently establish where the artwork came from or whether a third-party use is authorized.
For that reason, it helps to think of pre-production approval as two different checkpoints:
- Source and rights clearance: Do you understand where the artwork came from and the basis for the planned use?
- Production approval: Is the correct cleared artwork version connected to the intended placement, size, quantity, and order specifications?
The second checkpoint does not erase the first.
A customer can approve the appearance of a proof while the source of an embedded third-party graphic remains unclear. “Proof approved” should therefore describe production choices, not silently become an answer to an unresolved rights question.
Define When an Artwork File Should Be Put on Hold
You do not need to turn every unusual artwork file into a legal investigation. A more practical production control is to define the conditions that stop an automatic release and require additional source verification.
Examples can include:
- An asset identified or presented as the official Baltimore City Seal
- A City logo file with an unclear source or unclear proposed-use basis
- Artwork the customer says was found online
- A stock or marketplace graphic whose relevant license terms have not been checked
- An illustration clearly associated with another artist or organization when the usage basis is unknown
- The stated source of the artwork does not line up with the permission or license information provided
A production hold does not mean declaring that the design can never be used. It means moving an unresolved source question to the point where it belongs: before the file is printed rather than after production has already started.
Use a Four-Branch Preflight for Baltimore-Themed Artwork
The full decision can be reduced to four practical branches:
- Is it the official Baltimore City Seal? Check the applicable City Code provision and current official guidance. Do not process it as ordinary commercial artwork.
- Is it the official City logo? Keep it separate from the Seal, verify the official asset and its source, and do not infer third-party commercial permission solely from the City's internal brand guidance.
- Is it original or commissioned artwork? Record who created it, the source, the basis for the intended use, and the final version cleared for production.
- Is it customer-supplied, third-party, stock, or licensed artwork? Identify the creator or rightsholder and check the permission or license basis against the intended merchandise use.
If you cannot confidently determine which branch a file belongs to, resolve the source question before adding it to a final gang sheet or production order.
Move to Production Specifications After the Artwork Status Is Clear
Once the source and usage basis are clear enough for your workflow to release the artwork, you can move into the ordinary production decisions: finished dimensions, placement, quantity, garment plan, and transfer format.
When the artwork is ready for that stage, you can evaluate the appropriate DTF Transfers for the actual production specifications of the job.
The sequence matters. Instead of spending time preparing an unresolved asset for print and discovering the source problem later, keep the workflow in this order: source and rights preflight → cleared final artwork version → production specifications → transfer order.
Final Takeaway: Verify the Artwork's Status, Not Just Its Baltimore Reference
The most important shortcut to avoid in Baltimore-themed merch production is assuming that every city-related graphic has the same usage status.
The Baltimore City Seal has a specific City Code provision governing its use. The City logo is a separate official brand asset and should not be confused with the Seal. Independently created Baltimore-themed designs, customer-supplied files, commissioned artwork, and licensed third-party assets each raise different source questions.
Build those distinctions into the pre-production workflow. Identify where the file came from, determine which asset category it belongs to, check the relevant permission or license basis when one is needed, and connect the cleared status to the exact final artwork version that enters production.
If a particular use remains uncertain, do not guess that it is fair use, public domain, unrestricted, or prohibited. Check the applicable official source, license terms, or rightsholder as appropriate. Resolving that uncertainty before production creates a cleaner workflow than trying to reconstruct the artwork's status after the transfers have already been produced.
