Submit Feedback and Feature Requests

VidBlitz uses user feedback to understand what real users need, where workflows are painful, and which improvements matter most.

What Counts as Feedback

Feedback should come from a user need or workflow problem. Use feedback for:

• Bug reports for something broken.
• Feature requests for a new capability you want.
• Integration requests for tools or workflows you want connected.
• Workflow problems where the current product makes your work harder.

Feedback is different from the roadmap. Roadmap items are planned product work owned by the VidBlitz team. User feedback can influence the roadmap, but planned roadmap items should not be submitted as if they came from users.

Write a Good Feature Request

Include:

• What you want to do.
• Why it matters.
• How often you would use it.
• What workaround you use today.
• Example projects or workflows affected.

Good request: I want to create vertical Shorts from finished long-form videos so I can repurpose clips without rebuilding the project in another editor.

Weak request: Add Shorts.

Report a Bug

Include:

• What you clicked.
• What you expected.
• What happened instead.
• Workspace and project title.
• Screenshot or video if possible.
• Browser and device if the issue looks device-specific.

Vote on Existing Ideas

If a similar user idea already exists, vote on it instead of creating a duplicate. Add a comment with your use case if you have more context.

What Happens Next

Some feedback stays open while the team learns how many users need it. Some feedback may influence planned roadmap work. Completed improvements may be linked to changelog updates when released.

Roadmap items should be followed in the Roadmap area, not treated as user-submitted feedback.