DEV Community: Elias Larsen

Hyper3D Credits Review 2026: Half a Credit, No Gen-2.5 Download

Elias Larsen — Mon, 12 Oct 2026 15:50:04 +0000

This is an independent test. Nothing here came from vendor access: both tools were used on my own free and paid accounts.

I set out to obtain one knitted-tray model and record what the tested workflows actually charged. I ended up with two Hyper3D generations, one real ZIP, one blocked Download button and two charges that must stay on separate lines.

The first run used Hyper3D Gen-2.5. It took 0.5 Hyper3D credit, produced a preview, and then the tested Free account was told to subscribe before downloading it. I tried again with Gen-1.5 and the same picture. Its preview cost nothing on the observed balance; Geometry Confirm cost another 0.5; Material Generate and Confirm caused no further recorded debit. That second run really did deliver a PBR file. SupaVoxel quoted 3 of its own credits before generation and a request-linked transaction confirms exactly that debit; its Original size browser export subsequently failed.

My verdict in 60 seconds — SupaVoxel wins the pre-submit quote and concept-inspection loop; Hyper3D Gen-1.5 wins this tested delivery. SupaVoxel showed “Generate (3 credits)” before I uploaded the image, made one model and offered Textured, Mesh, Wire and Normals views. The request-linked −3 transaction matched the quote. But the Original size browser export failed, whereas Hyper3D's separate Gen-1.5 run put a ZIP on disk. For choosing and inspecting a direction with a visible charge first, SupaVoxel is my pick; for this exact Free-tier requirement of a file in hand, use the Hyper3D branch that actually downloaded. These credits cannot be exchanged or treated as comparable dollars.

Eight paired observations, not a weighted price score:

Pre-submit quote — Hyper3D: stage-specific debit observed later · SupaVoxel: 3-credit Generate quote visible before upload.
Number of generations in this journey — Hyper3D: blocked Gen-2.5, then separate Gen-1.5 · SupaVoxel: one identified project.
Higher-generation access — Hyper3D: Gen-2.5 charged 0.5, then download-gated · SupaVoxel: no comparable generation-tier gate tested.
Requested browser file — Hyper3D Gen-1.5: ZIP received · SupaVoxel Original size: export failed.
Attributable debit — Hyper3D: separately reconciled half-credit stages · SupaVoxel: request-linked −3 transaction.
Material work — Hyper3D: Generate then Confirm, no added debit here · SupaVoxel: completed textured project under its one transaction.
On-screen inspection — Hyper3D: model preview and mesh information · SupaVoxel: Textured, Mesh, Wire and Normals modes.
Format menu versus receipt — both showed options; only Hyper3D's selected Gen-1.5 route delivered the requested file.

Do not divide three credits by half a credit to choose a subscription. Each platform's own observed charge and actual entitlement are the only supported billing facts.

The invoice starts with two separate runs

The image file was byte-identical for the two products, but Hyper3D was tested twice: Gen-2.5 first, Gen-1.5 after its download gate. SupaVoxel was tested once. Hyper3D generated different automatic descriptions and used different generation settings between its two versions, so we do not treat these as the same pipeline at two selectable output resolutions. The exact shared source was a 1,862,608-byte PNG showing a shallow knitted tray with an oval opening on one visible side. Two Hyper3D geometry debits sum to 1.0 credit for this researcher's two-run journey; dividing that by the single accessible PBR file gives a journey cost, not a universal per-file tariff.

One shared input; the separate Gen-2.5 and Gen-1.5 attempts must remain separate billing lines.

Gen-2.5 spent a credit fraction before its export gate

The Hyper3D account showed 1.5 credits before the Gen-2.5 run and 1.0 after generation and confirmation: a verified 0.5 debit attributable to this attempt. We retained separate task intervals of 56.930 seconds for its preview generation and 32.878 seconds for geometry confirmation. Neither includes upload, hand-clicks, material work or download. A one-million-face number on a Gen-2.5 information panel is not a measured asset here because the Free account never received that generation's model. This is precisely the access surprise: a visible, paid-for preview need not be a downloadable file.

