Polish Onshape CAD views for product reviews, documentation, and marketing images.
Cloud-native CAD for browser-based parts, assemblies, drawings, collaboration, and version-controlled product design
Cloud-native CAD for browser-based parts, assemblies, drawings, collaboration, and version-controlled product design
Onshape teams often use a Part Studio or Assembly view to explain a mechanism, product enclosure, configurable option, or exploded arrangement before the design is final. That view can be an effective starting point for a polished visual when the goal is to communicate the product rather than inspect every CAD detail. RENDERCAD helps turn a clean Onshape viewport capture into a presentation-ready image for a concept review, sales deck, product page, design brief, manufacturing conversation, or documentation. It is especially useful for named views, configurations, section views, and exploded views where the framing already carries important design context. Use it to explore material character, lighting, shadows, and background direction while keeping the visible geometry and view anchored to the Onshape document. When a project needs a maintained, in-document render scene, Onshape Render Studio can instead build a scene from a versioned Part Studio or Assembly with its own appearances, environment, camera, and render settings.
In Onshape, open the Part Studio or Assembly and select the named view, configuration, section view, or exploded view that best communicates the product. Hide sketches, mate connectors, construction geometry, dimensions, comments, and other interface clutter, then frame the model at a clear presentation angle. Capture the clean viewport and upload it to RENDERCAD with guidance on the intended finish, lighting, background, audience, and geometry that must remain unchanged. Review the result against the Onshape view before using it in a product or design communication. For repeatable visual workflows, plan RENDERCAD API implementation through RENDERCAD developer documentation.
Modeled by CADSharp in Onshape. Rendered with RENDERCAD.
Add | Change | or Remove referenced objects with the stroke of a brush.
RENDERCAD uses a maintained selection of image-generation models for different rendering tasks. Results can vary by model and input, so compare generated output with the source design before relying on geometry, materials, or dimensions.
| Feature | RENDERCAD | Onshape Render Studio |
|---|---|---|
| Engine | Generative AI | Cloud-based photorealistic scene rendering |
| Output | Images + Video | JPG and PNG rendered images from Render Studio scenes |
| Resolution | HD / 4K | Custom and view-based image dimensions with selectable aspect ratios |
| Image Speed | Image renders complete in 60 seconds. | Cloud render time varies with model complexity, scene settings, and output size |
| Video Speed | Videos complete in 2-5 minutes. | No native video rendering workflow documented for Render Studio |
| Scene Set Up | No separate local scene | Create a Render Studio tab from a versioned Part Studio or Assembly, then set appearances, environment, camera, and render options |
| Input | Screen Snip | Onshape Part Studios and Assemblies inserted into a Render Studio scene |
| Hardware | Cloud GPU | Onshape browser workflow on supported devices |
| Install | None | No local renderer install; requires eligible Onshape access |
| Cost | from $9/mo | Render Studio availability and advanced features depend on the Onshape access level |
Read the numbers. We trust you to know theirs.
Skip a separate local scene build. Pick a condition, material, and background while RENDERCAD handles the image-generation step. Image renders complete in 60 seconds.
™
RENDERCAD™
Use the browser workflow directly, capture a selected view with the desktop app, or start from the browser extension.
Get StartedCommon solutions for Onshape users
Mask visible components separately when they need different material or color direction. Keep the source model or drawing beside the output because generated boundaries and part relationships can drift.
Yes, when you are authorized to use them. A generated concept can guide the visual direction of a later render, but product fidelity and style consistency still require review.
Describe the tint, transparency, thickness, and lighting direction. Generated absorption and reflections are visual approximations and should not be treated as material simulation.
Upload a clear image, choose the Realistic engine, and describe a large soft light source or overcast lighting. Generated shadows are visual approximations, not a physical lighting calculation.
Yes, use the "Details" field in the video tab to describe elements like "Steam rising" or "Lights flickering."
No local NVIDIA rendering GPU is required. Use a supported browser to upload an image or a current capture tool to select a screenshot; generation runs on cloud infrastructure.
The Render History page lets you browse and download retained images and videos. Storage duration depends on the account plan, so download assets you need before they expire.
Add a familiar scale cue such as a person, hand, or furniture item, then verify the generated relationship against known dimensions in the source model.
The core workflow starts from a selected 2D view, so it does not require native CAD-file conversion or source-model upload.
Reuse a clear history image and change the color instruction or reference. Treat the results as visual options rather than color-managed proof.
Describe the finish, gloss, grain direction, and lighting, or provide an authorized material reference. Generated reflections are visual approximations rather than physically verified material behavior.
It uses generative image models with screenshot or image inputs. Models and features can change over time, so current product documentation is the source of truth.