Programming language: Scala
License: MIT License
Tags: JSON    
Latest version: v6.2.0

scalajack alternatives and similar packages

Based on the "JSON" category.
Alternatively, view scalajack alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of scalajack or a related project?

Add another 'JSON' Package



license bintray Build Status Codacy branch grade Coveralls branch

ScalaJack is a very fast, seamless serialization engine for JSON, and other protocols, designed to require the minimum amount of help possible when serializing a class.

Advanced Features:

  • Handles tuples
  • 'Any' support
  • Handles default values for case class fields
  • Rich configuration of trait type hint/value
  • Supports value classes
  • Sealed trait-style enumerations
  • Extensible to other encodings (JSON, CSV, MongoDB, and DynamoDB are provided by ScalaJack, but you can roll your own too!)

Note: Scala 2.13.1 + JDK 13.0.1 + sbt 1.3.5+ or later is strongly recommended! There has been quite a bit of change lately in Scala and sbt and we've found various combinations of Scala/JDK/sbt do not play well together! We can vouch for the combination of Scala 2.13.1 / JDK 13.0.1 / sbt 1.3.5. Later versions should work as well, but you're on your own with earlier versions.


ScalaJack is extremely simple to use.

Include the following in your build.sbt:

resolvers += Resolver.bintrayRepo("blocke","releases")
libraryDependencies ++= Seq("co.blocke" %% "scalajack" % "6.2.0")

If you want to use the optional MongoDB serialization support include this as well:

libraryDependencies ++= Seq("co.blocke" %% "scalajack_mongo" % "6.2.0")

DynamoDB helpers are available here:

libraryDependencies ++= Seq("co.blocke" %% "scalajack_dynamo" % "6.2.0")

ScalaJack is hosted on Bintray/JCenter. If you're using pre-v0.13.9 of SBT you may need to enable the bintray resolver in your build.sbt with

useJCenter := true

Now you're good to go! Let's use ScalaJack in your project to serialize/de-serialize a case class object into JSON:

import co.blocke.scalajack._

val sj = ScalaJack()
val js = sj.render( myCaseObj )  // serialization
val myObj = sj.read[MyCaseClass](js) // deserialization

Couldn't be simpler!


  • [Case Classes and Traits](doc/classesAndTraits.md)
  • [Non-Case Classes and Java Class Support](doc/noncase.md)
  • [Re-name Case Class Fields](doc/mapname.md)
  • [Any Support](doc/any.md)
  • [Value Class Support](doc/valueClass.md)
  • [Parameterized Classes](doc/parameterized.md)
  • [Trait Type Hint Customization](doc/typeHint.md)
  • [Custom Type Adapters (custom read/render)](doc/custom.md)
  • [Try and Capture](doc/tryAndCapture.md)
  • [ParseOrElse and Cascading Fallback Parsing](doc/parseOrElse.md)
  • [Null and None treatment](doc/nullAndNone.md)
  • [Externalized Type Hints](doc/externalTypes.md)
  • [View/SpliceInto](doc/viewSplice.md)
  • [Filter](doc/filter.md)
  • [Union type](doc/union.md)
  • [Converters (new)](doc/map.md)
  • [ScalaJack Configuration](doc/config.md)
  • [Gimme Speed!](doc/speed.md)

Non-JSON Formats:

  • [YAML (new)](doc/yaml.md)
  • [MongoDB](doc/mongo.md)
  • [Delimited (e.g. CSV)](doc/delimited.md)
  • [DynamoDB](doc/dynamo.md)
  • [Json4s](doc/json4s.md)


I need to start this section with an apology. After having benchmarks deactivated for some time I finally wired them up and discovered that ScalaJack 6.0 series was significantly slower than the 5.x series. Definitely not desirable!

ScalaJack 6.1 has undergone a significant streamlining and refactoring with beneficial results. Numbers are below.

Disclaimer: Benchmarks are very situational. We didn't hand-pick a senario to favor our product. It is entirely possible/likely you can find scenarios where your favorite parser beats ScalaJack.

Benchmark Score Error Units
ScalaJack 6.1 (forType[T]) 27729.218 ± 338.995 ops/s
Hand-written 24041.835 ± 1752.455 ops/s
ScalaJack 6.1 20232.361 ± 736.766 ops/s
Circe 19971.288 ± 986.961 ops/s
ScalaJack 5.x 16349.600 ± 193.090 ops/s
ScalaJack 6.0 11111.795 ± 127.843 ops/s
LiftJson 9313.472 ± 639.219 ops/s
Json4s 3425.144 ± 219.970 ops/s

The key takeaway here is that for our sample test, ScalaJack was very fast, and most critically, ScalaJack 6.1 is a dramatic improvement over 6.0.

Series 6

Series 5 introduced a whole new engine for ScalaJack. For series 6 we went through and streamlined everything internally. JSON is no longer assumed in the core, allowing for an easier extension to other protocols. Internally the code is tighter and cleaner, which always makes us feel happy.

A major goal of this release was to clean up the internals to be ready for Dotty/Scala 3.0 when it comes out.

We've got to give our users at least a few new toys, so we've added a filter feature, so you can filter on incoming parsed messages, pulling out those you care about and passively ignoring those you don't.

There have also been improvements to Delimited/CSV handling. Before, ScalaJack could not handle List in CSV format. Now it can (for simple Lists), along with Either and Enumeration.

MongoDB support has been strengthened, with some of the limitations of earlier versions removed. Type hint modifiers (for type members) are now supported. Support for scalar non-String keys (Int, Boolean, etc) work now too. Try and SJCapture features are now supported for Mongo as well as JSON.

One feature was removed: non-canonical JSON support. If you loved this feature, I understand, but its benefits just weren't worth the benefit of continued maintenance.

We hope you'll enjoy using the latest ScalaJack!


*Note that all licence references and agreements mentioned in the scalajack README section above are relevant to that project's source code only.