The Gen-2.5 choice and 1.5-credit starting balance are visible before this distinct run.

The separate confirmation phase is in progress; do not relabel the two measured intervals as end-to-end delivery.

The download button was not the entitlement

The Gen-2.5 preview looked like the end of the job. The Pack screen showed Download. I clicked it and found the real condition: subscribe to download Gen-2.5; Gen-1.5 stays free. By then this run had used 0.5 credit, but there was no Gen-2.5 GLB to send to a product photographer or web developer. I did not use another route to fetch it. That spent half-credit is this particular false start, not a standard surcharge on every Gen-1.5 tray. If you're building a client listing, learn the file entitlement before polishing the preview.

The actual click exposed the subscription restriction after this Gen-2.5 attempt had spent 0.5 credit.

Gen-1.5 preview cost zero in this ledger

We selected the older Gen-1.5 mode and submitted the same PNG anew. The recorded Hyper3D balance was 1.0 before the preview, 1.0 once the preview had finished and 0.5 only after Geometry Confirm. Thus this case supports “the Gen-1.5 preview itself did not debit” and “confirmation debited 0.5,” not “generating always costs 0.5 at submission.” Its task/card intervals are 31.281 seconds for preview and 24.773 for Geometry Confirm, or 56.054 seconds for those two known stages together. No complete material-generation interval was captured, so 56.054 seconds is deliberately not the total time to a textured export.

Gen-1.5 Preview was still in flight at the unchanged 1.0 balance.

The 1.0-to-0.5 change belongs to Geometry Confirm, before the material path was finished.

Material was a workflow gate, not an extra debit here

A Material panel asked for a distinct Generate click and then a Confirm click. We checked the same account around each step: before and after Generate, 0.5 to 0.5; before and after Confirm, 0.5 to 0.5. The delivered Gen-1.5 PBR file in this case therefore incurred 0.5 verified Hyper3D credit including those two zero-debit material steps. This does not establish a universal free-material tariff. No pre-material geometry-only file was saved, so its size is unknown. The observed downloadable material option was 2K, with Shaded and PBR selected; the visible 4K option was unavailable to the Free account.

Material Generate adds an action and unmeasured total wait, not an observed extra charge in this run.

Confirmed material unlocks the 2K PBR and Shaded selections while this tested balance remained 0.5.

Asking for GLB delivered a ZIP

The Hyper3D sequence after geometry confirmation was Material Generate, Material Confirm, select .glb, then Download: four observable actions. SupaVoxel displayed a three-step menu path to its Original size option, but the browser conversion failed at that last action. “Three beats four” would therefore be a misleading delivery claim. The Hyper3D browser actually received a ZIP of 27,809,936 bytes. Its two contained files are not interchangeable: an 18,642,076-byte PBR GLB used for material and geometry measurements, plus a 9,167,608-byte Shaded GLB. If a publishing workflow requires just PBR, it must receive and unpack the ZIP first. The webpage transfer is the ZIP's 27.81 MB, not the extracted PBR member's 18.64 MB.

GLB with PBR and Shaded selected was the actual Export interaction that yielded the verified ZIP.

SupaVoxel's debit has a narrower, stronger identity

The SupaVoxel interface showed “Generate (3 credits)” before the test image was placed into its one primary slot, and still showed 3 after upload. The completed request was matched to the uploaded image's SHA-256 and an independent debit transaction of -3 SupaVoxel credits. This is stronger evidence for this one job than subtracting a shared test-account header balance used across many cases. We did not capture its precise charge moment relative to submission and completion; claiming it billed at either instant would invent a timeline. The transaction establishes what this case cost in its own internal units, while the UI established that its quoted price was visible at the start.

The quoted 3-credit Generate action is present before the image upload.

After loading the matching image, the displayed quote remains 3; the bill is verified by the separate transaction.

The two clocks measure different intervals

