Bugs Found in Tripo 3d AI SaaS
Tripo is a browser-based AI 3D workspace that lets users generate, edit, preview, and export 3D models. The platform lets you create a 3D model from an uploaded 2D image or a text prompt, offering plenty of design flexibility.
Diving deeper into its functionality, Tripo enables users to create high-quality 3D models in real time without specialized equipment. It does this by using cutting-edge AI algorithms that can map with impressive accuracy and detail.
Recently, our QAwerk team conducted a thorough bug crawl of the Tripo platform. We discovered a few bugs that might adversely impact performance and user experience. We invite you to review the findings below and see how addressing these issues can enhance the platform’s overall functionality.
Rigging operation failure with ‘406 Not Acceptable’ message
Severity:
Critical
Precondition:
- Log in to the account.
- Navigate to the ‘3D Workspace’ section.
- Create a model.
- Add texture to the model.
Steps to Reproduce:
- Click on the ‘Rigging’ tab.
- Select the figure with the texture.
- Click on the ‘Auto Rig’ button.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
The ‘3D Rigging & Animation’ (‘Rigging’) feature fails to work, showing an error message with Trace-id: 00-0333aba9a9a4a46605637ea876fb1ecc-403dcd4bbde0e72a-01.
Expected Result:
The ‘3D Rigging & Animation’ (‘Rigging’) feature should function correctly and initiate the rigging process without displaying any error messages.
Incorrect concurrency limit error displayed on ‘Home’ page prompt input
Severity:
Critical
Precondition:
- Log in to the account.
- Generate at least one 3D model.
Steps to Reproduce:
- Navigate to the ‘Home’ page.
- Enter the prompt for generating a 3D model in the input field.
- Click the button to start generation.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
Even though the user has sufficient coins, the system erroneously displays the following message in the ‘Home’ page prompt input: ‘Concurrent task limit reached. Please upgrade your plan or wait until the task is completed.’ When the same prompt is submitted directly in the 3D Workspace, this error does not occur.
Expected Result:
The ‘Concurrent task limit reached’ message should not be displayed when the user has sufficient coins and has not actually reached the active task limit. The prompt submission should proceed smoothly before the generation process, as it does in the 3D Workspace.
Credits erroneously reset to 300 and deductions don’t match usage history
Severity:
Critical
Precondition:
- Log in to the account.
- Use a certain number of credits.
- Don’t use the account for several months.
Steps to Reproduce:
- Log in to an account that was created a few months ago.
- Check your balance.
- Navigate to the ‘3D Workspace’ section.
- Create a model.
- Check your balance.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
Approximately 3-4 months after creating an account with 300 credits and using roughly 180 of these credits, the balance should have been 120. However, upon returning to the account later, the credit balance inexplicably reverted to 300, despite no recorded credit increase in the Usage History. Although a new model could be generated for a 20-credit deduction, the deduction appeared to be applied to the incorrect reset balance of 300. As a result, the account balance post deductions should be 100 credits, but 280 is displayed, highlighting a discrepancy between the expected and actual credit balance.
Expected Result:
The credit balance should consistently reflect the exact number of remaining credits over time. Any instances of credit addition (for example, promotional additions, top-up contributions, or resets) must be accounted for in the Usage History or within a specified credit addition log.
Generated 3D model doesn't display immediately after generation
Severity:
Major
Precondition:
Log in to the account.
Steps to Reproduce:
- Navigate to the ‘3D Workspace’ section.
- Select the ‘Text to model’ in the query input option.
- Enter aprompt in the prompt input field.
- Click on the ‘Generate model’ button.
- Wait for the request to finish processing.
- Refresh the page manually.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
The generated 3D model fails to display automatically after the generation completes. It only becomes visible after the page is manually refreshed.
Expected Result:
A newly generated 3D model should automatically appear in the viewer/assets list without requiring a manual page refresh.
Component in rendered 3D model is absent, despite being present in the input image
Severity:
Major
Precondition:
- Log in to the account.
- Download the logo to your computer (https://bugcrawl.qawerk.com/wp-content/uploads/2026/01/qawerk_logo.png).
Steps to Reproduce:
- Navigate to the ‘3D Workspace’ section.
- Select the query input option ‘Image in model’.
- Add the logo Image.
- Click on the ‘Generate model’ button.
- Wait for the request to finish processing.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
The generated 3D model is missing a part that is clearly present in the input image (for example, a letter or segment), so the result does not match the reference.
Expected Result:
All visible components in the input image, including the missing segment or letter, should be accurately represented in the generated 3D model, with the geometry closely matching the reference.
User is not automatically logged in after sign-up until page refresh
Severity:
Major
Precondition:
Open https://www.tripo3d.ai/.
Steps to Reproduce:
- Click on the ‘Try Tripo Studio’ button.
- Click on the ‘Sign up/Log in’ button.
- Enter an email address you have access to.
- Click on the ‘Send code’ button.
- Open your inbox.
- Open the email (may be in spam).
- Copy the code.
- Return to the login screen.
- Paste the code.
- Click on the ‘Login’ button.
- Enter a request.
- Click on the send button.
- Refresh the page manually.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
After completing registration, the user is not automatically logged in. The user must refresh the page to log in.
Expected Result:
Following successful account registration, the user should be automatically logged in (session/token applied) without needing to manually refresh the page.
Disparity in colors between textured 3D model and input image
Severity:
Minor
Precondition:
- Log in to the account.
- Download the logo to your computer (https://bugcrawl.qawerk.com/wp-content/uploads/2026/01/qawerk_logo.png).
Steps to Reproduce:
- Navigate to the ‘3D Workspace’ section.
- Select the query input option ‘Image in model’.
- Add the logo Image.
- Expand the ‘Texture Settings’.
- Toggle the ‘PBR’ switch to the on position.
- Click on the ‘Generate model’ button.
- Wait for the request to finish processing.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
The generated textured 3D model colors do not match the input image. For example, the left logo is red/black in the source image, but the generated result shows it as white/gray.
Expected Result:
When generating a textured 3D model from an input image, the resulting textures should preserve the main colors of the reference (for example, the logo colors should match the source image as closely as possible).
Credit return is displayed as negative value in ‘Usage History’
Severity:
Minor
Precondition:
- Log in to the account.
- Navigate to the ‘3D Workspace’ section.
- Create a model.
- Add texture to the model.
Steps to Reproduce:
- Click on the ‘Rigging’ tab.
- Select the figure with the texture.
- Click on the ‘Auto Rig’ button.
- Refresh the page.
- Check the credit balance.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
In ‘Usage History’, entries marked as ‘Failed (Credit Returned)’ display the returned credits as a negative value (for example, -25). This suggests an additional charge instead of a refund.
Expected Result:
When a task fails, and credits are returned to the user, the amount returned should be displayed as a positive value (e.g., +25) or clearly marked as a refund/credit. This way, users can clearly understand that the credits were added back to their account.
Grid disappears after camera reset and can’t be restored without page reload
Severity:
Minor
Precondition:
- Log in to the account.
- Download the logo to your computer (https://bugcrawl.qawerk.com/wp-content/uploads/2026/01/qawerk_logo.png).
Steps to Reproduce:
- Navigate to the ‘3D Workspace’ section.
- Select the query input option ‘Image in model’.
- Add the logo Image.
- Click on the ‘Generate model’ button.
- Wait for the request to finish processing.
- Click on the ‘Grid’ button.
- Rotate the image.
- Click on the ‘Camera Reset’ button.
- Click on the ‘Grid’ button.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
After resetting the camera, the grid disappears from the ‘3D workspace’. It becomes impossible to restore the grid through the User Interface. Refreshing or reloading the page is the only way to make the grid appear again.
Expected Result:
The grid should remain visible in the 3D scene after a camera reset. If it becomes hidden, there should be an option in the User Interface to turn it back on without refreshing or reloading the page.
Incorrect model loads when opening from ‘Home’ page
Severity:
Minor
Precondition:
Log in to the account.
Steps to Reproduce:
- Navigate to the ‘Home’ page.
- Click on any model.
- Click on the ‘Back’ button.
- Scroll down the ‘Home’ page.
- Click on any other model.
- Wait for the model to load.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
When opening a model from the ‘Home’ page, the app displays the previously opened model instead of the one the user clicked.
Expected Result:
When the user selects and loads a model from the ‘Home’ page, it should open and display correctly.
Inadequate padding between user input and the cost indicator
Severity:
Trivial
Precondition:
Log in to the account.
Steps to Reproduce:
- Navigate to the ‘Home’ page.
- Enter prompt text for generating a 3D model in the input field.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
The spacing between the prompt text entered by the user and the price/credits cost label is too small so theuser interface appears cramped, making the text difficult to read.
Expected Result:
The prompt text and the price/credits cost label should have enough (padding/margin) so they don’t look cramped or visually overlap, and the input remains easily readable.
Export menu displays incorrect format label for USDZ
Severity:
Trivial
Precondition:
Log in to the account.
Steps to Reproduce:
- Navigate to the ‘3D Workspace’ section.
- Select the query input option ‘Text to model’.
- Enter a prompt in the prompt input field.
- Click on the ‘Generate model’ button.
- Wait for the request to finish processing.
- Click on the ‘Export’ button.
- Expand the drop-down menu with formats.
- Click on the ‘USD’ option.
- Click on the ‘Export’ button.
- Expand the download.
Environment:
OS: Windows 10 Pro
Browsers: Chrome v.144.0.7559.60, Firefox v.147.0, Microsoft Edge v.143.0.3650.139
Actual Result:
The export menu displays an incorrect label (‘USD’ instead of ‘USDZ’) for the USDZ format.
Expected Result:
The export format list should display the correct format name, USDZ, with accurate spelling.
When testing Tripo, I found some critical issues in key flows, such as rigging failures (API 406), generated results and post-sign-up sessions requiring a page refresh, and the platform sometimes opening the wrong model. I recommend validating functional and non-functional requirements through end-to-end user-journey testing and risk-based regression testing, with a special focus on credit/billing reconciliation and session/state persistence to improve the platform’s performance and reliability.
