# Turn PDF Ad Specifications into Editable Figma Templates > Convert publisher media specs into practical Figma templates without trusting a PDF import more than the source document deserves. - Canonical page: https://www.hypermatic.com/articles/convertify-pdf-ad-specification-to-editable-figma-template-workflow/ - Published: 2026-07-24T00:00:00.000Z - Updated: 2026-07-24T00:00:00.000Z Media specifications often arrive as a PDF that was written for trafficking teams, not designers. One page lists desktop sizes. Another contains mobile placements. Footnotes define safe areas, animation limits, fallback requirements, and maximum file weights. The production team then has to translate that document into Figma frames before a single ad can be designed. [Convertify](/convertify/) can import PDF files into Figma as image-based references or vector content. That makes it useful for recovering the specification, but it does not turn publisher rules into a trustworthy template automatically. The real workflow is import, interpret, rebuild the important constraints, and validate them against the current source. This is different from [PDF Design File Extraction Workflow](/articles/convertify-pdf-design-file-extraction-workflow/) and [Figma Import Cleanup Checklist](/articles/convertify-figma-import-cleanup-checklist/). Those cover extracting design material or cleaning imported files generally. This article is specifically about converting an ad-specification PDF into an operational template that designers and media teams can safely use. ## Treat the PDF as evidence, not a component library An imported specification page may look editable while still being structurally useless. Common import results include: - dimensions represented as text rather than real frame sizes - diagrams broken into many vector fragments - tables with inconsistent grouping - fonts substituted during import - footnotes separated from the placements they qualify - old and new requirements appearing equally authoritative Do not distribute that import as the finished template. Keep one page named `Source specification` and place the imported PDF there. Add the publisher, document title, version, and date retrieved. That page is your evidence trail. The working template should be rebuilt beside it with deliberate Figma structure. ## Extract the rules into a placement matrix Before creating frames, turn the document into a small matrix. For each placement, record: - placement name - width and height - accepted format - maximum file size - maximum animation duration or loop rule - click-through requirement - fallback requirement - safe-area or logo constraint - source page number This forces ambiguous language into the open. If the PDF says “standard display sizes” but gives file-weight limits in a separate appendix, link those rules explicitly. If two pages conflict, flag the placement rather than choosing whichever value is easier. The matrix is also the right point to involve the media buyer or trafficking owner. Designers should not have to infer whether an old PDF is still current. ## Build frames from actual dimensions Create one Figma frame per approved placement using the exact pixel dimensions from the validated matrix. Name frames consistently: `publisher_campaign_placement_widthxheight` For example: `exampleco_spring-leaderboard_728x90` Inside each frame, add only the guidance designers need: - safe-area guides - persistent logo or legal zones - a note for maximum copy length when the format demands it - a placement identifier Keep technical rules in a nearby annotation component instead of placing them inside the exportable artwork. This reduces the risk of a note or red guide accidentally shipping in the final creative. ## Separate universal rules from publisher-specific rules Most production teams already have internal banner conventions: - campaign naming - clickTag QA - fallback generation - review stages - legal approval - archive structure The publisher PDF adds a second layer: - special file limits - custom safe areas - restricted animation behavior - unusual backup-image requirements Do not merge those layers into a single unexplained checklist. Mark rules as: - `team standard` - `publisher requirement` - `campaign decision` When something changes, the owner can update the correct layer instead of cloning an entirely new template family. ## Validate the template with an impossible test Before production starts, deliberately stress the template: - add the longest approved headline - use the widest logo lockup - include the full legal line - test the smallest placement - try the heaviest realistic asset If the template only works with placeholder copy and a compact logo, it is not ready. This test also reveals where the specification itself is incomplete. A PDF may define dimensions and file size but say nothing about how legal copy fits. That is a campaign decision the team needs to make, not a gap the designer should discover during final exports. ## Keep version changes visible Publisher requirements change. The template needs a refresh path. Record: - source PDF filename - retrieved date - approved template version - owner who confirmed ambiguous rules - placements added, removed, or changed When a new PDF arrives, import it onto a new source page and compare the placement matrix before updating frames. Do not silently overwrite the old reference; teams need to know whether an existing campaign was built against a different specification. ## Handoff checklist Before the template is used, confirm: - every frame matches a validated pixel dimension - each rule points back to a source page or named team standard - publisher-specific constraints are clearly marked - safe-area guides cannot be exported accidentally - the smallest placement survives realistic copy and branding - conflicting or ambiguous requirements have an owner - the source document and retrieval date are recorded - the trafficking team has reviewed the final matrix The tutorial on [importing PDF files to Figma with Convertify](/tutorials/how-to-import-pdf-files-to-figma-with-one-click-using-convertify/) is useful for understanding the image and vector import options before starting. ## Where Convertify helps [Convertify](/convertify/) removes the worst first step: manually recreating every page of a specification just to get the information into Figma. It cannot certify that a publisher PDF is current, resolve contradictory footnotes, or decide which restrictions apply to a campaign. Those remain human decisions. Use the imported PDF as a traceable reference, turn its rules into a verified placement matrix, and build clean frames from that interpretation. The result is not merely an editable PDF. It is a template the production team can use without repeatedly translating the same media document under deadline.