SupaVoxel's request was created and last updated 329.805 seconds apart, measured by subtracting its two stored timestamps. That interval includes queue time but excludes the preceding upload and subsequent export. Hyper3D's Gen-1.5 known 56.054 seconds combines only preview generation and geometry confirmation and lacks the material-generation span, interface actions and download. Hyper3D's Gen-2.5 56.930 plus 32.878 seconds are likewise just two stages of a different, blocked run. Comparing 56.054 to 329.805 to declare a 5.9-fold end-to-end speed victory would compare nonmatching phases. The elapsed time from image upload to both completed files was not captured; in particular, no SupaVoxel Original size file completed the browser export.

SupaVoxel's progress and estimated minutes are a waiting-state screenshot, not the measured end-to-end time.

Free account capacity is a limit, not a bulk promise

A new Hyper3D Free account's 5-credit starting grant would fund at most ten 0.5-credit Gen-1.5 confirmations, assuming no Gen-2.5 attempt, other debits or replenishment. This case's zero-debit material stages are not a bulk entitlement. One hundred hypothetical copies at the same charge require 50 Hyper3D credits, not a five-credit Free grant. We neither bought that entitlement nor ran the batch.

The downloadable Gen-1.5 PBR asset is the actual file behind the hypothetical ten-confirmation arithmetic.

The SupaVoxel model shown in the generation workspace; the analysis GLB pictured here was rebuilt locally after Original size browser export failed.

Multiply the right costs, never the wrong currencies

For 100 identical successful jobs at this case's charge, the hypothetical bills would be 50 Hyper3D credits for PBR files if both material stages stayed zero-debit, and 300 SupaVoxel credits. That is not a sixfold dollar comparison: tariffs and entitlements differ, and neither batch was run. The blocked Gen-2.5 debit belongs to this experiment, not every future Gen-1.5 file.

The higher-generation preview was visible; it was not one of the 100 hypothetical downloadable PBR files.

Delivery risk remains on both sides of the ledger

The Hyper3D Gen-1.5 PBR was obtained and independently parsed; its webpage transfer is known. Gen-2.5 was previewed and charged but cannot be called delivered. The SupaVoxel generation itself succeeded and its compressed project source was retained, yet the Original size browser export conversion crashed. A 74,362,796-byte GLB was reconstructed locally from that retained source for analysis; we did not receive those bytes through the site's Original size download action, nor can we promise byte-identical output from a working browser. The downloadable format row in a menu is not a receipt. When budgets require deliverables rather than previews, this single tested workflow favors the actual Hyper3D Gen-1.5 ZIP, while telling a SupaVoxel user to validate the chosen export route before planning downstream work.

SupaVoxel offers Compressed and Original size choices; this test did not successfully save the latter from the browser.

Final verdict: bill a deliverable, not a preview

I would not call Hyper3D's two runs a one-credit tariff. One 0.5-credit Gen-2.5 run led to a blocked Free Download; a separately created 0.5-credit Gen-1.5 model yielded the real ZIP, and its two material steps made no additional debit in this case. The late gate is worth knowing before spending either time or credits. SupaVoxel's single identified request cost 3 of its own credits, visible as a quote before submission, and exposed four model-inspection modes. Its intended Original size browser export failed this time, so the 74.36 MB analysis reconstruction must never enter the ledger as delivered bytes.

For concept inspection, SupaVoxel's one project and visible pre-submit quote matter. For delivering this exact file from the tested browser, reverse the preference: Hyper3D's ZIP is in hand and SupaVoxel's Original size export is not. Neither internal-credit unit translates into the other's cash cost.

Use SupaVoxel for this job

Start with SupaVoxel if you need to quote the 3-credit action up front, generate one tray and inspect its textured and mesh views before deciding whether the knit is worth refining. Test your required download path right away; my Original size attempt crashed. If an actual Free-tier PBR file today is the binding constraint, use Hyper3D Gen-1.5 rather than assuming Gen-2.5's paid preview includes export rights.

How I tested this

