An architecture studio often has years of strong work trapped in one polished PDF. The original InDesign file is missing, project photographs live in scattered folders, and the next bid needs a shorter portfolio with new team credits by Friday. Rebuilding every page from screenshots is fast until text needs editing, drawings look soft, and nobody knows whether a consultant was credited correctly.
Convertify can import supported PDF content into Figma, including editable text where the source permits it. Conversion is a recovery step, not a declaration that the PDF is complete, current, or legally reusable. Architecture portfolios need a deliberate audit because drawings, photography, project facts, and authorship carry different risks.
Inventory the portfolio before conversion
Record the PDF filename, publication date, page count, intended page size, and known source files. Then create a project ledger with:
- official project name and location;
- completion status and date;
- client-approved description;
- studio role and project team;
- architects, engineers, photographers, and other required credits;
- image and drawing rights;
- confidentiality or embargo restrictions;
- current source of truth for areas, costs, and sustainability claims.
Do not assume the PDF is authoritative just because it is beautifully typeset. A proposal portfolio may contain projected completion dates, concept renders, or simplified role descriptions that became inaccurate later.
Import a representative section first
Before converting the entire document, test pages that expose the difficult material:
- a photograph-led project opener;
- a page with plans, sections, or fine linework;
- a dense project-data page;
- a spread with full-bleed imagery;
- a page using unusual fonts, masks, transparency, or rotated text.
Import those pages with Convertify, then compare them with the original PDF at the same size. Check text editability, line breaks, image crops, clipping paths, vector strokes, gradients, and font substitutions. If the PDF contains flattened pages, conversion cannot recreate missing semantic structure or original high-resolution assets.
This workflow is narrower than the general PDF design extraction workflow and different from real-estate brochure migration. A studio portfolio needs project authorship, drawing legibility, reusable project modules, and multiple bid-specific editions.
Rebuild a system, not a pile of imported pages
Create Figma styles and components after the representative test reveals the document’s real patterns. Useful components might include:
- project opener;
- project facts panel;
- image with caption and credit;
- plan or section with scale note;
- quote or award block;
- team and collaborator credits;
- contents and section divider.
Keep imported pages in a locked reference section. Reconstruct the live pages with named components and predictable text styles. This creates a maintainable source while preserving a visual benchmark for reconciliation.
Avoid forcing every old project into one identical template. A built project with professional photography, a competition entry with diagrams, and an urban strategy project may need different evidence. Standardize the information contract and typography, not the story itself.
Recover drawings and images at useful quality
Inspect plans and sections at intended print size. Thin strokes may disappear, screened fills may merge, and tiny labels may become unreadable after conversion or later PDF compression. Confirm whether a scale bar remains valid; a numerical scale such as 1:200 becomes misleading when the page is resized.
For photographs, search for the approved originals rather than accepting images extracted from the PDF. Record the chosen crop, photographer credit, color treatment, and usage limits. Do not use generative enlargement to invent facade or site detail. If only the PDF image exists, label that constraint and test it in the final output.
Keep renders visibly distinguishable from completed-project photography. Review image captions for design stage and completion status so a proposal does not accidentally present unbuilt work as built work.
Reconcile facts and credits project by project
Use a review table rather than relying on visual sign-off:
| Field | Legacy PDF | Verified source | Final Figma page |
|---|---|---|---|
| gross floor area | 8,200 m² | 8,460 m² | 8,460 m² |
| studio role | architect | design architect | design architect |
| photographer | omitted | Mei Chen | Mei Chen |
| status | under construction | completed 2024 | completed 2024 |
Ask a project lead to review claims, a marketing owner to review narrative, and the rights owner to review images and credits. The designer should not have to guess which historical number is safe to publish.
Prepare bid-specific editions without source drift
Maintain one approved project library, then assemble editions by sector, region, capability, or bid requirement. Do not duplicate whole Figma files for every proposal if corrections will never flow back.
Tag project pages with useful selection data: typology, scale, status, geography, services, certifications, and permission level. When a project description or credit changes, update the governed source before generating the next edition.
Export a short proof and inspect it in the medium that matters. For print, check trim, bleed, spreads, fine lines, image resolution, color expectations, and binding. For screen delivery, check file weight, links, page navigation, and readability on a laptop. The legacy design cleanup checklist is useful for the broader post-import pass.
Migration completion criteria
The recovery is complete when:
- representative pages have been compared against the PDF;
- fonts and substitutions are documented;
- project facts, roles, credits, and status are verified;
- high-resolution approved images replace extracted previews where available;
- drawings remain legible at final size and scale language is accurate;
- page patterns are rebuilt as reusable Figma components;
- imported reference pages remain available for reconciliation;
- bid-specific editions draw from one governed project source;
- a real exported proof has passed print or screen review.
The goal is not to make the old PDF editable at any cost. It is to recover enough structure and evidence that the next portfolio can be accurate, adaptable, and easier to maintain than the document it replaced.
Read as Markdown Related resource index Site index for AI agents
Pro Bundle