Skip to main content

known issues

  • Each layer name must be unique ; otherwise, you might see strange results!

  • Make sure to use the colon “:” correctly. if it’s missing or misplaced, the layer might show up with an unexpected color or thickness. I’ve tried to make the app error-tolerant, but you know.

  • Images are not yet supported: Currently, NearSolid does not process images. If an image is part of the SVG, it will be ignored. We are working on this feature.

  • Open paths may produce unexpected results: NearSolid requires closed shapes for extrusion. If you need a quick mockup, consider converting an open line into a shape, even if it’s very thin. Depending on your software, you can use a function like "Expand Stroke", which turns the line into a shape.

  • SVG specification supports gradients and image patterns, but NearSolid does not (yet!): At the moment, we cannot display these styles in NearSolid.

  • NearSolid is not meant for "superb high-quality renders": It's designed to provide a good enough approximation that runs smoothly in a web browser. If you need a higher-quality render, try exporting the NearSolid-generated model as GLTF and importing it into Blender.

  • Sometimes things can go wrong: A shape with too few points might not properly detect the previous layer. If this happens, try adding an extra point or vertex to help NearSolid recognize the object.

  • Need help? If you're having trouble with a specific file or design, feel free to reach out at victor@nearsolid.com and I'll do my best to assist you!