Both products received the same independently generated 1,862,608-byte PNG. Hyper3D Gen-2.5 moved from 1.5 to 1.0 credits in its first, download-blocked run; a second Gen-1.5 run held at 1.0 through preview, fell to 0.5 at Geometry Confirm, and held at 0.5 through Material Generate and Confirm. A 27,809,936-byte ZIP was browser-downloaded for that second run. SupaVoxel's −3 debit was linked to the input-matched project transaction; a shared account header is not a case ledger. Its 329.805-second database request interval includes queueing but excludes upload and export; Hyper3D's 56.054 seconds are only known Gen-1.5 preview and geometry-confirm stages, with the material-generation span missing. There is no comparable end-to-end timer, cash conversion or measured hundred-job entitlement. All batch numbers here are one-sample multiplications, not an executed order.

Hyper3D 3D Print Review 2026: The Floor Cables Became Ribs

Elias Larsen — Sat, 10 Oct 2026 16:07:22 +0000

This is an independent test. Nothing here came from vendor access: both tools were used on my own free and paid accounts.

I set out to test one question with a shallow knitted-tray reference: would its handle holes, rope-patterned wall and large crossing floor cables survive as actual shape? A good-looking preview alone would not answer a geometry question.

I gave the same reference image to Hyper3D and SupaVoxel, then stripped the colors off the two inspectable models. There was a catch before I even got to the mesh: Hyper3D's newer Gen-2.5 charged for a preview that my tested Free account could not download. The Hyper3D file I could inspect came from a separate Gen-1.5 run; the SupaVoxel comparison file was reconstructed locally after its Original size browser download failed.

My verdict in 60 seconds — both are repair-first meshes, and Hyper3D Gen-1.5 wins this tested print-file handoff. Both welded meshes close, but neither floor follows the photographed cable crossings. Hyper3D gives you raised but oversimplified ribs and an actual Free-tier PBR download. SupaVoxel earns a conditional recommendation for a finer-wall design prototype: finer diagonal wall relief, 1,375 fewer sliver faces and an estimated $0.59 less solid resin at the same outer scale. Explore SupaVoxel if that narrower wall-and-material brief is yours, but verify its required browser export and remodel the floor before printing. That is not a claim that it beat Hyper3D on this tray's printable cable geometry.

Eight paired evidence checks for the tray:

Recognizable open tray — Hyper3D: shallow basin and apertures · SupaVoxel: shallow basin and apertures.
Wall texture in bare geometry — Hyper3D: chunky raised ropes · SupaVoxel: finer visible diagonal relief.
Photographed floor crossings — Hyper3D: mostly parallel ribs · SupaVoxel: irregular patches; neither shows repeated over-under cables.
Floor relief without color — Hyper3D: raised rows remain · SupaVoxel: much of the apparent puff fades.
Welded solid topology — Hyper3D: one watertight shell, no nonmanifold edges · SupaVoxel: the same narrow topology result.
Triangle hygiene — Hyper3D: zero degenerates, 5,048 slivers · SupaVoxel: 60 degenerates, 3,673 slivers.
Estimated solid resin — Hyper3D: 63.96 cm³ · SupaVoxel: 47.00 cm³ at a 120 mm longest side; no physical print.
Actual browser export — Hyper3D Gen-1.5: ZIP received · SupaVoxel Original size: failed in this run.

Those checks describe starting materials, not a printable-product certificate. I neither sliced nor printed either tray.

The image is a raised tray, not a flat swatch

We used the exact same 1,862,608-byte PNG for both products and checked its SHA-256 against the SupaVoxel request input. It was independently generated with a maker-gallery cover as visual reference, not an existing 3D model downloaded and submitted as an answer. The photograph-like input shows an open circular tray with a visible wall, chunky crossing cables across the floor and wall, and an oval aperture on the right. The left and reverse faces are obscured. Calling this a flat texture test would erase the wall, openings and height that a printer must actually realize. At 120 mm normalized longest side, the two resulting tray heights are only 24.48 and 20.71 mm—not 120 mm high.

One shared input, one visible right-hand opening; the hidden hole positions have no photographed ground truth.

Which Hyper3D mesh can actually be tested?

