Unfortunately, Revit’s API doesn’t currently provide a method to bake procedural textures into raster images for export. Procedural materials are defined internally by parameters rather than image maps, and the API has no access to the underlying generation algorithms used by Revit’s material engine.
If you need to export a visual representation, your best option is to render the material (e.g., through the Appearance Asset Rendering in Revit or via external engines like Enscape or Twinmotion) and then capture that rendered result as a bitmap.
Another possible workaround — though limited — is to replicate the procedural material by programmatically generating a texture externally (for example, using Python or .NET image libraries) based on the same parameter values, then assigning it to a new AppearanceAssetElement as a standard image texture.
As of Revit 2025, there’s no direct API access to the procedural texture data or generator. Hopefully, Autodesk exposes this in a future release, since it would open up workflows for material visualization and custom exporters.
