Measure an AAV vector genome ITR to ITR, see where every base is spent, and find out whether it will package before you commit to a build. Everything runs in your browser: your sequence never leaves your computer.
Paste the whole plasmid. A GenBank file gives the best result, because its features become the budget — Annotate DNA produces one. Plain sequence or FASTA works too: the ITRs are found from the sequence itself.
/label= qualifiers, so anything annotated by Annotate DNA, SnapGene or Benchling will be understood.
Overlapping annotations are fine — each base is counted once, awarded to the most specific feature covering it.
What Pack-It does. It finds the two ITRs, measures the genome between them inclusive, and compares that length against the packaging limit you set. ITRs are located from annotation where your file has it, and from the sequence itself otherwise — which is why you can paste a whole plasmid rather than trimming to ITR–cargo–ITR by hand.
Everything between the ITRs is then divided into segments. Annotated features become named rows in the budget; stretches with no annotation are counted as unannotated, with short runs pooled into a single line so they do not bury the elements that matter. Each base is awarded to one segment only, so overlapping annotations do not double-count and the rows always add up to the genome length.
Limits. Pack-It measures what you give it. A GenBank file with good features produces a meaningful budget; plain sequence produces a correct total with almost everything in the unannotated row. The default capacity figures are the commonly quoted AAV numbers, not a property of your serotype, prep or assay — set them to whatever your programme uses. Nothing here predicts packaging efficiency or titre.
Defaults are the commonly quoted figures for AAV. Set them to whatever your programme uses.
Each base is counted once. Where annotations overlap, the base is awarded to the dominant feature, so these lengths sum exactly to the genome size.
What each number means, and what a bad one looks like.
The budget bar is the headline. It draws the genome against the limit you set, with the efficient minimum marked. Green means it fits with room to spare, amber means it fits but sits below the efficient minimum, and red means it is over the limit. Over the limit is not a soft warning: oversized genomes package heterogeneously and truncate from the 5′ end.
| Tile | What it means | What a bad one looks like |
|---|---|---|
| Genome, ITR to ITR | The length that actually has to package, inclusive of both ITRs, against the limit you set. | Red when it exceeds the limit. Amber when it is under the efficient minimum, where a stuffer is usually the answer. |
| Headroom | Bases left before the limit, and the percentage of capacity used. A negative headroom is shown with a minus sign. | Negative. A few hundred bases of headroom is comfortable; single digits means any future tag or linker pushes you over. |
| Coding | Bases in annotated CDS features, and what share of the genome they take. | “No CDS annotated” usually means the file has no feature table rather than that the construct has no coding sequence. Run it through Annotate DNA first. |
| Unannotated | Bases in no annotated feature. Some is normal — spacers, linkers, cloning scars. | Amber above a quarter of the genome. That much unaccounted payload means the budget below is not telling you where your bases are going. |
| CpG in payload | CpG count, per-kb density and GC content across the packaged genome. CpG content bears on innate immune sensing of the vector genome. | There is no universal threshold. Compare it against the construct you are replacing, and use Recode-It on the transgene if you want it lower. |
| ITRs | How the ITRs were identified, and where they sit. | Amber when no ITRs were found, or only partially. The genome length then means something different from what you think, so fix this before reading anything else on the page. |
Where the bases go lists every element with its position, length and share of the genome, and the chart beside it shows the same thing to scale in sequence order. This is where to look when you need to find bases: the rows are ordered by position, so a large unannotated block between two features is immediately visible.
Findings collects what is worth acting on, including the largest elements you could trim and roughly what each would save. It suggests where the bases are, not whether you can afford to lose them.
Report is a plain-text summary for a notebook or a design review. There is more on what these tools do and do not check in the help and FAQ.
For research use only. Packaging limits vary with serotype, construct and preparation, and the figures above are the ones you set. Verify critical designs experimentally.
Annotate DNA turns a raw sequence into the GenBank this tool reads, and Clone-It and Cleave-It build and check the plasmid. Each opens in a new tab with the sequence from the box above already loaded.
Pack-It runs entirely in your browser: your sequence is not sent to our server or stored anywhere. Packaging limits are design parameters you set, not fixed constants. We count how often this page is opened, and nothing else.