Hyper3D let the Free account generate and confirm Gen-2.5, and its UI later displayed a million-face preview. Clicking Download instead displayed a subscription requirement; no Gen-2.5 model was retrieved. Its 1,000,000-face and 766,963-vertex readout is consequently a UI claim, not our offline mesh measurement. We made a separate Gen-1.5 run, finished Material Generate and Confirm, and received a 27,809,936-byte ZIP with Shaded and PBR models. Every Hyper3D mesh metric here belongs to the extracted 18,642,076-byte Gen-1.5 PBR GLB, not to the blocked higher-generation preview. A buyer choosing the free path gets the smaller inspected mesh, not evidence of the inaccessible one's printable geometry.

The Gen-2.5 download restriction appeared after the preview and confirmation; we did not bypass it.

The floor fails the literal cable test

The top-view render makes the mismatch obvious: the reference has cords weaving across one another like a knitted jumper. From above, Hyper3D's floor has raised rows—but they travel side by side, rarely crossing. SupaVoxel draws a denser scatter of soft-looking stitches without the large, repeatable over-under route. Its analysis mesh has 1,500,000 triangles against Hyper3D's 120,000. That's 12.5 times as many triangles, but no extra triangle can follow a cable path the generated shape never laid down. If the buyer ordered this exact knit, someone still has to remodel the floor.

Hyper3D's raised directional rows are recognizable, but the crossings have become parallel ribs.

SupaVoxel's top view is denser and less orderly than the input's repeated large cables.

Turn off the material before promising a print

The Hyper3D bare-mesh render still contains protruding wall cables, multiple open holes and some raised floor ribs. That is real geometry, not just a painted illusion; it is also a simplified pattern. The SupaVoxel bare-mesh render retains fine diagonal relief on the wall and the side openings, but the floor loses much of the clustered texture's apparent depth. The 1.5-million-triangle total therefore does not mean 1.5 million useful pieces of cable relief. At the chosen 120 mm scale the average triangle edge is 1.1313 mm in the Hyper3D file and 0.2357 mm in the SupaVoxel file. Neither average establishes the width of the smallest printable groove or whether a 0.4 mm nozzle will resolve the desired knit.

Hyper3D without material: genuine wall relief, holes and shallow floor bars, not interwoven floor cables.

SupaVoxel without material: the floor's stronger textured impression does not survive as comparable geometry.

Weld the UV seams before calling either model broken

Both GLBs split vertices along texture seams. Before welding, the raw meshes misleadingly report open boundaries: 67,868 raw boundary edges in Hyper3D and 123,796 in SupaVoxel. We merged coincident positional vertices and only then measured topology. Both then yielded one face-connected shell, watertight surfaces, zero boundary edges, zero nonmanifold edges and consistent winding. On those narrow geometric checks, the pair ties. A seam mistaken for a hole would reverse the recommendation for no sound reason. Equally, a watertight flag cannot certify that a handle fits fingers, the tray carries weight, the surface is food-safe or a support-free slice succeeds. Those are different tests and were not run.

The front-facing holes survive in the solid mesh; an opening is not proof that its location or diameter was specified.

The other tray also has real open handles, while the front rim is more continuous.

Clean topology is not clean triangles

Hyper3D has zero degenerate triangles in the measured file, whereas SupaVoxel has 60. In the opposite direction, the sliver-face count is 5,048 for Hyper3D and 3,673 for SupaVoxel, a difference of 1,375 in SupaVoxel's favor despite its much denser mesh. Both observations must travel together: calling either model uniformly cleaner would hide a measured problem. Hyper3D's own information overlay quotes 120,000 faces and 97,930 vertices. The exported GLB confirms 120,000 faces but contains 97,677 raw vertices, a discrepancy of 253; we rely on the file for this article. For a shop, this suggests checking triangles and the actual scale before accepting a vendor's one-word readiness badge.

Hyper3D's Gen-1.5 overlay agrees on faces, not vertices; its Print-Ready badge is not a slice result.

Downward-facing area needs the right name

With world Y defined as up, we counted faces whose normals lie within 45 degrees of straight down. Hyper3D's measured potentially downward-facing surface is 10,243.3 mm², or 28.05% of its area, after scaling the longest dimension to 120 mm. SupaVoxel's is 11,259.4 mm², or 33.48%: about 1,016.1 mm² more. Some of that area is the underside contacting the build plate. These are surface orientations, not a slicer's actual support structures or a measurement of resin spent on supports. Change the build orientation and the comparison can change. Anyone quoting the extra square millimeters as an extra support bill would be turning a normal-vector screen into a fabricated workshop outcome.

