Reference Formats
SKP
The proprietary native project format of SketchUp, a widely used architectural and interior-design 3D modeling tool, storing geometry, materials, components, layers, and scenes in a closed binary structure.
Extension
.skp
Full name
SketchUp Document File
Introduced
2000, with the launch of @Last Software's SketchUp
Vendor
@Last Software (acquired by Google in 2006, then Trimble in 2012)
What is inside the container
A .skp file stores SketchUp's characteristic 'push-pull' polygon geometry, applied materials/textures, reusable nested 'components' and 'groups,' organizational layers, saved camera scenes, and optionally embedded 2D image entourage. Unlike open interchange formats, SKP's binary structure is proprietary and undocumented by Trimble, meaning third-party support depends on reverse-engineered libraries rather than an official public specification — a meaningful risk factor for long-term archival compared to open formats like STEP or glTF.
How to open it
For archives
Because SKP is a closed, proprietary format with no official public specification, a DAM relying on long-term SKP archival carries real format-risk that open formats like STEP or glTF don't — third-party parsing depends on reverse-engineered tools that can lag behind SketchUp's own format revisions. For architecture, interior design, and real-estate DAM use cases where SKP is unavoidable (it remains the dominant format for that market), best practice is retaining the native .skp alongside an exported, open-format derivative (glTF or COLLADA) specifically for long-term accessibility. As with other 3D formats, native in-DAM preview isn't available without a dedicated viewer or an embed of Trimble's own 3D Warehouse/SketchUp for Web preview capability.
SketchUp, and its native .skp format, launched in 2000 from @Last Software, a small startup that built the tool around an unusually approachable ‘push-pull’ modeling interaction aimed at architects and designers rather than dedicated 3D specialists. That accessibility made SketchUp popular quickly, and Google acquired the company in 2006, integrating SketchUp with Google Earth and building out the 3D Warehouse as a public library of shared .skp models — a pairing that made SketchUp arguably the most widely used entry-level architectural 3D tool of its era.
Google sold SketchUp to Trimble, the positioning and construction-technology company, in a deal announced in April 2012, and Trimble has continued developing it since, including a modern browser-based SketchUp for Web. Throughout these ownership changes, the .skp format itself has remained proprietary and closed — Trimble has never published an official public specification, so all third-party support (Blender importers, viewers, converters) relies on reverse-engineered understanding of the format rather than documented cooperation.
For a DAM, SKP is unavoidable in architecture, interior design, and real-estate visualization workflows, where it remains the dominant modeling format despite the rise of BIM tools like Revit. The proprietary, closed nature of SKP is a real long-term archival concern worth flagging explicitly to stakeholders — a DAM managing significant SKP libraries should pair the native file with an exported open-format derivative (COLLADA or glTF) specifically to reduce dependency on continued third-party format support.
Frequently asked
Is the SKP format openly documented, or proprietary to Trimble?
It's proprietary and closed — Trimble has never published an official public specification, so third-party tools support it through reverse-engineered parsing rather than documented cooperation, which is a real long-term archival risk factor.
Why is SKP so dominant specifically in architecture and interior design DAM libraries?
SketchUp's approachable 'push-pull' modeling interface made it the entry-level standard for architects and designers since 2000, and Google's later 3D Warehouse integration cemented it as the most widely shared format in that space.
Should a DAM keep only the .skp file, or also an open-format export?
Given SKP's closed, proprietary structure, best practice is retaining the native .skp for editing plus an exported open-format derivative like glTF or COLLADA specifically to reduce long-term dependency on third-party format support continuing to work.
Can a DAM preview SKP files without SketchUp installed?
Only through Trimble's own SketchUp for Web or the public 3D Warehouse viewer, or a third-party reverse-engineered viewer — there's no universal, vendor-independent SKP renderer the way there is for open formats.
What organizational features does SKP support that matter for DAM cataloging?
Nested 'components' and 'groups' for reusable geometry, layers for organization, and saved camera 'scenes' — a DAM cataloging SKP assets can extract this structure to describe the model's internal organization, not just its overall geometry.
Who owns SketchUp and the SKP format today?
Trimble, the positioning and construction-technology company, which acquired SketchUp from Google in a deal announced in April 2012; Google had acquired the original developer, @Last Software, in 2006.
Does SKP support embedded textures and materials?
Yes, materials and texture images are stored within the .skp project, along with the geometry, layers, and components — making it more visually complete than a pure geometry format like STL, though still closed-format.
How does a DAM handle version compatibility for SKP files across SketchUp releases?
SketchUp files are generally forward-compatible within reason, but very old .skp versions can require an intermediate SketchUp version to open in the current release — a DAM should record the SketchUp version an asset was saved with.
Sources
- The SketchUp SKP file format was developed and launched in 2000 by @Last Software, acquired by Google in 2006 checked 2026-08-07 — FileFormat.com — SKP File Format
- Trimble announced on April 26, 2012 that it would acquire the SketchUp 3D modeling platform from Google checked 2026-08-07 — Equipment World — Trimble acquires Google SketchUP 3D modeling platform