The current Fab publishing process feels fragmented and could be improved. We should move toward a unified, single-page publishing interface. Streamlining the workflow into a one-page layout would reduce friction for publishers and bring our UX in line with modern marketplace standards.
The system should automatically identify the file type by parsing the file extension or recognizing naming convention suffixes (e.g., _max, _fbx, _blend). This automated recognition is standard practice across other marketplaces and would significantly improve the publisher experience. Thanks
And there are no appropriate tags for some of my products that I’m publishing.
I agree this process could be streamlined. Something more like how we handle Sketchfab uploads could be good. You can simply throw any file/folder/archive at it and it “just works”.
It gets a little bit tricky if you upload an archive that contains multiple valid files, but I think Sketchfab also handles this pretty gracefully. We have a prioritized list of extensions and will preferentially process them in that order. For example, if you upload a ZIP with an FBX and an OBJ, we will process the FBX for the viewer over the OBJ. I think we could also improve Fab’s upload a format for sale VS upload a file for a 3D viewer VS processing the file for tech details - it should just all happen seamlessly.
That’s not quite as nice in the Fab marketplace context where we want the different format versions separated out nicely, compared to Sketchfab where the main goal is to get a 3D viewer.
We’re also thinking about how to better allow multiple files within the same format, for example if you want to upload several different LODs of FBX or something like that, and they can be distributed individually.
I’m not a huge fan of depending on naming conventions since they then have to be maintained forever.
I completely agree—right now, the publishing process feels a bit clunky. Moving to a single-page workflow would make things much faster and more intuitive. Automatically detecting file types based on extensions or naming conventions would also save a lot of extra steps.
And yes, the tag options are often limited for certain products, which makes organizing them tricky. These changes would really improve the overall experience.