The unseen reverse of SupaVoxel's tray is generated, not verified by the single input photograph.

Resin is an estimate under one very specific setup

Now picture a hundred of these on a wedding favor table. Scale each model until its longest box edge is 120 mm, fill it solid and assume standard resin at $35/L. Hyper3D's closed shell encloses 63.96 cm³, or about $2.24 per tray; SupaVoxel's encloses 47.00 cm³, about $1.65. That's $0.59 each, or $59 across an imagined hundred in SupaVoxel's favor—not an invoice. The two heights would be only 24.48 and 20.71 mm: neither is a 120-mm-tall tray. Supports, hollowing, machine time and rejected prints could change that bill. This is a material-planning advantage, not a finished factory quote.

Hyper3D's taller wall and larger solid-volume estimate are visible in its side silhouette, not a measured resin purchase.

The missing back cannot be graded for accuracy

The reference shows the right opening but does not disclose the entire far wall. Hyper3D fills that unseen reverse with a central oval opening, prominent vertical ropes and other apertures; SupaVoxel continues a finer diagonal surface with fewer conspicuous openings. Neither could have copied hidden truth from this photograph. A customer needing a specific handle position must inspect and edit the generated back rather than count the most holes as the best reconstruction. This is a practical limit on one-view image-to-3D generation, not proof that every additional opening is mechanically defective. Both remain one connected closed shell after the weld, so the geometric hole openings and the absence of mesh boundary holes are compatible facts.

Hyper3D invented a dramatic reverse wall; the photo provides no reverse-side design to validate it against.

What a real print decision would still require

We did not slice, print, wash, cure, load-test, measure handle clearance or verify food-contact safety. Before quoting a tray, check its physical size and openings, compare the untextured geometry with the requested crossings, address SupaVoxel's 60 degenerate faces and slice at the intended orientation. Hyper3D's obtained Free-tier PBR is a starting file, not a finished product; SupaVoxel's Original size browser export was not obtained, though its locally reconstructed specimen supports the mesh analysis here.

SupaVoxel's Textured, Mesh, Wire and Normals controls help expose the difference between painted detail and printable relief.

Final verdict: a tray shape is not a knit pattern

If I had to send a mesh from this tested workflow to a print technician today, I would send Hyper3D's actual Gen-1.5 PBR file first. Its raised ribs survive color removal, the welded shell closes, and the file arrived. I would also mark its floor for reworking: parallel ribs are not the source's crossing cables, and the reverse-side holes came from inference. That isn't a ready-to-print endorsement.

SupaVoxel is the tray I would show when the customer wants a finer wall weave and a leaner estimated solid resin shape. The wall has fine diagonal relief, its 3,673 slivers beat Hyper3D's 5,048, and at equal 120 mm outer longest side the calculated solid fill is 47.00 rather than 63.96 cm³. I would then turn off the material to expose the nearly flat floor and check export again; 60 degenerate triangles and a failed Original size browser conversion are not details to hide. Neither file copies the pictured floor knit; there is no basis here for a general-purpose winner.

Use SupaVoxel for this job

If the brief is a shallow decorative concept and you can rework the floor, SupaVoxel lets you inspect the textured tray beside its bare mesh before signing off on the knit. Bring your own picture, check the hidden side, and verify your chosen export before promising a physical item. For a finished cable-knit print, neither of these one-shot results is done.

How I tested this

One independently generated 1,862,608-byte reference PNG, byte-matched across the products; one downloadable Hyper3D Gen-1.5 PBR GLB from a 27,809,936-byte ZIP; one SupaVoxel analysis GLB reconstructed locally from its retained compressed project source after its Original size browser export failed. The separate Hyper3D Gen-2.5 preview spent 0.5 credit but was blocked on Free, so it contributes no file measurements. We parsed the files and welded UV seam vertices before topology checks. Longest bounding-box side, not vertical height, was scaled to 120 mm: actual vertical spans were 24.48 and 20.71 mm. Resin is volume × $35/L under hypothetical solid fill; downward-facing area uses world Y-up normals within 45° of down, not slicer support. No slice, print, strength or fit test occurred; no sourced design for the hidden back exists.

Aqua Voice Review 2026: The 230 WPM Dictation App's Plans, Limits and Trade-offs

Elias Larsen — Thu, 08 Oct 2026 15:52:38 +0000

Aqua Voice is a desktop and mobile dictation app that turns speech into clean, formatted text in any application, with a free tier of 1,000 words and paid plans from $8 a month. I went through Aqua Voice’s feature set, its five plans, its platform coverage and the claims on its homepage to work out who should switch from the keyboard and where a voice generation tool, rather than a voice input tool, is the thing you actually need.

“We’ve typed for 150 years. It’s time to speak.” That is the first line on Aqua Voice’s homepage, and the pitch under it is precise: hold a key, speak naturally, and Aqua Voice writes what you meant — into an email, a document, a Slack update or a Codex prompt — at up to 230 words per minute against a 40 WPM keyboard. Aqua Voice has become a favourite of people who spend their day prompting coding agents, and the testimonials on its download page are almost all from that crowd. I spent a week reading Aqua Voice’s homepage, its pricing table and FAQ, and the download page, mapping every plan and every claim.

Because Aqua Voice is strictly about getting your words onto the screen, I kept a text-to-speech and voice-cloning studio, Supavocal, open in the next tab for the opposite direction — turning finished text back into a voice — and I come back to that at the end.

Aqua Voice’s pitch is one gesture — hold Space and speak — and one number: 230 WPM with Aqua 3.1, five times faster than typing.

What Aqua Voice is

Aqua Voice is a system-wide dictation app. You hold a hotkey, talk, and Aqua Voice’s model refines what you said as you talk — removing filler, fixing punctuation, formatting lists — then inserts the text wherever your cursor is. There is no separate window to paste from. Three ideas carry the product:

Works with all your apps. Aqua Voice sits at the OS level, so it dictates into Mail, Notion, Cursor, Codex, a browser form or a terminal without per-app setup.
Your thoughts set the pace. Aqua Voice is built to keep up with fast, rambling speech and to tidy it rather than transcribe it verbatim.
Your screen is its dictionary. Aqua Voice reads what is on screen — code syntax, variable names, product names — so “useState hook for selectedTaskId” comes out spelled the way your file spells it.

The homepage demo is a React component request dictated at 230 WPM with the correct camelCase identifiers, next to the same sentence typed at 40 WPM with typos. That is the Aqua Voice use case in one image.

Getting started with Aqua Voice

Aqua Voice is available for Mac, Windows and iOS, with Android on a waitlist. The Starter plan is free, needs no credit card, and includes 1,000 words with the Avalon transcription model — enough to dictate a few long prompts and a couple of emails and decide whether your voice and Aqua Voice’s model get along. The Mac build is the primary one; “Get Started on Mac” is the call to action on every page.

The download page is a wall of quotes from developers — “for coding prompting with voice nothing beats Aqua Voice”, “saved me over 2 days of typing”.

Aqua Voice pricing in 2026

Aqua Voice sells two individual plans above the free tier and two for organisations, with annual billing 20% cheaper. From Aqua Voice’s pricing page and FAQ:

Starter — free. 1,000 words, Avalon transcription model, no card required.
Pro — $8/month billed annually, or $10 month-to-month. Unlimited words, custom instructions (tell Aqua Voice how you want text formatted), an expanded custom dictionary.
Max — $24/month annually, or $30 month-to-month. Everything in Pro plus Realtime Mode (see words appear live as you speak), the “Send it” voice command that submits the message without touching the keyboard, and early access to new features.
Team — $12/user/month annually, or $15 month-to-month, for teams of 2–9. Pro features plus centralised billing, team-wide settings and an enforced Privacy Mode.
Business — custom, for 10+ seats. SSO/SAML and SCIM, advanced reporting, zero data retention, team-wide dictionaries and volume discounts.

Students get 70% off Pro and Max with a school email — Pro drops to $2.40 a month annually. Everything is cancel-anytime.

The individual tiers differ on one axis — how much Aqua Voice does beyond transcription — not on word counts, once you are past the free 1,000.

Aqua Voice for coding and prompting

This is the audience Aqua Voice is chasing hardest. The homepage’s second section is titled “Prompt faster with your voice” and shows Aqua Voice dictating into the Codex app with GPT-6 Astra selected: “Give GPT-6 Astra the full context in the Codex app. Speak your prompts with Aqua, from the first idea to the final fix.” The screen-as-dictionary feature is what makes this work — Aqua Voice sees the file, the framework and the library names, so spoken prompts arrive with the right identifiers. The testimonials back it up: “all the other transcription apps don’t work well with code like Tailwind class names”, “lowest latency, highest quality STT I’ve used so far”.

The speed and accuracy claims

Aqua Voice claims “5x faster than typing and twice as accurate”, with the 230 WPM figure attributed to its Aqua 3.1 model. Both are demo-derived rather than benchmarked in public, and the accuracy half depends heavily on microphone, accent and how much you ramble. What is fair to say is that Aqua Voice’s refinement step — cleaning the transcript as it goes — is where it differs from built-in OS dictation, and users consistently describe it as “much more accurate than macOS dictation”.

What Aqua Voice gets right

Works everywhere. One hotkey, every app, no paste step.
Context from the screen makes it the best dictation option for code and prompts.
Unlimited words from $8 — the free tier is a trial, but Pro removes the meter entirely.
Custom instructions and dictionary let you shape the output rather than correct it.
Realtime Mode and “Send it” on Max close the loop for hands-free agent conversations.
Team controls — enforced Privacy Mode, SSO, zero data retention — for regulated workplaces.

Where Aqua Voice falls short

1,000 free words is small. At 230 WPM that is under five minutes of speech; you will decide on the paid plan before you have finished evaluating.
Android is waitlist-only. Mac first, Windows and iOS second, Android not yet.
Realtime Mode is a Max feature. Seeing your words as you speak — the thing most people expect from dictation — costs three times Pro.
Cloud processing. Aqua Voice’s model runs in the cloud; Privacy Mode and zero data retention exist, but at Team and Business tiers.
Input only. Aqua Voice turns your voice into text. It does not produce a voice from text, clone one, or make audio for anything you publish.

Aqua Voice vs the alternatives

Against OS-native dictation, Aqua Voice wins on cleanup, context and speed. Against other AI dictation apps, its edge is the screen-aware dictionary and the coding focus; its costs are the metered free tier and the Max-only realtime view. Against text-to-speech tools there is no contest because they do the opposite job — which is exactly why I found myself running both.

Verdict: is Aqua Voice worth it in 2026?

For anyone who writes long prompts to AI agents, drafts a lot of email, or simply thinks faster than they type, Aqua Voice Pro at $8 a month is an easy purchase — the free 1,000 words will tell you in an afternoon. Max is for people who live in voice all day and want to send without touching the keys. Try it on your own long prompts for a day before you choose between Pro and Max.

The alternative worth keeping next to it: Supavocal

Two Aqua Voice facts kept a second tab open: it is voice in, never voice out, and it is the wrong tool the moment you need audio for a video, a course or a product. Supavocal is a text-to-speech and voice-cloning studio for exactly that direction.

30+ voices, 30+ languages, with cloning from a 15-second sample and a Voice Lab for tuning delivery.
Simple metering. 1 credit is 1 character; cloning costs 3x. Starter is $49 a month for 600,000 characters, Pro $99 for 1.5 million, Business $299 for 5 million.
Commercial use included on every paid plan, with API access for pipelines.
Built for output — narration, dubbing, voice-overs and agents that speak, all from text you may well have dictated with Aqua Voice.

Use Aqua Voice to get the words out of your head. When those words need to be spoken back to an audience, keep Supavocal open.

Photo by Klim Musalimov on Unsplash